[MAGNOLIA-200] Cache html has no character encoding Created: 21/Nov/04 Updated: 23/Jan/13 Resolved: 16/Aug/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Bug | Priority: | Major |
| Reporter: | Massimiliano Segreto | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux + jsdk 1.4.2_06 |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
The problem is with the cached html contents. 1) Save a paragraph with accented character (èéiàòù) 2) Publish the page. This invalidate the cache on the public instance. 3) Go to te public instance and browse the page. The first time you get the right characters on the page shown. If you look at the http header you will find: 4) Clear the browser cache, navigate somewhere and then back to the page, or reload the page. You got some strange character instead of the original accented, depending on the platform/browser you use. The problem is: the content from cache is served compressed (gzip), without the original character set. The http header will be: Workarounds I have found so far: 1) Disable cache, with impact on performance but with flexible character encoding 2) Keep the cache enabled but "hardcode" character encoding in Config value: text/html;charset=ISO-8859-1 so every html content will be served with ISO-8859-1 character encoding. |