Bug 23810 - [regression] globalization responseEncoding ignored (content-type charset utf-8)
Summary: [regression] globalization responseEncoding ignored (content-type charset utf-8)
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web ()
Version: master
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-10-14 06:45 UTC by etienne.champetier
Modified: 2017-01-19 21:09 UTC (History)
3 users (show)

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

testcase (532 bytes, application/download)
2017-01-19 21:09 UTC, Luis

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 23810 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:

Description etienne.champetier 2014-10-14 06:45:31 UTC

we have <globalization requestEncoding="utf-8" responseEncoding="utf-8"/> in our machine.config

instead of
content-type: text/html; charset=utf-8 (mono 3.2.7/3.2.8)
we only have
content-type: text/html

this break all accents ...

the culprit must be 3cc0e3fe3d33bb9dbd8357dd3430db7d507f4487 i think
Comment 1 etienne.champetier 2014-10-14 08:17:40 UTC
Comment 2 Bernhard Urban 2016-03-29 18:16:27 UTC
as discussed in the mentioned PR, this needs a test.
Comment 3 Luis 2017-01-19 21:09:25 UTC
Created attachment 19407 [details]

Attached a testcase.