On 11/14/22 07:12, Dieter Bloms wrote:
I've increased the debuglevel, but can't find any reason, why squid reponds with ERR_INVALID_RESP.
HTTP/1.1 200 OK Server: Oracle-Application-Server-11g Transfer-Encoding: chunked Via: 1.1 www.ilo.org Transfer-Encoding: chunked
The above (abridged) response is malformed because it has two Transfer-Encoding headers signalling "chunked, chunked" transfer encoding. The proxy and/or the origin server your Squid is talking to is broken.
Modern Squids reject such messages because they are known to be used for cache poisoning and other security breaches. There is no official workaround (yet).
HTH, Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
