[ROL-1226] Multi-byte charset pages are decoded incorrectly while the browser showing local cached pages

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0
• Component/s: User Interface - General
• Environment: Windows XP + IE 6.0 (Chinese version), Other OS and browsers may also apply although having not tested yet.; 3.0-dev (unreleased)
• Browser Version: IE 6.0
• Level of effort: 1
• Assignee: Anil Gangolli
• Reporter: Miles Huang
• Created: 04/Sep/06 17:09
• Updated: 08/Jan/14 04:40
• Resolved: 08/Sep/06 15:37

Description

The html content-Type meta info:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
is vital for browser decoding utf-8 encoded multi-byte charset correctly while showing local cached pages.
Without the meta info, the browser can show the page correctly when if it is send back from the server directly. The browser can get encoding indication from the HTTP response content-Type header.
When the browser show the same GET response later, it use the local cached page, hence there is no HTTP content-Type header. If the html meta info is also missing, the browser will know nothing about the actual page encoding. The browser may guess the page encoding as local codepage such as GB18030, Shift-JIS, etc (depending on the OS and browser environment), leading chaotic outputs.