Unfixable garbled text if charset= in HTTP headers is incorrect
Reported by
spix...@gmail.com,
Jan 9 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Example URL: http://fi.muny.cz/data/PA159/PA159-pa159-16-12-2014-predtermin.txt Steps to reproduce the problem: Open text file What is the expected behavior? windows encoding What went wrong? it had unicode encoding instead of windows encoding Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? No Mozilla Firefox, Edge Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 Chrome there is not any character encoding option anymore, so I have to use other browsers, thank you very much for it
,
Jan 10 2017
,
Jan 10 2017
Related: issue 597488 I've tried the suggested "Set Character Encoding" [1] extension from that thread but it didn't process text/plain content type. I've reported the issue to the developers so hopefully they'll fix it since it's trivial (I know since I've modified their extension locally). [1]: https://chrome.google.com/webstore/detail/set-character-encoding/bpojelgakakmcfmjfilgdlmhefphglae
,
Jan 11 2017
Able to reproduce this issue on Windows-10 and Mac OS 10.12 using chrome latest stable M55-55.0.2883.87. Observed the text file is not encoded properly with expected content. No issues observed on Ubuntu 14.04. This issue is observed on chrome previous version of M35-35.0.1849.0 as well, Hence marking it as untriaged. Thanks!
,
Jan 11 2017
I believe this is "working as intended" following the removal of the character encoding selection option. See issue 597488 Comment #3 is very helpful suggesting workarounds, although as noted they are as yet incomplete.
,
Jan 11 2017
FYI, the server is sending the data with following HTTP header which confuses Chrome: Content-Type: text/plain; charset=UTF-8
,
Feb 15 2017
,
Feb 15 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Jan 10 2017