Unexpected char in header, : but its ok! read on about rabbitmq-stomp HOT 4 CLOSED

According to the stomp 1.1 spec http://stomp.github.io/stomp-specification-1.1.html you need to escape colons in your header values by changing them to "\c"

from rabbitmq-stomp.

I think the spec should have been a bit more intelligent in the definition, and had an exception if the header value is inside quotes. Like most other specs.... maybe thats why active/apollo took it upon themselves not to be so ruthlessly strict, when logically, HEADER:"content" looks ok to humans.

Sometimes servers should go beyond specs, if specs are not bullet proof. Having said that, yes - its trivial to fix active current client code to adjust if need be.

And specifically, the stomp-js module does this ... and handles this multi colon case.
It would take extra effort to abort the extra colon in this case.

        one_header = headers_split[i].split(':');
        if (one_header.length > 1) {
            header_key = one_header.shift();
            header_val = one_header.join(':');
            these_headers[header_key] = header_val;
        }

from rabbitmq-stomp.

We have had a bug open to investigate this issue for a while and we're looking at making our 1.1 parsing more 'permissive' with regards this issue. Feel free to drop by the #rabbitmq channel on freenode if you wish to discuss this further. In the meanwhile, this issue will be closed once we've merged a fix (or decided otherwise). :)

from rabbitmq-stomp.

We will try to make header parsing more permissive but according to the spec, it is not a server issue.

from rabbitmq-stomp.