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

Michal Mocny commented on CB-1406:
----------------------------------

I just tried the attached test case with these results:

- on ios6 safari, readyState 4, status 0
- on ios6 webview, readyState 4, status 0
- on ios5 safari, readyState 4, status 0

I did not test with cordova, since I am not reproducing the expected results as 
is (though clearly something is wrong since status is 0).  It seems like either 
the attached test case is invalid, or there is some long standing ios bug with 
web workers/XHR.  I'm not digging further for now, just wanted to give another 
data point.
                
> HTTP-Get via XHR in Web Workers always return status 0 under iOS 6 (Beta 4)
> ---------------------------------------------------------------------------
>
>                 Key: CB-1406
>                 URL: https://issues.apache.org/jira/browse/CB-1406
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.1.0
>         Environment: all iOS devices and simulators
>            Reporter: Jochen Magnus
>            Assignee: Shazron Abdullah
>              Labels: HTTP, WebWorker, XHR
>             Fix For: 2.2.0
>
>         Attachments: testworker.js, workertest.html
>
>
> HTTPRequests in the Web Workers ending always with http.readyState==4  
> (that's the ready state) but with http.status==0, which is an undefined 
> status (normal is 200 for "o.k."). The file is requested from and fully 
> deliverd by the webserver. 
> This happens under iOS 6 Beta 4 but not under iOS 5.x where the same app with 
> the same Cordova version works well.
> The problem did not occur with XHR in the native programs main thread nor in 
> non-native HTML5-apps (WebApps without the use of Cordova). 
> A Xcode test project is available. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to