You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2012/09/21 06:04:07 UTC
[jira] [Created] (CB-1518) FileTransfer.download progress events
has this.lengthComputable = false when response is gzipped on iOS
Andrew Grieve created CB-1518:
---------------------------------
Summary: FileTransfer.download progress events has this.lengthComputable = false when response is gzipped on iOS
Key: CB-1518
URL: https://issues.apache.org/jira/browse/CB-1518
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 2.2.0
Reporter: Andrew Grieve
Assignee: Andrew Grieve
Priority: Minor
As far as I can tell, there is no way to track the actual bytes downloaded except for changing network stacks to something like ASI's.
Lame other option #1:
Re-gzip the response locally to approximate.
Lame other option #2:
Send a second request HEAD request without accept-encoding header (while the first request is in progress), and that will tell us the expected non-compressed length. This option is actually reasonable I think.
--
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
[jira] [Updated] (CB-1518) FileTransfer.download progress events
has this.lengthComputable = false when response is gzipped on iOS
Posted by "Shazron Abdullah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shazron Abdullah updated CB-1518:
---------------------------------
Fix Version/s: 2.4.0
> FileTransfer.download progress events has this.lengthComputable = false when response is gzipped on iOS
> -------------------------------------------------------------------------------------------------------
>
> Key: CB-1518
> URL: https://issues.apache.org/jira/browse/CB-1518
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 2.2.0
> Reporter: Andrew Grieve
> Assignee: Andrew Grieve
> Priority: Minor
> Fix For: 2.4.0
>
>
> As far as I can tell, there is no way to track the actual bytes downloaded except for changing network stacks to something like ASI's.
> Lame other option #1:
> Re-gzip the response locally to approximate.
> Lame other option #2:
> Send a second request HEAD request without accept-encoding header (while the first request is in progress), and that will tell us the expected non-compressed length. This option is actually reasonable I think.
--
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