[squid-users] Bad HTTP header error on non-standard HTTP response code

[Alex Rousskov]

On 2/6/19 10:39 AM, Ivan Larionov wrote:
> is there an option to change squid 4 behavior to match squid 3?

It is easy to relax Squid response parser to accept more syntactically
invalid HTTP responses, but one would need a good use case to do so
officially because of the problems with HTTP/0 responses (that Amos has
mentioned) and other message smuggling dangers. A single case of an
unusual/rare broken origin server is unlikely to be sufficient for this
IMHO.

Alex.
P.S. If you want to patch your Squid, look for the tok.int64() call in
Http::One::ResponseParser::parseResponseStatusAndReason().