Hello,
I wonder if Squid can pass different login/password to another, depending to an
ACL ?
I mean:
1) a client connected to Squid without any identification helper like ntlm,
basic, etc ...
2) an ACL like IP src, or browser, header, ... forward the request to an
another squid with a login/p
On 3/11/2016 9:47 p.m., FredB wrote:
> Hello,
>
> I wonder if Squid can pass different login/password to another, depending to
> an ACL ?
> I mean:
>
> 1) a client connected to Squid without any identification helper like ntlm,
> basic, etc ...
> 2) an ACL like IP src, or browser, header, ...
That is how I felt about it, since nothing in the changelog indicated anything
that would impact that. I'll switch back to the old version tonight, maybe the
client traffic that was inducing the entries that isn't trying anymore? I
don't have a good answer, I'll try the old version tomorrow an
> Authentication credentials represent and verify the identity of your
> proxy. That is a fixed thing so why would the credentials used to
> verify
> that static identity need to change?
I'm only speaking about users identities, not something like cache_peer
login=XXX
So each user must have is
Hi,
I installed squid v3.5.22 on windows and enabled with ssl_bump.
Now my issue is.
Web page is opening very slowly. For ex. www.google.com its taking more
than 30 seconds.
In cache log showing below warning
2016/11/03 17:45:16 kid1| helperOpenServers: Starting 1/8 'ssl_crtd'
processes
2016/11/03
