We do not know and can not know why the server sends such a request.
There are only assumptions of varying degrees of reliability. SQUID
configuration in this case is absolutely not enough to give a reasonable
answer.
If the problem is DNS - then what's the Squid?
24.11.15 17:22, Ahmad Alzaeem пишет:
Hi Devs ,
I have a server that send to squid http/https with wrong destination ips
So assume I want to open google
The request hit the squid with https/http packet with payload
www.google.com <http://www.google.com> with ds tip 10.0.0.1 not the
real ds tip of google like 74.125.x.x
The question is being asked here is .
Is it possible to let squid to do another resolving again and chck the
right dst ip (74.125.x.x) and reach it ?
Or at least let squid skip looking @ the ds tip and look only at the
payload (google.com) and try to resolve it and operate ?
Is that possible on squid ?
thanks
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
