Wed 26 Nov 2008 08:24:49 PM UTC, original submission:
I'm running the following wget, pulled from Hg today and compiled on Ubuntu Intrepid:
$ ../wget/src/wget --version
GNU Wget 1.12-devel (bb58048a2b58)
Options : +digest +ipv6 +nls +ntlm +opie +md5/openssl -gnutls
+openssl +gettext
Wgetrc : /usr/local/etc/wgetrc (system)
Locale : /usr/local/share/locale
Compile : gcc -DHAVE_CONFIG_H
-DSYSTEM_WGETRC="/usr/local/etc/wgetrc"
-DLOCALEDIR="/usr/local/share/locale" -I. -I../lib -g -O2
Link : gcc -g -O2 -lssl -lcrypto -ldl -lrt ftp-opie.o openssl.o
http-ntlm.o gen-md5.o ../lib/libgnu.a
Find a non-resumable URL, or just funnel requests through Privoxy. (Privoxy disables resuming when any filtering is active.) I'm using http://cr.yp.to/papers.html, but any non-resumable source will work.
First, download a bit of it.
$ ../wget/src/wget -c --limit-rate=30k 'http://cr.yp.to/papers.html'
--2008-11-26 15:20:38-- http://cr.yp.to/papers.html
Resolving cr.yp.to... 131.193.36.21
Connecting to cr.yp.to|131.193.36.21|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 56203 (55K) [text/html]
Saving to: `papers.html'
17% [=====> ] 9,966 30.0K/s
I hit CTRL-C after it was partly downloaded, to get a partial file.
Now, attempt to resume it:
$ ../wget/src/wget -c --limit-rate=30k 'http://cr.yp.to/papers.html'
--2008-11-26 15:20:54-- http://cr.yp.to/papers.html
Resolving cr.yp.to... 131.193.36.21
Connecting to cr.yp.to|131.193.36.21|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 56203 (55K) [text/html]
Saving to: `papers.html'
68% [========================> ] 56,203 30.0K/s in 1.8s
2008-11-26 15:20:56 (30.0 KB/s) - `papers.html' saved [56203/56203]
Note that the progress bar doesn't come out to 100%, even though the file is all there. (It's not corrupted, either.) It seems like the correct filesize isn't being used to calculate the maximum size of the progress bar.
Additionally, if the file is all there, the progress bar will always fill to fifty percent, and complete the file at that point.
I ran into this while testing bug #24940, but it's a separate issue.
|