On 8/15/23 15:04, Andreas Weigel wrote:
just in reference to
https://github.com/squid-cache/squid/pull/702#issuecomment-762459132, I
was made aware of a(nother) buggy server in the wild, that sends the
header quoted in the subject (Squid version 4.16) in its response:
https://riverbird.de. Squid rejects connection to that server with an
"Invalid response..." error message, while all browsers I used were able
to open the website.
The server seemingly only shows the behavior if 'Accept-Encoding: gzip'
is set in the request. The actual encoding used for the response is a
simple (single) chunked encoding.
FWIW, in my test, that server sent two identical "Transfer-Encoding:
chunked" and many other duplicated header fields:
HTTP/1.1 200 OK
Date: Thu, 17 Aug 2023 16:44:46 GMT
Server: Apache
Link: ...
Set-Cookie: <cookie1>
Set-Cookie: <cookie2>
Set-Cookie: <cookie2>
Vary: Accept-Encoding
X-Via-NSCOPI: 1.0
X-Via-NSCOPI: 1.0
Transfer-Encoding: chunked
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache
Cache-Control: no-cache
Strict-Transport-Security: max-age=157680000
Strict-Transport-Security: max-age=157680000; includeSubDomains
Content-Encoding: gzip
I could not quickly check what the actual transfer encoding was.
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
