On 12.01.2012 02:28, kimi ge wrote:
Hi Amos,
Really appreciate your help.
I did changes with your sugguestion.
Some debug logs are here:
2012/01/11 13:21:58.167| The request GET
http://ids-ams.elabs.eds.com/
is ALLOWED, because it matched 'origin_servers'
2012/01/11 13:21:58.168| client_side_request.cc(547)
clientAccessCheck2: No adapted_http_access configuration.
2012/01/11 13:21:58.168| The request GET
http://ids-ams.elabs.eds.com/
is ALLOWED, because it matched 'origin_servers'
2012/01/11 13:21:58.170| ipcacheMarkBadAddr:
wtestsm1.asiapacific.hpqcorp.net 16.173.232.237:80
2012/01/11 13:21:58.171| TCP connection to
wtestsm1.asiapacific.hpqcorp.net/80 failed
There you go. Squid unable to even connect to the IIS server using TCP.
Bit strange that it should use 404 instead of 500 status. But that TCP
connection failure is the problem.
<snip>
My squid environment information:
RHEL6.0 64bit.
squid v 3.1.4
A very outdated Squid release version, even for RHEL (which are on
3.1.8 or so now).
* start with checking your firewall and packet routing configurations
to ensure that Squid outgoing traffic is actually allowed and able to
connect to IIS.
* if that does not resolve the problem, please try a newer 3.1
release. You will likely have to self-build or use non-RHEL RPM, there
seem to be no recent packages for RHEL.
Amos
