[squid-users] IPv6 happy eyeball on dualstack host

2024-06-05 Thread sachin gupta
Hi We are shifting to IPv6 dual stack hosts. As per squid documentation , IPv6 is enabled by default. I tried a request on www.google.com which has both IPv4 and IPv6 address. As per documentation, based on DNS response squid will try both IP4 and IPv6 i

Re: [squid-users] TCP_TUNNEL/500 in squid logs in squid 5.9

2023-06-12 Thread sachin gupta
hin, > > What's the issue? > That the logs don't reflect the reality? > > Thanks, > Eliezer > > > From: squid-users On Behalf > Of sachin gupta > Sent: Thursday, May 25, 2023 18:21 > To: squid-users@lists.squid-cache.org > Subject: [squid-users] TCP_TUN

Re: [squid-users] host_verify_check behaviour in intercept mode for domain behind Loadbalancer ( multiple IPs )

2023-05-30 Thread sachin gupta
age.cc(1386) buildBody: No existing error page language negotiated for ERR_CONFLICT_HOST. Using default error file. Regards Sachin On Tue, May 16, 2023 at 7:33 PM Amos Jeffries wrote: > On 16/05/2023 6:52 pm, sachin gupta wrote: > > Hi > > We recently shifted to squid 5.9 and start

Re: [squid-users] TCP_TUNNEL/500 in squid logs in squid 5.9

2023-05-26 Thread sachin gupta
406 debugs(33, 9, "clientLogRequest: http.code='" << al->http.code << "'"); The lines inside if ( 400-401 ) did not get printed but 406 got printed with status code as 500. I also collected cache.log with debug level as 5 but mailing list is not

[squid-users] TCP_TUNNEL/500 in squid logs in squid 5.9

2023-05-25 Thread sachin gupta
Hi All We are migrating for squid 4.15 to squid 5.9. We are running our existing test suite to check if we pass our sanity testing. For requests in transparent mode, though request passes and client get 200, in squid logs we are getting TCP_TUNNEL/500. We were not getting this issue with squid 4.

[squid-users] host_verify_check behaviour in intercept mode for domain behind Loadbalancer ( multiple IPs )

2023-05-15 Thread sachin gupta
Hi We recently shifted to squid 5.9 and started seeing errors in Transparent mode SECURITY ALERT: Host header forgery detected on conn3615903 local=44.242.184.237:443 remote=10.109.176.240:8990 FD 28029 flags=17 (local IP does not match any domain IP) Previously we were using https://github.com/

Re: [squid-users] host_verify_strict is not working as expected

2021-08-02 Thread Sachin Gupta
Amos Jeffries wrote: > On 2/08/21 6:12 pm, Sachin Gupta wrote: > > Hi All > > > > I am using squid version 4.9. I did set host_verify_strict to on. As per > > documentation in link > > > https://urldefense.com/v3/__http://www.squid-cache.org/Doc/config

[squid-users] host_verify_strict is not working as expected

2021-08-02 Thread Sachin Gupta
Hi All I am using squid version 4.9. I did set host_verify_strict to on. As per documentation in link http://www.squid-cache.org/Doc/config/host_verify_strict The request should fail if host header is different than uri. I used this request and squid allowed the request though as per documentaion