[rabbitmq-discuss] STOMP incompatibility upgrading 2.7 to 3.1: escaping colons in header values
matthias at rabbitmq.com
Wed May 22 12:28:55 BST 2013
On 22/05/13 01:41, Kevin Goess wrote:
> STOMP 1.0 allowed colons in header values, e.g.
...whereas the STOMP 1.1 spec explicitly forbids that.
> But this commit a couple months ago disallowed them in any stomp
> That seems like a mistake to me, but either way I'm calling it out
> here in case anybody else is travelling down the same road.
We use a single parser to parse all versions of STOMP. We don't want to
start parameterising the parser with the STOMP version - way too much
complexity and hassle. So the question is whether we could construct a
lenient parser that accepts unescaped colons in header values across all
STOMP versions w/o introducing any breakages. I have filed a bug to look
More information about the rabbitmq-discuss