On 2024-07-12 11:38, Ben Toms wrote:
Think I made the changes Alex requested:
12/Jul/2024:15:36:31 +0000.640 local.server.ip TCP_MISS_ABORTED/502 3974
GET https://local.server.fqdn/path/to/file -
FIRSTUP_PARENT/public.ip.of.public.server text/html
ERR_READ_ERROR/WITH_SERVER
Thank you for using Squid v6 for this test.
Unfortunately, due to Squid logging bugs, ERR_READ_ERROR/WITH_SERVER
does not always mean what it says. For example, parent Squid could have
closed the child-parent connection prematurely, but there could be other
reasons. A full debugging log should give us more information.
2024/07/12 14:57:08.678 kid1| 11,2| Stream.cc(274) sendStartOfMessage:
HTTP Client REPLY:
This is a child proxy response to the client. We need parent response to
the child proxy. Look for "HTTP Server RESPONSE" lines instead.
HTH,
Alex.
---------
HTTP/1.1 502 Bad Gateway
Server: squid/6.6
Mime-Version: 1.0
Date: Fri, 12 Jul 2024 14:57:08 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 3629
X-Squid-Error: ERR_READ_ERROR 0
Vary: Accept-Language
Content-Language: en
Cache-Status: squid.host;detail=mismatch
Via: 1.1 squid.host (squid/6.6)
Connection: keep-alive
----------
Regards,
Ben.
*From: *squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> on
behalf of Amos Jeffries <squid3@xxxxxxxxxxxxx>
*Date: *Friday, 12 July 2024 at 15:22
*To: *squid-users@xxxxxxxxxxxxxxxxxxxxx <squid-users@xxxxxxxxxxxxxxxxxxxxx>
*Subject: *Re: TCP_MISS_ABORTED/502
On 13/07/24 01:52, Alex Rousskov wrote:
On 2024-07-12 08:06, Ben Toms wrote:
Seems that my issue is similar to -
https://serverfault.com/questions/1104330/squid-cache-items-behind-basic-authentication <https://serverfault.com/questions/1104330/squid-cache-items-behind-basic-authentication>
You are facing up to two problems:
1. Some authenticated responses are not cachable by Squid. Please share
HTTP headers of the response in question.
FYI, those can be obtained by configuring squid.conf with
debug_options 11,2
Cheers
Amos
2. TCP_MISS_ABORTED/502 errors may delete a being-cached response. These
can be bogus errors (essentially Squid logging bugs) or real ones (e.g.,
due to communication bugs, misconfiguration, or compatibility problems).
I recommend adding %err_code/%err_detail to your logformat and sharing
the corresponding access.log lines (obfuscated as needed).
Sharing (privately if needed) a pointer to compressed ALL,9 cache.log
while reproducing the issue using a single transaction may help us
resolve all the unknowns:
https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction <https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction>
HTH,
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
<https://lists.squid-cache.org/listinfo/squid-users>
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
