Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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:
Thanks for the pull request and the included tests.