> Personally I am satisfied with just downloading the file ignoring 404 status. That would be convenient, and follows the "deal with it or ignore it and render

> Personally I am satisfied with just downloading the file ignoring 404 status. That would be convenient, and follows the "deal with it or ignore it and render what you can" pattern followed by browsers in the face of malformed HTML, but... > I wonder which should be the correct behavior? I'd argue that displaying the "not found" message, and aborting any other transfer, would be the more correct thing to do, despite being less convenient. Something thinks there is an error condition while responding the request, so can you really trust any content returned by the response to be as it should be?