Issue 168 in serf: Problems with proxies with NLTM authentication

[se...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 168 by michael....@gmail.com: Problems with proxies with NLTM
authentication
https://code.google.com/p/serf/issues/detail?id=168

We use an integrated subversion client in out software and updated from
1.6.x to 1.8.x recently. We also use latest released version of serf, 1.3.8.
Everything is ok without proxies. But we made some tests with a proxy which
requires NTLM authentication and the checkout process breaks after a few
files with an "The handle is invalid" message. TortoiseSvn 1.8.10 is also
affected.

The invalid handle error results from a call to InitializeSecurityContext
in auth_spnego_sspi.c. I think, the problem is related to the fact, that
serf uses the same authentication context for proxies for all connections,
unlike the context for server authentication. NTLM is a multiphase
authentication protocol and the responses seam to overlap which leads to
problems.
We need to release our software soon, so I changed the code to store the
proxy authentication infos in the connection object as well and everything
works.
Could you please investigate it?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[se...@googlecode.com]

Updates:
Status: Accepted

Comment #1 on issue 168 by lieven....@gmail.com: Problems with proxies

with NLTM authentication
https://code.google.com/p/serf/issues/detail?id=168

Thanks for the report and suggestion on how to fix it, I'll look into it.