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

ASF GitHub Bot commented on CB-13466:
-------------------------------------

GitHub user bobobobo opened a pull request:

    https://github.com/apache/cordova-plugin-file-transfer/pull/193

    CB-13466: (ios) Only use HEAD to get real length if content encoding …

    …is gzip


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/notnotse/cordova-plugin-file-transfer 
ios-gzip-real-length

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-plugin-file-transfer/pull/193.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #193
    
----
commit a0b03fee7d1f4ab4d478c28dcd612235bb588bb8
Author: Bobo Häggström <[email protected]>
Date:   2017-10-19T12:02:17Z

    CB-13466: (ios) Only use HEAD to get real length if content encoding is gzip

----


> HEAD request to get real length should only be used for content encoding gzip 
> on iOS
> ------------------------------------------------------------------------------------
>
>                 Key: CB-13466
>                 URL: https://issues.apache.org/jira/browse/CB-13466
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-plugin-file-transfer
>            Reporter: Bobo Häggström
>
> When downloading files without file size (for example dynamically created 
> content) the progress is not updated correct because of the HEAD request to 
> get the real length. In the Android implementation which works, a HEAD 
> request is only used for content encoding gzip. I think the iOS 
> implementation should work the same way.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to