On 2012-07-12 20:43:05 -0400, ThoMas Dickey wrote: > What you're saying is that the content length is incorrect. > > RFC 2616 doesn't appear to specify behavior when the content-length is > incorrect.
No, what I'm saying is that the content-lenth is correct (it is the real length of the file), but the server sends additional data after the file contents. I assume that these data are unspecified (but there occur after the file has been sent), and most browsers seem to ignore them. In any case, if lynx is confused by something unspecified, it should display an error (and exit with a non-zero exit status in case of -dump), not let the user with a corrupted file. -- Vincent Lefèvre <[email protected]> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
