On 4/02/2023 11:06 am, Tom JABBER wrote:
@alex
"because popular browsers pretty much ignore CONNECT response headers
(except for proxy authentication) and body (always?)."
Well that's exactly how we discovered it: facing a parent proxy that
needs some AUTH.
"* After sending (to the client) an HTTP response header promising a
body, Squid has an obligation to send that promised (and available to
Squid) response body. Squid does not send it. Squid is buggy."
We definitively agree on this.
"It is possible to modify Squid to stop promising to send the
cache_peer response body (at an HTTP framing level), but it is
probably better (and easier!) to modify Squid to just generate a short
error response from scratch (instead of forwarding cache_peer response
headers without a body). Doing so will probably break some use cases,
so such a change may be officially rejected, but, even if it is, it
may still work/help in some other specific use cases."
By saying this you're suggesting I try to code this ? Or is there a
possible configuration I missed ?
@amos
"curl itself does this even without Squid."
What do you mean ?
The curl trace I showed in my post after that statement is identical in
all the important ways to the one provided as evidence of Squid bug.
Except that my trace was done by making curl contact a web server - not
a proxy.
In my test, using the squidclient tool to replicate the identical
traffic shows content being delivered by the web server that curl did
not show.
As such the curl output provided with "no content" is not evidence of
anything other than how curl itself is behaving.
Cheers
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
