[ https://issues.apache.org/jira/browse/AMQ-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705834#comment-15705834 ]
ASF subversion and git services commented on AMQ-5939: ------------------------------------------------------ Commit f888cc2729832c6c71f0da9b5586d731e7a41648 in activemq's branch refs/heads/master from [~davsclaus] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=f888cc2 ] AMQ-5939: ActiveMQ REST GET request is always encoded in ISO-8859-1. Thanks to Kirill Dubovikov for the patch. This fixes 140. > 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 > Components: webconsole > Affects Versions: 5.12.0 > Reporter: Kirill Dubovikov > Assignee: Christopher L. Shannon > Priority: Minor > Fix For: 5.15.0 > > > 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)