On 8/04/2014 8:51 p.m., Kinkie wrote: > This looks like a legitimate forwarding loop. What is your request > routing configuration? > cache_peer parent and never_direct are the most interesting lines on > top of my head. Configuration directive "via on" should make Squid catch and abort on the first cycle through the loop so you can debug where its happening much easier. We also see these loops with IP:port in the Host header with NAT "port forwarding". The NAT intercept *MUST* be done (only) on the Squid machine itself - it cannot be done by a separate router. Amos > > On Tue, Apr 8, 2014 at 8:15 AM, Dipjyoti Bharali wrote: >> Hi, >> >> I facing this peculiar issue with certain specific clients. When these >> clients connect to the proxy server, it goes for a toss until i reload the >> service. When examined through the log file, i get this same message >> everytime. >> >> /2014/04/02 09:00:17| WARNING: Forwarding loop detected for: >> GET / HTTP/1.1 >> Content-Type: text/xml; charset=Utf-16 >> UNICODE: YES >> Content-Length: 0 >> Host: 192.168.1.1:3128 >> Via: 1.0 hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg >> (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 >> hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), >> 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg >> (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 >> hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), >> 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg >> (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 >> hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), >> 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg >> (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 >> hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), >> 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 hindenberg >> (squid), 1.1 hindenberg (squid), 1.1 hindenberg (squid), 1.1 >> . >> . >> . >> . >> . >> . >> >> X-Forwarded-For: 192.168.1.74, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, >> 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, 192.168.1.1, . >> . >> . >> . >> . >> . >> . >> >> Cache-Control: max-age=5999400 >> Connection: keep-alive/ >> >> >> Please help. I have to reload every now and then, otherwise. For now i have >> disconnected those clients from the network >> >> >> *Dipjyoti Bharali* >> >> Skanray Technologies Pvt Ltd, >> Plot No. 15-17, Hebbal Industrial Area, >> Mysore - 570018 >> Cell Phone : +919243552011 >> Phone/Fax: +91 821 2415559/2403344 Extn: 310 >> >> ; www.skanray.com <http://www.skanray.com> >> >> *Please consider the environment before printing this email. * >> >> >> --- >> avast! Antivirus: Outbound message clean. >> Virus Database (VPS): 140407-0, 07-04-2014 >> Tested on: 08-04-2014 11:45:53 >> avast! - copyright (c) 1988-2014 AVAST Software. >> http://www.avast.com >> >> >> > > >
