Ralf Hildebrandt wrote:
We're using a
intranet -> squid -> Dansguardian -> squid -> Internet
setup to filter the traffic for viruses
This must be the cause for this warning:
Aug 27 23:18:46 proxy-cvk-2 squid[27921]: WARNING: Forwarding loop detected
for: Client: 127.0.0.1 http_port: 127.0.0.1:8888 GET
http://127.0.0.1/squid-internal-periodic/store_digest HTTP/1.0^M Accept:
application/cache-digest^M Accept: text/html^M Host: 127.0.0.1:3129^M Via: 0.0
wlan-proxy.charite.de:3128 (squid/2.6.STABLE3), 1.0
proxy-cvk-2-nocache.charite.de:8888 (squid/2.6.STABLE3)^M X-Forwarded-For:
unknown, unknown, 127.0.0.1^M Cache-Control: max-age=259200^M Connection:
keep-alive^M X-Forwarded-For: unknown, unknown, 127.0.0.1^M ^M
Aug 27 23:18:46 proxy-cvk-2 squid[27916]: temporary disabling (Not Found)
digest from 127.0.0.1
How can I prevent the internal stuff from being forwarded to the
parent_proxy?
Hello Hildebrand,
A forwarding loop is when a request passes through one proxy more than
once. You can get a forwarding loop if
* a cache forwards requests to itself. This might happen with
interception caching (or server acceleration) configurations.
* a pair or group of caches forward requests to each other. This can
happen when Squid uses ICP, Cache Digests, or the ICMP RTT
database to select a next-hop cache.
Thanks,
Visolve Squid Team
www.visolve.com/squid/
