[
https://issues.apache.org/jira/browse/CB-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033546#comment-14033546
]
ASF GitHub Bot commented on CB-6928:
------------------------------------
Github user jpuerto commented on the pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/31#issuecomment-46279769
As commented in the dev mailing list, this patch is not valid. We need to
return the caching status with the error callback so the developer can act
accordingly.
> Wrong behaviour transferring cacheable content
> ----------------------------------------------
>
> Key: CB-6928
> URL: https://issues.apache.org/jira/browse/CB-6928
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
> Affects Versions: 3.5.0
> Reporter: Javier Puerto
> Priority: Minor
> Attachments: CB-6928.diff
>
>
> Use case:
> Transfer resources from server to the device. To avoid unnecessary use of the
> device bandwidth, the resources that exists already are checked with the
> "If-Modified-Since" header so server can return 304 status code and update
> just in case that is needed.
> Result for Android test:
> The plugin doesn't care about the status code, if the request is success,
> open the InputStream and copy the content to the file. The problem is that a
> HTTP status of 304 has no response and that leads to a corrupted file
> transfer.
> Fix:
> If status code is 304, doesn't makes sense to process the InputStream. Read
> the status code after connection and if it's 304, skip the copy process and
> return the file entity like a success transfer.
> I've tested for Android only.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
