[ https://issues.apache.org/jira/browse/AMQ-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706726#comment-14706726 ]
ASF GitHub Bot commented on AMQ-5939: ------------------------------------- GitHub user kernelmode opened a pull request: https://github.com/apache/activemq/pull/140 fix for AMQ-5939 See https://issues.apache.org/jira/browse/AMQ-5939 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Cinimex-Informatica/activemq AMQ-5939 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq/pull/140.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #140 ---- commit 7b41bf21758623755504773ac51300dc307c7b56 Author: Kirill Dubovikov <dubovikov.kir...@gmail.com> Date: 2015-08-21T13:22:48Z fix for AMQ-5939 ---- > ActiveMQ REST GET request is always encoded in ISO-8859-1 > --------------------------------------------------------- > > Key: AMQ-5939 > URL: https://issues.apache.org/jira/browse/AMQ-5939 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.12.0 > Reporter: Kirill Dubovikov > Priority: Minor > > ActiveMQ REST protocol does not support encodings other than ISO-8859-1. > 1) response.setContentType is called after response.getWriter - this > contradicts servlet specification, so setContentType does not work at all > 2) Content-Type header for the GET response is hardcoded inside > MessageServlet class > I've changed the class so that Content-Type header is being read from > request. This way users now can specify message body encoding through > Content-Type header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)