[AMQ-6699] STOMP headers are not escaped when using WebSocket

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.14.5
• Fix Version/s: 5.15.0, 5.14.6
• Component/s: STOMP

Environment

Java SE Runtime Environment (build 1.8.0_102-b14)

• Assignee: Timothy A. Bish
• Reporter: Albertas Vyšniauskas
• Created: 09/Jun/17 10:31
• Updated: 14/Jun/17 20:05
• Resolved: 14/Jun/17 19:18

Description

When using STOMP over WebSockets, STOMP header values are not escaped in frames sent by ActiveMQ.

When the following frame is sent:

SEND
destination:/queue/test
escaped-header:one\ntwo\cthree

Hello World

ActiveMQ interprets escaped headers correctly, but does not escape them when sending own frames:

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

Correctly escaped frame should look like this:

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