New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 785209 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
█ krajshree@chromium.org
jinsuk...@chromium.org
█ sc00335...@techmahindra.com
█ susanjuniab@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Character set guessed wrong on 403 pages, with no way to recover

Reported by jidanni@gmail.com, Nov 15 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.30 Safari/537.36

Steps to reproduce the problem:
1. Browse http://k1019.jjvk.com/bdsn/

What is the expected behavior?
Can read something.

What went wrong?
A jumble of wrong charset chars.

Did this work before? N/A 

Chrome version: 63.0.3239.30  Channel: n/a
OS Version: 
Flash Version: 

In other browsers there is a button to change to try a different character set.

Perhaps because this page returns a HTTP 403, Chromium's character set detection was defeated.

Yes you can blame them for poor HTML, but then again there is no button to try another character set anymore.

Comment 1 by susanjuniab@chromium.org, Nov 16 2017

Cc: susanjuniab@chromium.org
Labels: Needs-Triage-M63 Needs-Feedback
jidanni@ Thanks for the issue.

Tested this issue on Ubuntu 14.04 using the latest Stable 62.0.3202.94 and Beta 63.0.3239.52 and unable to reproduce this issue.

1. Launched Chrome and navigated to the page  http://k1019.jjvk.com/bdsn/.
2. Opened the same on firefox and can see the same behavior as Chrome.
Attached are the screen shots for reference.

Request you to please check and update if we have missed anything from our end.

Also request you please specify the repro steps and expected behavior and a screen shot of the same will be helpful in further triaging of this issue.

Thanks..
785209_Chrome.png
180 KB View Download
785209_Firefox.png
60.6 KB View Download

Comment 2 by jidanni@gmail.com, Nov 16 2017 

YES, what you are seeing is the jumbled characters!! Bug confirmed!

OK, now in Firefox, please click the menu > more > text encoding > Unicode.

Now you will see the correct:
... 你好！

系統發生錯誤！403

已派訓練有素的猴子前往處理中！...

The problem is the user has no way to do that in Chromium anymore, as that control was removed as it was thought that Chromium would never guess wrong...
Project Member

Comment 3 by sheriffbot@chromium.org, Nov 16 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by sc00335...@techmahindra.com, Nov 17 2017

Cc: jinsuk...@chromium.org sc00335...@techmahindra.com
Components: -UI UI>Internationalization
Labels: Triaged-ET OS-Mac OS-Windows
Able to reproduce this issue on reported version 63.0.3239.30 and on latest canary 64.0.3271.0 using Ubuntu 14.04,Windows 10 and Mac 10.12.6 with steps mentioned in comment#0.

Removing of Encoding option in chrome is intended. For reference please check https://bugs.chromium.org/p/chromium/issues/detail?id=597488.

Maybe this Chrome-extension helps to set encoding options:
https://chrome.google.com/webstore/detail/set-character-encoding/bpojelgakakmcfmjfilgdlmhefphglae.

cc'ing jinsukkim@ from 597488 for further inputs on this.

Comment 5 by divya.pa...@techmahindra.com, Nov 23 2017 

jinsukkim@, could you please take a look at this issue

Comment 6 by jinsuk...@chromium.org, Nov 23 2017

Status: WontFix (was: Unconfirmed)
Please use the extension mentioned in #c4.

Comment 7 by jidanni@gmail.com, Nov 25 2017 

(Confirming that 403 has nothing to do with it:

# echo -e "HTTP/1.1 200 OK\\r\\n\\r\\n<!DOCTYPE html><html><head><title>test</title></head><body><p>測試</p></body></html>"|
nc -l -N -p 80
$ chromium http://localhost/index.html
)

Comment 8 by jinsuk...@chromium.org, Nov 27 2017

Cc: krajshree@chromium.org
 Issue 788429  has been merged into this issue.
►

Sign in to add a comment