That’s a very good point ... Well that’s good to know. I’ll keep experimenting with the http_access rules until I get it right.
Thanks Amos On 23 Jan 2014, at 7:06 pm, Amos Jeffries <squ...@treenet.co.nz> wrote: > On 23/01/2014 4:46 p.m., Dan Charlesworth wrote: >> Hi folks >> >> I’m running a Squid 3.4.2 instance which has both intercepting >> http_ports and explicit ones. We use proxy_auth on the explicit >> connections and use myportname ACLs to bypass all the auth-related >> stuff on the intercepting ports. This seems to work just fine. >> >> However, for EVERY SINGLE intercepted request we’re now getting this >> NOTICE printed into the cache.log. Very annoying and unnecessary; if >> the system simply wants to warn me of this incompatibility, isn’t >> once enough? During startup perhaps? > > That message is only printed when the auth ACL is actively tested for an > intercepted requests credentials. Apparently your myportname ACL test is > not working and your clients are being faced with a lot of unnecessary > rejections. Would you (or I) have been able to identify the cause easily > if it was only printed once? > > NP: For a working config it should never appear at all. > >> >> So, assuming there is isn’t some magic http_access hierarchy that >> will prevent this, am I going to need a patch or something? > > Yep, there should be a magic heirarchy that does that. > > Amos
