Hi Amos,
I'm still trying to configure login pass-through. Now, I'm using negotiate /
kerberos. On the frontend machine, I enabled login = PASSTHRU in the
cache_peer configuration line. As previously stated, the authentication is
present only on the parent machine.
The cache.log of my parent mach
On 22/11/2016 4:17 a.m., Eduardo Carneiro wrote:
>
> So, Amos, if I to use Negotiate/Kerberos or any basic auth, the PASSTHRU
> parameter will works for my purpose. That's right?
>
Yes, login=PASSTHRU should work for any auth scheme.
Amos
___
squid-u
Amos Jeffries wrote
> On 22/11/2016 1:33 a.m., Eduardo Carneiro wrote:
>> Hi all.
>>
>> Sorry if this is already answered here. But I couldn't find any clear
>> tips
>> about this topic.
>>
>> I'm using Squid 3.5.19 with dynamic content caching in a huge user base
>> (almost 10.000). Due to the l
On 22/11/2016 1:33 a.m., Eduardo Carneiro wrote:
> Hi all.
>
> Sorry if this is already answered here. But I couldn't find any clear tips
> about this topic.
>
> I'm using Squid 3.5.19 with dynamic content caching in a huge user base
> (almost 10.000). Due to the large number of requisitions, int
Subject: [squid-users] Authentication pass-through cache_peer
Hi all.
Sorry if this is already answered here. But I couldn't find any clear tips
about this topic.
I'm using Squid 3.5.19 with dynamic content caching in a huge user base (almost
10.000). Due to the large number of requisitions
Hi all.
Sorry if this is already answered here. But I couldn't find any clear tips
about this topic.
I'm using Squid 3.5.19 with dynamic content caching in a huge user base
(almost 10.000). Due to the large number of requisitions, internet access is
getting very slow.
So I decided to use cache_p
