[
https://issues.apache.org/jira/browse/WW-5100?focusedWorklogId=523168&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-523168
]
ASF GitHub Bot logged work on WW-5100:
--------------------------------------
Author: ASF GitHub Bot
Created on: 11/Dec/20 12:12
Start Date: 11/Dec/20 12:12
Worklog Time Spent: 10m
Work Description: coveralls commented on pull request #456:
URL: https://github.com/apache/struts/pull/456#issuecomment-743158711
[](https://coveralls.io/builds/35637301)
Coverage increased (+0.003%) to 49.779% when pulling
**73dbe5b5954c58c23b752ac28787c06f094d873a on
WW-5100-character-encoding-on-response** into
**7840fa13335323b19ce03dc6b597b45808155282 on master**.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 523168)
Time Spent: 20m (was: 10m)
> 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
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
