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

Shazron Abdullah commented on CB-2183:
--------------------------------------

I proposed on CB-1600 that we revert that patch since it only applies to iOS 
4.3, and we only support iOS 5.0 and greater now.
                
> [iOS] FileTransfer.didReceiveResponse may not return NSHTTPURLResponse
> ----------------------------------------------------------------------
>
>                 Key: CB-2183
>                 URL: https://issues.apache.org/jira/browse/CB-2183
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.2.0
>         Environment: Tested on iOS 5.1 and 6.0
>            Reporter: William Wong
>            Assignee: Shazron Abdullah
>            Priority: Critical
>              Labels: File, FileTransfer
>
> When FileTransfer.download() is downloading a file from file:///, 
> NSURLConnection did not return with NSHTTPURLResponse. This will fail for 
> apps that copy files from www/, e.g. apps that initialize its database from a 
> pre-built cache packaged in IPA.
> In CB-1600 (fixed in 2.2.0), the fix assumes all response must be 
> NSHTTPURLResponse. So when FileTransfer.download() is downloading from a 
> file:/// URL (e.g. copying file from www/ folder to Documents/), FileTransfer 
> assumed the download operation failed and returned 403.
> Tested if we comment out CB-1600, downloading from file:/// works again.
> We need to find out a better fix instead of commenting out CB-1600.
> According to 
> http://developer.apple.com/library/ios/#documentation/Cocoa/Conceptual/URLLoadingSystem/URLLoadingSystem.html#//apple_ref/doc/uid/10000165i,
>  URL of file:/// is supported.
> You can test FileTransfer.download() by calling it with 
> "encodeURI(document.location.href)" as the "source" parameter.

--
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