ons 2007-06-27 klockan 13:57 +0200 skrev Joerg Schuetter: > request: > CONNECT keylink.ubs.com:443 HTTP/1.1 > User-Agent: Mozilla/4.0 (Windows 2003 5.2) Java/1.4.2_06 > Host: keylink.ubs.com > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Proxy-authorization: NTLM (~80 chars) Hmm.. no proxy-connection: keep-alive in the request. > reply: > HTTP/1.0 407 Proxy Authentication Required > Server: squid/2.6.STABLE5 > Date: Wed, 20 Jun 2007 08:25:31 GMT > Content-Type: text/html > Content-Length: 1321 > Expires: Wed, 20 Jun 2007 08:25:31 GMT > X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0 > Proxy-Authenticate: NTLM (~250 chars) > X-Cache: MISS from myhostname.domain.com > X-Cache-Lookup: NONE from myhostname.domain.com:3128 > Via: 1.0 myhostname.domain.com:3128 (squid/2.6.STABLE5) > Proxy-Connection: close And the connection gets closed here.. not good. What do the requests/replies look like when using Squid-2.5? Does things return to how they were if you back out the following patch? http://www.squid-cache.org/Versions/v2/2.5/bugs/squid-2.5.STABLE12-ntlm_nonpersistent.patch (apply with "patch -p1 -R <squid-2.5.STABLE12-ntlm_nonpersistent.patch") Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
