[rabbitmq-discuss] rabbitmq-stomp 2.5.1 does not respect the spec wrt content-type

Lionel Cons lionel.cons at cern.ch
Tue Aug 9 13:08:28 BST 2011

I sent with STOMP a test message with a binary body to a RabbitMQ
2.5.1 broker and got back a garbaged text body.

More precisely, the sent message did not contain any content-type
header but the received one did contain "content-type:text/plain",
wrongly added by the broker. Some bytes from the sent message have
been replaced by the Unicode replacement character U+FFFD.

The STOMP 1.1 specification [1] contains:
 | If the content-type header is not set, the receiver SHOULD consider
 | the body to be a binary blob.

Could some Rabbit expert confirm whether this is indeed a bug or not?



[1] http://stomp.github.com/stomp-specification-1.1.html#Header_content-type

More information about the rabbitmq-discuss mailing list