Bug 18685 - The content encoding response header on Mono returns "gzip" or "deflate" even when automatic decompression is set to true on the request
Summary: The content encoding response header on Mono returns "gzip" or "deflate" even...
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web (show other bugs)
Version: 3.2.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-03-31 19:16 UTC by Gustavo Guerra
Modified: 2014-03-31 19:16 UTC (History)
1 user (show)

Tags:
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 for Bug 18685 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Gustavo Guerra 2014-03-31 19:16:21 UTC
In .NET when automatic decompression is on, the "gzip" or "deflate" values are removed from the content encoding header, as that encoding has already been processed. This slight difference is enough to cause very weird bugs between the two platforms
Comment 1 Gustavo Guerra 2014-03-31 19:16:53 UTC
This was caught on the Travis build of FSharp.Data