[
https://issues.apache.org/jira/browse/TAP5-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-2344:
---------------------------------
Affects Version/s: 5.4
> Asset/module responses are sent without charset
> -----------------------------------------------
>
> Key: TAP5-2344
> URL: https://issues.apache.org/jira/browse/TAP5-2344
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Labels: encoding
>
> 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 utf-8, everything works fine. Changing the symbol
> value will probably cause responses to be read with the wrong charset.
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
