Thank you for the quick response and confirmation that this is indeed a bug. I have since confirmed that the same bug is present also in 6.1. On Wed, Aug 9, 2023 at 3:38 PM Alex Rousskov wrote: > Thank you for sharing those details. When developers start working on a > fix, they may find them very useful (if they can find them at that > time). You may also want to post a bug report on Squid Bugzilla. I have gone ahead and submitted bug 5294 (https://bugs.squid-cache.org/show_bug.cgi?id=5294) for this issue now. > Given all these uncertainties, if your infrastructure relies on a very > specific HTTP status response code, it may be a good idea to redesign. Indeed. I would expect clients to functionally behave the same whether they receive a 500 or a 503 in this case. It's just less informative and may require more investigation time to determine if there is indeed an actual internal error in Squid or if the client just tried to connect to a domain that doesn't exist. At least now I know that it's not expected behavior so that I can document it accordingly for our users. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
