[TAP5-2344] text assets (including modules and stacks) should assume a utf-8 charset, and incude ;charset=utf-8 in the response content type

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Labels: encoding
• Assignee: Howard Lewis Ship
• Reporter: Jochen Kemnade
• Created: 30/May/14 13:00
• Updated: 27/Aug/14 16:47
• Resolved: 27/Aug/14 16:18

Description

The Content-Type header sent for asset and module responses does not contain a charset specification. When they are loaded from within a page, browsers seem to assume that they have the same charset as the page, so as long as SymbolConstants.CHARSET is the same as the resource's charset, everything works fine. Changing the symbol value will cause the browser to use that to interpret the resonse and the result will probably be wrong.
When requesting the module/asset in a separate browser tab, is is interpreted as ISO-5559-1 (HTTP 1.1 default charset). That can be seen when starting the tapestry-core/app1 test app and navigating to http://localhost:8080/tapestry-core/modules/moment.js. All the special characters in the i18n section are broken.

Issue Links

• breaks: TAP5-2293 Closure minimizer produces invalid output on non-UTF-8 systems