"Tony Lewis" <[EMAIL PROTECTED]> writes: > Since wget is an HTTP/1.0 client, its behavior is entirely > consistent with the specification. Noel was probably thinking of RFC > 2068, which says: > > When a Content-Length is given in a message where a message-body > is allowed, its field value MUST exactly match the number of > OCTETs in the message-body. HTTP/1.1 user agents MUST notify the > user when an invalid length is received and detected.
Even so, when less data have been received, it's impossible to detect whether that's because of a faulty network or a faulty server. Wget defaults to believing the server, which is in conformance with HTTP. 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.
