Bug 30081 - HttpResponseHeaders is missing headers on Android
Summary: HttpResponseHeaders is missing headers on Android
Status: RESOLVED ANSWERED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Net.Http ()
Version: 4.2.0 (C6)
Hardware: PC Windows
: Normal normal
Target Milestone: Untriaged
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2015-05-14 12:32 UTC by Corey Sunwold
Modified: 2017-09-04 22:29 UTC (History)
6 users (show)

Tags: XATriaged
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 ANSWERED

Comment 7 Marek Safar 2016-09-02 11:00:07 UTC
The woot url is no longer working. Could you provide working version of it?
Comment 8 David Hathaway 2016-09-02 15:01:44 UTC
This same issue existed in ModernHttpClient (on Android).  I fixed it there, and made a pull request.  You can see the commit here for reference.

https://github.com/dwhathaway/ModernHttpClient/commit/5cf4a2d79f65a38d3747cdfb8bf64614578eb6ea

I can reach out to the customer to see if they have another sample URL that can be hit, or if we'll have to mock something up.
Comment 9 Marek Safar 2017-09-04 22:29:42 UTC
It seems the issue has been fixed already