Nick Hogg <[EMAIL PROTECTED]> writes: > At 11:07 06/02/2004, Hrvoje Niksic wrote: > >>Did it wait for 900 seconds before timeouting? Generally, does the >>error occur at the same byte position each time? > > Seems to...It seems to happen on the same byte. But its happening on a > few domains I am trying. > > Here is a sample of one of the logs (slightly edited)... > > #less ../logs/wget/wget.log_www.somedomain.com > 1 --11:21:37-- http://www.somedomain.com/ > 2 => `domain/www.somedomain.com/index.html' > 3 Resolving www.somedomain.com... done. > 4 Connecting to www.somedomain.com[xxx.xxx.xxx.xxx]:80... connected. > 5 HTTP request sent, awaiting response... 200 OK > 6 Length: ignored [text/html] > 7 Last-modified header missing -- time-stamps turned off. > 8 --11:21:38-- http://www.somedomain.com/ > 9 => `domain/www.somedomain.com/index.html' > 10 Connecting to www.somedomain.com[xxx.xxx.xxx.xxx]:80... connected. > 11 HTTP request sent, awaiting response... 200 OK > 12 Length: ignored [text/html] > 13 > 14 0K .......... ......... > 18.39 KB/s > 15 > 16 11:36:40 (18.39 KB/s) - Read error at byte 19768 (Operation > timed out).Retrying.
Hmm. Does the download work if you add `--no-http-keep-alive'? It might be that `--ignore-length' interferes with Wget's attempts to use persistent connections.
