I think I'm getting my head around this now, but I don't know what the solution is yet. The external IP of the squid box is also the public IP of the sites it's redirecting. All the redirected machines are on our internal network. I am of course using the virtual directive, as shown in the config file I posted. Surely there's a standard way of getting around this difficulty. Regards, Paul On Thu, 2005-03-10 at 16:58 +1300, Paul Dorman wrote: > On Wed, 2005-03-09 at 10:45 +0100, Henrik Nordstrom wrote: > > On Wed, 9 Mar 2005, Paul Dorman wrote: > > > > > So Squid is denying POST attempts. I've tried all sorts of things but > > > always have the same result. > > > > I don't see any obvious reasons from your description. > > > > > What am I missing here? I can't see anything about this mentioned in > > > FAQs or on Google, but I'm sure it's something really simple I've > > > missed. > > > > The Squid FAQ on how to debug access controls may help... > > > > Regards > > Henrik > > Yeah, it does. I have: > > 2005/03/10 16:56:55| WARNING: Forwarding loop detected for: > POST /user/login HTTP/1.0 > Host: www.public.domain > User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) > Gecko/20050210 Firefox/1.0 (Debian package 1.0+dfsg.1-6) > Accept: text/xml,application/xml,application/xhtml > +xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 > Accept-Language: en-us,en;q=0.5 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Referer: http://www.public.domain/ > Cookie: eZSESSIDbiotech=977a648c2964b7a946f07f888a3a1ec7 > Content-Type: application/x-www-form-urlencoded > Content-Length: 84 > Via: 1.1 squid.internal.cwa.co.nz:80 (squid/2.5.STABLE8) > X-Forwarded-For: 203.96.59.39 > Cache-Control: max-age=259200 > Connection: keep-alive > > How do I work around this? > > Cheers, > Paul > >
