> -----Original Message----- > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Tuesday, January 19, 2010 11:23 AM > To: squid-users@xxxxxxxxxxxxxxx > Subject: Re: Issue with NTLM/Exchange in squid-3.0 > > Christian Koerner wrote: > > Hi list, > > > > I am investigating a problem with squid and Exchange at the moment. > > We are using a self-compiled squid-3.0.stable15 and people can not > > use Exchange OMA/OWA through the squid proxy. It does not display a > > login prompt, the page that is returned by Exchange shows a "HTTP > > Error 401.2". > > > > "Is this a problem with connection pinning > (http://wiki.squid-cache.org/Features/ConnPin), that has been > re-implemented in 3.1? Any help appreciated. > " > > That page did not quite make it clear. Connection pinning does not exist > at all in 3.0. You are looking at the direct result of that absence. Thanks Amos for your speedy reply. Sorry if it is not clear to me, but does it mean -as connection pinning does not exist in 3.0- access to OMA/OWA through squid 3.0 can not be realized? > If you can, use 3.1. Otherwise stick with 2.7. At worst please at least > use the latest 3.0 available, there are serious security issues in older > 3.0 releases. Thanks, I will take it in consideration for any further testing/usage. > PS. please do not use "dash dash space newline" in emails or news posts. > That is specific protocol syntax for end of message / start of digital > signature. You are right, forgot about that. > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21 > Current Beta Squid 3.1.0.15 Regards, Christian This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
