[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391)
From: |
Darshit Shah |
Subject: |
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391) |
Date: |
Fri, 17 Aug 2018 09:37:10 +0000 |
Right.. Waiting for that and the documentation changes.
Also, I just realised there's another issue. The `length` parameter you're
using is the size of the finally downloaded file which is not the same the
number of bytes downloaded.
The issue occurs when the web server serves a gzip-transport. Then the `length`
parameter will be larger (or smaller, in edge cases) than the actual number of
bytes downloaded as expected from the `content-length` header. You will have to
make a few more changes to get the raw number of bytes downloaded
(`resp->cur_downloaded` is the cumulative number of raw bytes downloaded)
--
Reply to this email directly or view it on GitLab:
https://gitlab.com/gnuwget/wget2/merge_requests/391#note_95093799
You're receiving this email because of your account on gitlab.com.
- Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), (continued)
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Darshit Shah, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Darshit Shah, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Josef Möllers, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391),
Darshit Shah <=
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Josef Möllers, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Josef Möllers, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Tim Rühsen, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Josef Möllers, 2018/08/17
Re: [Wget-dev] wget2 | Fix progress display (issue #339) (!391), Josef Möllers, 2018/08/17