[
https://issues.apache.org/jira/browse/TAP5-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040990#comment-14040990
]
Jochen Kemnade commented on TAP5-2344:
--------------------------------------
I'd say we just append {{;charset=utf-8}} to all text/* responses, especially
when sending out assets and modules. I'm aware that we *assume* that assets and
modules are saved as UT-8, but I wonder if we actually *require* it. I guess it
would be a good idea to do so.
> 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 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
