Search squid archive

Re: Squid 3.2.1 Reverse Proxy. TCP_MISS/403 suddenly appearing for one cache peer.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Update:  I haven't changed anything yet but have noticed that it sometimes
works.  It's currently working perfectly but other times it stops working.

I think it's got something to do with the login/authorization.

I just logged in on 1 pc and it worked fine.  I then went to another PC with
a browser I never use (IE10) and entered invalid credentials to the nagios
login prompt.  This gave me access to the web console anyway!

So once any user at all has logged in successfully, anybody who tries to
access the page is already authenticated.  Why would this be happening?



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-2-1-Reverse-Proxy-TCP-MISS-403-suddenly-appearing-for-one-cache-peer-tp4661218p4661380.html
Sent from the Squid - Users mailing list archive at Nabble.com.




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux