Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Encoding issue when html meta charset differs from HTTP header Content-Type charset
See original GitHub issueWhen crawling a website which respond using HTTP header
Content-Type: "text/html; charset=windows-1252"
And HTML contains :
<meta charset="utf-8">
We end up with accented characters being badly encoded because the real encoding is windows-1252 but while parsing the DOM we are using UTF8
An other issue seems to appear with charset not being detected when there is a space juste after the semi colon.
In MimeType.cs > GetParameter(String key) method, the StartsWith should take into account spaces, or the variable _params should be trimmed in the ctor ?.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Which version are you using? This should have been fixed (as a sideeffect) in #282 (see PR #284).
Will be available in the next release, see PR #299.