flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-35110) Flex based component using FileReference Upload API fails with 400 Bad Request for multi upload scenario because of missing boundary conditions
Date Tue, 12 Jul 2016 14:43:20 GMT

    [ https://issues.apache.org/jira/browse/FLEX-35110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372980#comment-15372980
] 

Alex Harui commented on FLEX-35110:
-----------------------------------

You would have to contact Adobe support for an official answer.  Adobe Flex 3.6 shipped with
Adobe Flash Builder 4.7 which is still under support, so you may get support for Adobe Flex
3.6.

However, FileReference is a Flash API, not a Flex API.  A recommended practice when you are
having trouble with Flash APIs in a Flex app is to make an ActionScript-only (no Flex) test
project that tests the Flash API.  If you can make it fail, then you can more easily see if
it will fail against the last Flash version and then you should be able to get support from
Adobe.

> Flex based component using FileReference Upload API fails with 400 Bad Request for multi
upload scenario because of missing boundary conditions
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-35110
>                 URL: https://issues.apache.org/jira/browse/FLEX-35110
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: RPC: General
>            Reporter: Vamshi Krishna Kaley
>         Attachments: Multiple SCORM Uploads   Troubleshooting with Engg and CO.msg
>
>
> We have developed a component of multi file upload using flex sdk 3 using FileReference
Upload built in functionality.
> However we have encountered that the upload fails for more than two files over slow transmission
networks.
> On further investigation  We found that the flash is resulting in I/O Errors during the
retrieval of total bytes being uploaded for display in the upload progress with the log information
as displayed below
> ==============================================
> 388956 AVMINF: MTHD flash.events::ProgressEvent/get bytesLoaded ()
> 388958 AVMINF: MTHD flash.events::ProgressEvent/get bytesTotal ()
> 388960 AVMINF: MTHD flash.events::IOErrorEvent ()
> 388962 AVMINF: MTHD flash.events::ErrorEvent ()
> 388964 AVMINF: MTHD flash.events::TextEvent ()
> 388965 AVMINF: MTHD flash.events::Event ()
> 388967 AVMINF: MTHD flash.events::Event/ctor ()
> 388970 AVMINF: MTHD FileUpload/OnIOError ()
> 388972 AVMINF: MTHD flash.events::IOErrorEvent/toString ()
> IOError Event : Dispatched when the upload or download fails.[IOErrorEvent type="ioError"
bubbles=false cancelable=false eventPhase=2 text="Error #2038: File I/O Error. URL: <<http
based Post URL>>
> =============================================
> Due to this error the POST request is resulting in Bad Requests on the Web Server because
of the missing boundary closures which are required to complete the POST request.
> This issue is always replicable on slow networks which are hovering around 100Kbps
> Request you to look into it and do the needful to provide a fix which needs to be incorporated
as one of our customers are critically affected with this functionality miss.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message