NOVM errmsg misses HTTP status

Fesgar math,

The difference between a NOVM and a VM squid is that a NOVM squid does not
prepend the HTTP/1.0 header on error messages.

For instance, if I ask my NOVM (with telnet, or sock)

GET http://nonexistent.my.domain/ HTTP/1.0

it will reply directly with the error message (as if this was HTTP/0.9).
But if I ask the same question my VM Squid, it will reply *with* the
HTTP/1.0 header (the line above is just meant to provoke an error message
from my squids).

The importent part is that many automatic thingies check for the HTTP
result code. A missing code is often assumed to be no error. The bug is
still visible with the 19th series of Squid.

Okok, here the platform: Solaris 2.5.1, gcc 2.7.2.3, used -O option.
Does anybody have a suggestion to a fix?

Le deagh dhùrachd,
Dipl.-Ing. Jens-S. Vöckler (voeckler@rvs.uni-hannover.de)
Institute for Computer Networks and Distributed Systems
University of Hanover, Germany
Received on Mon Dec 29 1997 - 05:03:17 MST