[rabbitmq-discuss] rabbitmq-stomp 2.5.1 does not respect the spec wrt content-type
Lionel.Cons at cern.ch
Tue Aug 9 15:40:01 BST 2011
I confirm that my test message did include a content-length header and no content-type. It should have been treated as binary.
Even if the spec indeed uses SHOULD for this matter, I consider it bad practice to add something to the message that can be incorrect.
From: Steve Powell [mailto:steve at rabbitmq.com]
Sent: Tuesday, August 09, 2011 4:08 PM
To: rabbitmq-discuss at lists.rabbitmq.com
Cc: Lionel Cons
Subject: Re: [rabbitmq-discuss] rabbitmq-stomp 2.5.1 does not respect the spec wrt content-type
Yes, indeed, this does look like a bug.
You do not say whether your test message included a content-length header. You ought to know that without it there is no way a STOMP server can determine the length of a binary body, other than by using the NULL byte terminator (the usual rule).
If the SENDer gave a message with content-type binary (explicitly or implicitly) and omitted the content-length header, would you wish us to reject the message (with an ERROR) or use the NULL terminator rule, which would almost always indicate a potential error in the binary case?
Notice that the requirement to include a content-length header and the requirement to assume binary when the content-type is omitted are both imposed with the SHOULD keyword. We are not clear what the force of that term is in this context. We are going to clarify this.
Thank you for pointing this out.
Steve Powell (a hoppy bunny)
----------some definitions from the SPD----------
Rigatoni n. A prime-ministerial grin.
Nigella n. The next bottle-size up from a Nebuchadnezzar.
Homily adv. Rather like a frenchman.
On 9 Aug 2011, at 13:08, Lionel Cons wrote:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss