Legal characters for routing and binding keys

[James Gardner]

Hi,

I looked at the AMQP 0-9-1 reference, and Googled, but I cannot find any definitive list of legal/illegal characters for routing keys, or topic binding keys.
Obviously the '.', '*', and '#' are special characters and I can rule them out for use in keys, but what other restrictions are there, if any?

I am planning on using a query-string-like KV pair arrangement for one of the words in a routing key, so the routing key would end up looking something like:

someword.fm=png&pu=ztf&pve=noaa&vs=1;fm=jpeg&pve=nids%20dept.someotherword.etc


Please let me know what is acceptable, both from the perspective of the specification, and RabbitMQ in particular if it differs from the spec in any way.
Many thanks,

James Gardner (NIDS- NOAA)

[Simon MacMullen]

As far as I can see there is no limit in the spec other than "valid
UTF-8 byte sequence with no null character". That's what we allow.

That's opposed to the situation with exchange and queue names, which in
the spec are confined to [a-zA-Z0-9-_.:]* (although again we allow the
same as for routing keys).

Cheers, Simon

On 28/10/14 17:22, James Gardner wrote:
>
> Hi,
>
> I looked at the AMQP 0-9-1 reference, and Googled, but I cannot find any
> definitive list of legal/illegal characters for routing keys, or topic
> binding keys.
> Obviously the '.', '*', and '#' are special characters and I can rule
> them out for use in keys, but what other restrictions are there, if any?
>
> I am planning on using a query-string-like KV pair arrangement for one
> of the words in a routing key, so the routing key would end up looking
> something like:
>

> someword.*fm=png&pu=ztf&pve=noaa&vs=1;fm=jpeg&pve=nids%20dept*.someotherword.etc

>
>
> Please let me know what is acceptable, both from the perspective of the
> specification, and RabbitMQ in particular if it differs from the spec in
> any way.
> Many thanks,
>
> James Gardner (NIDS- NOAA)
>

> --
> You received this message because you are subscribed to the Google
> Groups "rabbitmq-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to rabbitmq-user...@googlegroups.com
> <mailto:rabbitmq-user...@googlegroups.com>.
> To post to this group, send email to rabbitm...@googlegroups.com
> <mailto:rabbitm...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

[Laing, Michael]

I believe I chased this down and UTF8 is acceptable. Routing keys are limited to 256 octets however.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

[Laing, Michael]

Or maybe it is 255...

[James Gardner]

Awesome, I appreciate the confirmation. Thanks Simon, and Michael!
Cheers,
James

[Behrang]

Where in the spec is the valid characters for an exchange name specified? Couldn't find anything related to exchanges in the spec: http://www.amqp.org/sites/amqp.org/files/amqp.pdf

> <mailto:rabbitmq-users+unsub...@googlegroups.com>.

[Michael Klishin]

See section 1.1, the exchange-name and shortstr domains (data types) [1].

1. http://www.rabbitmq.com/resources/specs/amqp-xml-doc0-9-1.pdf

> <mailto:rabbitmq-users+unsubscri...@googlegroups.com>.

> To post to this group, send email to rabbitm...@googlegroups.com
> <mailto:rabbitm...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ