On 26/01/2012 4:50 a.m., Clem wrote:
Amos,
Can you tell me if there'll be soon a revision of 3.2 beta for fixing the
problem with ntlm auth via rpc over https (outlook anywhere) ?
There is another beta package scheduled to go out next weekend (early Feb).
I'm not sure what the "doesn't work" problem you are seeing is exactly
happening to say whether it is fixed by that package.
Have you tried:
* the latest 3.1 release? the statusIfComplete message you reported
might be a sign that the RPC method is hitting bug 3398 which was fixed
in 3.1.17 and later.
* or the current 3.2 beta daily bugfix snapshot? more HTTP/1.1
persistent connection problems are fixed there than in 3.1
* enabling persistent connections to both servers and clients in Squid?
* and HTTP/1.1 features to proxies in the MS client software?
If all else fails have you tried viewing the packets being sent on the
client-squid and squid-server connections to see what is breaking?
Amos
Thanks, regards
Clémence
-----Message d'origine-----
De : cl00m [mailto:clemfree@xxxxxxx]
Envoyé : mardi 24 janvier 2012 15:55
À : squid-users@xxxxxxxxxxxxxxx
Objet : Re: NTLM auth for RPC over HTTPS to outlook everywhere
Please, help ...
I'll have to find another solution if squid doesn't work with NTLM auth for
rpc over https to outlook anywhere...
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/NTLM-auth-for-RPC-over-HT
TPS-to-outlook-everywhere-tp4315913p4323954.html
Sent from the Squid - Users mailing list archive at Nabble.com.
