Bug 27214 - NTLM Authentication fails when KeepAlive == false
Summary: NTLM Authentication fails when KeepAlive == false
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Net.Http ()
Version: 3.12.0
Hardware: PC All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-02-19 09:25 UTC by Lukasz Kulisz
Modified: 2015-02-20 11:21 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Lukasz Kulisz 2015-02-19 09:25:36 UTC
NTLM requires connection to be maintained after successful authentication. 

At the moment, when client sets KeepAlive to false on an instance of HttpWebRequest, then the request will fail with 401 error, because after the successful handshake connection will be closed. This happens, because HttpWebRequest always sets 'Connection: Close' header when KeepAlive == false. 

.NET on Windows omits this header in the second step of NTML auth, even when KeepAlive is set to false.

Setting KeepAlive to false may help when connecting through certain types of proxies. 

I have implemented a simple fix for this issue along with updated tests, and submitted it as a pull request:
https://github.com/mono/mono/pull/1578
Comment 1 Miguel de Icaza [MSFT] 2015-02-20 11:21:01 UTC
Thanks for the pull request and the included tests.