In the log, the exactly same sequence, on w7 it hangs, on xp it continues : ....:::::::::::::::::: Win7 2012/05/14 10:14:15.090| ctx: enter level 0: 'https://mail.x.fr/rpc/rpcproxy.dll?fqdn_exchange_server:6002' 2012/05/14 10:14:15.090| HTTP Server local=ip_squid:49014 remote=ip_exchange_server:443 FD 12 flags=1 2012/05/14 10:14:15.090| HTTP Server REPLY: --------- HTTP/1.1 200 OK Date: Mon, 14 May 2012 10:15:09 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: application/rpc Content-Length:20 Connection: Keep-Alive ---------- 2012/05/14 10:14:15.091| ctx: exit level 0 2012/05/14 10:14:15.091| The reply for RPC_OUT_DATA https://mail.x.fr/rpc/rpcproxy.dll?fqdn_exchange_server:6002 is 1, because it matched 'all' 2012/05/14 10:14:15.091| HTTP Client local=ip_squid:443 remote=ip_wan_client:51556 FD 11 flags=1 2012/05/14 10:14:15.091| HTTP Client REPLY: --------- HTTP/1.1 200 OK Date: Mon, 14 May 2012 10:15:09 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: application/rpc Content-Length: 20 X-Cache: MISS from mail.x.fr Via: 1.1 mail.x.fr (squid/3.2.0.17-20120415-r11555) Connection: keep-alive ---------- 2012/05/14 10:14:15.092| FilledChecklist.cc(100) ~ACLFilledChecklist: ACLFilledChecklist destroyed 0x8dff1c8 2012/05/14 10:14:15.092| ACLChecklist::~ACLChecklist: destroyed 0x8dff1c8 And it hangs there ... ....:::::::::::::::::: Win7 ....:::::::::::::::::: WinXP 2012/05/11 13:22:33.452| ctx: enter level 0: 'https://mail.x.fr/rpc/rpcproxy.dll?fqdn_exchange_server:6002' 2012/05/11 13:22:33.452| HTTP Server local=ip_squid:46111 remote=ip_exchange_server:443 FD 12 flags=1 2012/05/11 13:22:33.452| HTTP Server REPLY: --------- HTTP/1.1 200 OK Date: Fri, 11 May 2012 13:23:13 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: application/rpc Content-Length:20 Connection: Keep-Alive ---------- 2012/05/11 13:22:33.452| ctx: exit level 0 2012/05/11 13:22:33.452| The reply for RPC_OUT_DATA https://mail.x.fr/rpc/rpcproxy.dll?fqdn_exchange_server:6002 is 1, because it matched 'all' 2012/05/11 13:22:33.452| HTTP Client local=ip_squid:443 remote=ip_wan_client:1162 FD 11 flags=1 2012/05/11 13:22:33.452| HTTP Client REPLY: --------- HTTP/1.1 200 OK Date: Fri, 11 May 2012 13:23:13 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: application/rpc Content-Length: 20 X-Cache: MISS from mail.x.fr Via: 1.1 mail.x.fr (squid/3.2.0.17-20120415-r11555) Connection: keep-alive ---------- 2012/05/11 13:22:33.454| FilledChecklist.cc(100) ~ACLFilledChecklist: ACLFilledChecklist destroyed 0x8dccea8 2012/05/11 13:22:33.454| ACLChecklist::~ACLChecklist: destroyed 0x8dccea8 2012/05/11 13:22:33.512| HTTP Client local= ip_squid:443 remote=ip_wan_client:1160 FD 8 flags=1 2012/05/11 13:22:33.512| HTTP Client REQUEST: --------- RPC_IN_DATA /rpc/rpcproxy.dll? fqdn_exchange_server:6002 HTTP/1.1 Accept: application/rpc User-Agent: MSRPC Host: mail.x.fr Content-Length: 1073741824 Connection: Keep-Alive Cache-Control: no-cache Pragma: no-cache ................ and that continues ... ....:::::::::::::::::: WinXP And no more infos why It's hanging Clem -----Message d'origine----- De : Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Envoyé : lundi 14 mai 2012 12:17 À : squid-users@xxxxxxxxxxxxxxx Objet : Re: https analyze, squid rpc proxy to rpc proxy ii6 exchange2007 with ntlm On 14/05/2012 7:42 p.m., Clem wrote: > Hi Amos, > > Thx for your answer. > > I'm still searching why my solution works with XP and only when I change 2 settings (lanmanager level, and disable msstd) on Windows7. > So I use a cache.log with debug options to analyze more precisely, to see the difference between these two OS. > > When that doesn’t work on windows7, the request is "stuck" on RPC_OUT_DATA with a 200 success HTTP, sort of time out, and no infos, I've sniffed all I can, and nothing ... > > The only thing I can see in logs is the cookie header and the pragma "sessionid" on windows7. In XP there is no cookie header and pragma is "no-cache" only, no other values. Hmm. Hanging usually means something somewhere is waiting expecting data somewhere. Could be an HTTP object sent with wrong body size. Or another side channel somewhere expected to be working but not operating. Things like unexpected side channels seem to happen a lot with MS software IME. >> Also, request_header_replace requires a previous "request_header_access deny ..." giving permission to remove existng header details before it can replace the content. > Thx for this info, I'll test it today. > If I write : > request_header_access Cookie deny all > request_header_replace Cookie none > > Does this disable cookie header ? It erases all existing Cookie values and creates the header "Cookie: none". Amos
