Inappropriate error messages?

At times, something happens and Squid (1.0.17) feels that it's necessary
to return an error message to the client. Normally, if nothing has yet
been received this is fine as the browser renders the error message
properly.

Sometimes (like right now, with our backbone microwave reporting 88%
packet loss), part of a page will be returned before the error occurs
(read timeout, whatever) - but Squid still returns an error message! The
result on the client's browser is somewhat confusing for those who don't
know what's going on, because it even includes all the normal HTTP headers
that aren't generally shown to the user.

Is it possible for Squid to keep a flag, and as long as nothing has yet
been sent to the browser, return an error message, but if *anything* has
already been sent, remain silent? Or does 1.1 do this already?

Thanks..

dave
Received on Sun Oct 27 1996 - 04:07:01 MST