[rabbitmq-discuss] STOMP 1.1 Repeated Headers

Lionel Cons lionel.cons at cern.ch
Fri Nov 18 06:40:34 GMT 2011

gmallard <allard.guy.m at gmail.com> writes:
> I establish a 1.1 level connection, and send a frame:
> destination:/queue/tq
> dupkey1:latest
> dupkey1:before1
> dupkey1:before2
> Payload.^@
> Later I SUBSCRIBE, and receive that message.
> When the MESSAGE frame comes off the wire, I expect to see all three
> of those 'dupkey1' headers, in order.  I do not.  Only the first of
> the 'dupkey1' headers is present.

To my understanding, this is compatible with the STOMP 1.1 spec that
says that, in case of repeated header entries, "only the first header
entry SHOULD be used as the value". So RabbitMQ just considers "latest"
as the value for dupkey1. When it later sends the MESSAGE frame, only
this value is sent.



More information about the rabbitmq-discuss mailing list