Re: [squid-users] NTLM Authentication and Connection Pinning problem

>> There appears to be a problem with the connection pinning in both
>> versions squid-2.7.stable7 and
>> squid-3.1.0.7. I have some network captures that show the client
>> (IE6) creating multiple TCP
>> connections to the squid proxy and the proxy creating multiple TCP
>> connections to an IIS server.
 ....
>> I have tcpdump traces for both versions available.
>>
>> In the 3.1 dump summary, note that the client packet 207 is the server
>> packet 210.
>> The server should be on port 37159 and it is on port 37161.
>>
>> Can a developer look at this?
>
> There are quite a few pinning issues resolved since 3.1.0.7 (beta) was
> released.
> Try 3.1.0.16 beta.
>
> Amos
>

Sorry I mis-typed, I am running version 3.1.0.16.

Not sure how connection pinning works. Does it tie a client TCP socket
to an upstream TCP socket? Or does it tie a client URL to an upstream
socket?

Jeff F>
Received on Thu Feb 11 2010 - 14:30:11 MST