Hrvoje Niksic wrote:
If your point is that Wget should print a warning when it can *prove*
that the Content-Length data it received was faulty, as in the case of
having received more data, I agree. We're already printing a similar
warning when Last-Modified is invalid, for example.
I'm
Hello,
If the http content-length header differs from actual data length,
wget disregards the http specification as follows:
1) if content-length is greater than actual data, wget keeps retrying to
receive the whole file indefinitely. Using the command-line parameter
--ignore-length fixes this
Noel Koethe [EMAIL PROTECTED] writes:
If the http content-length header differs from actual data length,
wget disregards the http specification as follows:
It doesn't disregard the HTTP specification. As far as I'm aware,
HTTP simply specifies that the information provided by Content-Length
