[AMQNET-345] NMS.Stomp doesn't properly encode or decode header values according to the Stomp v1.1 spec

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.5.2, 1.6.0
• Component/s: Stomp
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 03/Nov/11 21:55
• Updated: 03/Nov/11 23:47
• Resolved: 03/Nov/11 23:47

Description

When connected to a Stomp v1.1 broker the client needs to dead with encoding and decoding of header values according to the spec.