Hi all,
We currently have a setup with proxies that use NTLM authentication
(we hope to upgrade to kerberos in the future) and based on the
username send the user to one of several parent proxies, to improve
caching we would like to instead route all traffic through one proxy
that is heavily optimi
2011/10/18 E.S. Rosenberg :
> Hi all,
> We currently have a setup with proxies that use NTLM authentication
> (we hope to upgrade to kerberos in the future) and based on the
> username send the user to one of several parent proxies, to improve
> caching we would like to instead route all traffic th
On Tue, 18 Oct 2011 13:53:18 +0200, E.S. Rosenberg wrote:
Hi all,
We currently have a setup with proxies that use NTLM authentication
(we hope to upgrade to kerberos in the future) and based on the
username send the user to one of several parent proxies, to improve
caching we would like to instea
2011/10/19 Luis Daniel Lucio Quiroz :
> 2011/10/18 E.S. Rosenberg :
>> Hi all,
>> We currently have a setup with proxies that use NTLM authentication
>> (we hope to upgrade to kerberos in the future) and based on the
>> username send the user to one of several parent proxies, to improve
>> caching
2011/10/19 Amos Jeffries :
> On Tue, 18 Oct 2011 13:53:18 +0200, E.S. Rosenberg wrote:
>>
>> Hi all,
>> We currently have a setup with proxies that use NTLM authentication
>> (we hope to upgrade to kerberos in the future) and based on the
>> username send the user to one of several parent proxies,
On 20/10/2011 18:11, E.S. Rosenberg wrote:
> On the whole I just need the backend to know the username, or what
> 'browsing plan' the session is using, sometimes plans are also
> determined based on src IP (ie. certain stations aren't allowed to
> browse no matter who's logged in, or are supposed t
2011/10/20 Ed W :
> On 20/10/2011 18:11, E.S. Rosenberg wrote:
>> On the whole I just need the backend to know the username, or what
>> 'browsing plan' the session is using, sometimes plans are also
>> determined based on src IP (ie. certain stations aren't allowed to
>> browse no matter who's logg
