Search squid archive

Re: NTLM Authentication and Connection Pinning problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 10 Feb 2010 12:53:16 -0600, Jeff Foster <jfoste@xxxxxxxxx> wrote:
> 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.
> The initial couple of requests are OK but after that the input TCP
> connection to output TCP
> connect is broken. The requests are changing output bound TCP
> connections. This is breaking
> the NTLM authentication handshake.
> 
> I can supply my squid configuration files if needed. I do have NTLM
> authentication enabled
> in both configurations.
> 
> 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

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux