[rabbitmq-discuss] [BUG] Management interface fails to render queues with non utf-8 names.

Ceri Storey ceri at lshift.net
Wed Oct 30 14:56:56 GMT 2013


We noticed that one of our customers has created some queues whose names
aren't valid UTF-8. From the AMQP spec it looks like short-strings
should be valid UTF-8, and contain only certain character classes.
However, my colleague Frank has tracked down some code in
where there's a comment to the effect that those rules aren't enforced

However, if we try to request the list of queues via the API, we get the
following backtrace:

webmachine error: path="/api/queues"

Which seems to indicate that the management console assumes that entity
names are valid UTF-8. We've advised our customer to consider renaming
their queues, but it'd be good to somehow rectify the difference in
assumptions around name encodings. My first thought might be to
percent-encoded non-utf8 data. but there's likely better ways to handle

The quickest way to reproduce the problem would be to run this ruby
script using Bunny (assuming you have a local rabbit with the default

require 'bunny'
bunny = Bunny.new().tap { |b| b.start }
q = bunny.queue("foo\316null")

Once you've done that, if you try to list the queues in the root
virtualhost, you'll find you get the above exception.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131030/310f108d/attachment.htm>

More information about the rabbitmq-discuss mailing list