Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.2.0
-
None
Description
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.