[
https://issues.apache.org/jira/browse/AMQ-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albertas Vyšniauskas updated AMQ-6699:
--------------------------------------
Attachment: stomp-over-websocket-escape.patch
Patch with test and fix.
> STOMP headers are not escaped when using WebSocket
> --------------------------------------------------
>
> Key: AMQ-6699
> URL: https://issues.apache.org/jira/browse/AMQ-6699
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.14.6
> Environment: Java SE Runtime Environment (build 1.8.0_102-b14)
> Reporter: Albertas Vyšniauskas
> Priority: Minor
> Attachments: stomp-over-websocket-escape.patch
>
>
> When using STOMP over WebSockets, STOMP header values are not escaped in
> frames sent by ActiveMQ.
> When the following frame is sent:
> {quote}
> SEND
> destination:/queue/test
> escaped-header:one\ntwo\cthree
> Hello World
> {quote}
> ActiveMQ interprets escaped headers correctly, but does not escape them when
> sending own frames:
> {quote}
> MESSAGE
> expires:0
> destination:/queue/test
> subscription:12345
> priority:4
> escaped-header:one
> two:three
> message-id:ID:-50091-1497003246573-3:1:-1:1:1
> timestamp:1497003247783
> Hello World
> {quote}
> Correctly escaped frame should look like this:
> {quote}
> MESSAGE
> expires:0
> destination:/queue/test
> subscription:12345
> priority:4
> escaped-header:one\ntwo\cthree
> message-id:ID\c-50091-1497003246573-3\c1\c-1\c1\c1
> timestamp:1497003247783
> Hello World
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
