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
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.
With Xamarin.iOS 18.104.22.168 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.
Created attachment 12738 [details]
Repro and workaround
Could you look at this one?
Does this problem still exist?
I can confirm that this is still an issue and that we are experiencing it right now in our development.
Re-opening based on comment #4
Thanks so much for taking the time to submit this report! I’m unable to reproduce this issue using the latest Xamarin.iOS 10.12.0.14. 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
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!