Hi All,
I am having a problem with our Squid hierarchy. I am getting
TCP_DENIED in the access.log and the cache.log shows a forwarding
loop detected. Here is the access.log entry:
192.168.1.81 - - [03/Sep/2007:14:01:06 -0500] "GET http://
web.example.com/customers/mba HTTP/1.0" 403 1469 TCP_DENIED:NONE
208.106.5.39 - - [03/Sep/2007:14:01:06 -0500] "GET http://
web.example.com/customers/mba HTTP/1.1" 403 1570 TCP_MISS:DIRECT
And here is the cache.log entries:
2007/09/03 13:58:50| parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST)
failed: (92) Protocol not available
2007/09/03 14:00:20| parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST)
failed: (92) Protocol not available
2007/09/03 14:01:06| WARNING: Forwarding loop detected for:
Client: 192.168.1.81 http_port: 192.168.1 1.81:80
GET http://web.example.com/customers/mba HTTP/1.0
Accept: */*
Accept-Language: en
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en)
AppleWebKit/419.3 (KHTML, like Gecko) Safari/419.3
Host: web.accelerint.com
Via: 1.1 squid-1.example .com:80 (squid/2.5.STABLE14)
X-Forwarded-For: 208.106.5.39
Cache-Control: max-age=259200
Connection: keep-alive
I think our Squid parent is not responding so Squid goes direct to
source. Is there a way to ensure that Squid will not go to origin
even if the parent does not respond? We do DNS load-balancing so
when the Squid tries to go direct to source, I think that is where
our loop begins.
Thanks,
Paul
