I am a programmer. I recently added NTLM authentication support to the
Chromium browser, and I'm working with a Privoxy 3.0.10 user on an NTLM
authentication problem to his company proxy.
Note: although I found old bugs on Privoxy's NTLM authentication problems:
I have to open a new bug because I can't add a comment to those old bugs.
My investigation found pretty much what was reported in bug ID: 1760018,
that Privoxy adds the "Connection: close" header to the proxy's 407 response
that contains the proxy's NTLM challenge.
The Chromium browser respects the "Connection: close" header, so it
closes the old connection and opens a new one to send its response to
the NTLM challenge to the proxy. Since NTLM challenge-response must
proceed on a keep-alive connection, the authentication fails.
I made an experimental change to Chromium so that it would ignore the
"Connection: close" header that Privoxy added and leave the connection
open, and NTLM authentication to the proxy succeeded. This experiment
shows that when Privoxy adds the "Connection: close" header, it doesn't
mean it -- Privoxy won't close the connection if the browser leaves the
I'd really like to find a way to fix this bug while respecting the HTTP
"Connection: close" header.
Can Privoxy detect that NTLM authentication is in progress and not
add the "Connection: close" header?
Alternatively, is there a configuration option to prevent Privoxy from
adding the "Connection: close" header?
Thank you for your help.