Bug 34747 - HttpClient hangs with AutomaticDecompression enabled
Summary: HttpClient hangs with AutomaticDecompression enabled
Alias: None
Product: iOS
Classification: Xamarin
Component: BCL Class Libraries ()
Version: XI 8.9.x (iOS 8.3)
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-10-10 08:03 UTC by Grigory (Playtika)
Modified: 2017-07-25 13:46 UTC (History)
4 users (show)

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 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 Grigory (Playtika) 2015-10-10 08:03:14 UTC
I do many parallel http calls with enabled AutomaticDecompression on HttpClientHandler.

As a result - no responses on some of them.

Windows Phone 8 and Win32 works perfectly. Mono doesn't.

XI - (private Enterprise  8.9.1 build with ios9 hotfix)

I have no repro. Just tried on our production app.

Same on Android (latest stable build).
Comment 1 Grigory (Playtika) 2015-10-10 08:06:35 UTC
To be more clear. Without AutomaticDecompression everything works fine.
Comment 2 Marek Safar 2016-01-15 15:46:35 UTC
How you setup HttpClient and how do you run your parallel request would help to repro.
Comment 3 John Miller [MSFT] 2017-07-25 13:46:27 UTC
Because we have not received a reply to our request for more information, we are marking this issue as RESOLVED→NORESPONSE. If you are still encountering this issue on the latest Xamarin.iOS, please don’t hesitate to reopen the ticket with the requested information. Thanks!