[
https://issues.apache.org/jira/browse/WW-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243003#comment-17243003
]
Lukasz Lenart commented on WW-5100:
-----------------------------------
It works but for actions, that JavaScript request isn't an action and that's
why it wasn't applied. I tested applying default encoding based on
{{struts.i18n.encoding}} to the HttpServletResponse for any request/response
and it works, but this was also applied to non-text responses (*.gif, *.png,
*.pdf) which can break something else - I need to read/investigate this deeper.
> incorrect content-type behavior after upgrading to struts 2.5.*
> ---------------------------------------------------------------
>
> Key: WW-5100
> URL: https://issues.apache.org/jira/browse/WW-5100
> Project: Struts 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5.22
> Environment: Windows
> Reporter: xue
> Priority: Blocker
> Labels: features
> Fix For: 2.6
>
>
> 1. After upgrading from struts 2.3.* to struts 2.5.22, the content-type
> header of the response will changed to
> "application/script;charset=charset=ISO-8859-1" which was
> "application/script" in struts 2.3.4.
> Which caused our application failed, as it should be default as UTF-8.
> 2. When specifying the charset in Content-type with struts filer, the
> Content-Type is change to "application/script;charset=charset=UTF-8", but
> UTF-8 encoded file can still not be loaded correctly.
> It is blocker issue, which fails our application after upgrading.
> Please help to explain and provide solution, thanks,
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
