[rabbitmq-discuss] STOMP & message-id

Matthias Radestock matthias at rabbitmq.com
Mon Aug 22 13:48:23 BST 2011

On 22/08/11 13:46, Tony Garnock-Jones wrote:
> On 22 August 2011 08:09, Matthias Radestock <matthias at rabbitmq.com
> <mailto:matthias at rabbitmq.com>> wrote:
>     amqp-message-id is the header one can supply in SEND in order to set
>     the message_id field of AMQP's 'basic' content. Similarly, in
>     MESSAGE, if the AMQP 'basic' content contains a message_id it is
>     turned into an amqp-message-id header.
> OK, that's good; it doesn't explain Lionel's report that SENDing with
> "message-id" set led to a correspondingly-set "message-id" on the
> resulting MESSAGE, though. Looking at the code, I'm guessing that Lionel
> either sent an "amqp-message-id" header on the SEND, or that I've
> overlooked or misinterpreted something!

message-id, just like all user-defined headers, are simply passed 
through. The exception are the headers we map to AMQP's 'basic' fields.


More information about the rabbitmq-discuss mailing list