Paul Bertain wrote:
Hi Tek and Adrian,
I appreciate the suggestions. We have resolved our issue, which was
related to our custom-built Squid parent that was expecting ICP
connections only from the configured IP address of the Squid
(192.168.1.81). Squid is running on a host system with the
Hi Tek and Adrian,
I appreciate the suggestions. We have resolved our issue, which was
related to our custom-built Squid parent that was expecting ICP
connections only from the configured IP address of the Squid
(192.168.1.81). Squid is running on a host system with the IP
192.168.1.17
Hi Paul,
Paul Bertain wrote:
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/custo
On Mon, Sep 03, 2007, Paul Bertain wrote:
> Via: 1.1 squid-1.example .com:80 (squid/2.5.STABLE14)
You might consider upgrading to squid-2.6.STABLE16 when it comes
out.
> X-Forwarded-For: 208.106.5.39
> Cache-Control: max-age=259200
> Connection: keep-alive
>
> I think our Squid parent is not res
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
