Change encoding in AMQ Classic 6.1.8 REST Connection
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing queue retrieval through the REST API with Cyrillic content and inspect the response Content-Type and charset. Review jetty.xml and the REST response path, including handling of the Accept header; done means messages retain Cyrillic characters and the response is served with UTF-8 rather than ISO-8859-1.
Written by the indexing model from the issue text.
Description
Hi,
I am using ActiveMQ Classic in version 6.1.8 and connect via. REST API to the AMQ Broker. When retrieving messages from a queue, the message is encoded using ISO-8859-1 (Latin).
Is there a way to change this? I've already tried patching the jetty.xml file, but that didn't work. Right now, I'm having an issue where, for example, Cyrillic messages are being transmitted as ???? due to the incorrect encoding.
Even a request with the Accept header set to Accept: application/xml;charset=UTF-8 does not work. The response is always
Content-Type: text/plain;charset=iso-8859-1
Thanks and kind regards,
trxg19
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1.5k
- Avg merge
- 14h 42m
- Merged PRs (30d)
- 85
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/activemq
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/activemq#2558 · 2 comments ·
Maintainers usually reply within 1 day
-
Stale
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/activemq#1999 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
apache/activemq#1871 · 2 comments ·
Maintainers usually reply within 1 day
-
Topic expiry task loads the whole JDBC topic store into the heap on PostgreSQL (AMQ-6067 fix is ineffective with pgjdbc)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/activemq#2630 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
team:Lumberjack
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenLiberty/open-liberty#35998 ·
Maintainers usually reply within 1 day
-
[BUG] SQS SendMessageBatch accepts more than 10 entries instead of TooManyEntriesInBatchRequestOpen
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
floci-io/floci#5319 · 1 comment ·
Maintainers usually reply within 1 day
-
Bug QWP
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100