Bug 33610 - StreamContent internal buffers are not reset property when using NTLM auth with POST method and HttpClient
Summary: StreamContent internal buffers are not reset property when using NTLM auth wi...
Alias: None
Product: iOS
Classification: Xamarin
Component: BCL Class Libraries ()
Version: XI 8.13 (C6 early alphas)
Hardware: Other Other
: --- normal
Target Milestone: Untriaged
Assignee: Martin Baulig
Depends on:
Reported: 2015-09-03 13:05 UTC by Jerome Laban
Modified: 2017-08-28 20:45 UTC (History)
6 users (show)

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

Repro and workaround (2.17 KB, text/plain)
2015-09-03 13:07 UTC, Jerome Laban

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 Developer Community or GitHub 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:

Description Jerome Laban 2015-09-03 13:05:57 UTC
With Xamarin.iOS on MacOS

When using NTLM auth with a POST request with a body, the internal buffers of StreamContent are not reset properly,  making the authenticated replay of the POST request body send a content-length of zero.

This issue is similar to https://bugzilla.xamarin.com/show_bug.cgi?id=30869, https://bugzilla.xamarin.com/show_bug.cgi?id=15213 and https://bugzilla.xamarin.com/show_bug.cgi?id=19119.

See the attached sample for a repro and potential workaround.
Comment 1 Jerome Laban 2015-09-03 13:07:59 UTC
Created attachment 12738 [details]
Repro and workaround
Comment 2 Rodrigo Kumpera 2015-09-03 13:20:14 UTC
Hi Martin,

Could you look at this one?
Comment 3 Martin Baulig 2016-11-11 10:03:35 UTC
Does this problem still exist?
Comment 4 Soeren Larsen 2016-11-17 08:04:34 UTC
I can confirm that this is still an issue and that we are experiencing it right now in our development.
Comment 5 Sebastien Pouliot 2016-11-22 02:20:03 UTC
Re-opening based on comment #4
Comment 6 John Miller [MSFT] 2017-07-26 18:34:44 UTC
Thanks so much for taking the time to submit this report! I’m unable to reproduce this issue using the latest Xamarin.iOS Please attach the following to help us reproduce this issue: 
-Detailed reproduction steps 
-Version information (Visual Studio → About Visual Studio menu) 
-Solution and projects that can be used to reproduce this
Comment 7 Vincent Dondain [MSFT] 2017-08-28 20:45:15 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!