What is a forwarding loop?
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. Forwarding loops are detected by examining the Via request header. Each cache which “touches” a request must add its hostname to the Via header. If a cache notices its own hostname in this header for an incoming request, it knows there is a forwarding loop somewhere. NOTE: Squid may report a forwarding loop if a request goes through two caches that have the same visible_hostname value. If you want to have multiple machines with the same visible_hostname then you must give each machine a different unique_hostname so that forwarding loops are correctly detected. When Squid detects a forwarding lo
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 transparent 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. Forwarding loops are detected by examining the Via request header. Each cache which “touches” a request must add its hostname to the Via header. If a cache notices its own hostname in this header for an incoming request, it knows there is a forwarding loop somewhere. NOTE: A pair of caches which have the same visible_hostname value will report forwarding loops. When Squid detects a forwarding loop, it is logged to the cache.log file with the recieved Via header. From this header you can determine which cache (the last in the list) forwarded the request to you. One way to reduce forwarding loops
