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

2019-02-10 Thread 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 respo

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

2019-02-06 Thread Amos Jeffries
On 7/02/19 6:39 am, Ivan Larionov wrote: > Hello. > > We've recently noticed a difference in behavior between squid v3 and v4. > > On HTTP response with non-standard 4-digits HTTP code, for example > something like this: > > HTTP/1.1 5009 Update Error > Connection: Closed > > {"code":500911,"me