[rabbitmq-discuss] Default vhost and Http API

[stone]

Hi Tony,

I didn't save the scene, didn't really look into the fault client code.
Just had a quick test, reproduced by using term_to_binary instead of
list_to_binary to make the queue name in Erlang client.
Perhaps this WAS exactly the case from the other day. shame :)
I simply though it was UTF used in that case because the crash report has
"utf" in it.

http://localhost:55672/#/queues
{error,{exit,{ucs,{bad_utf8_character_code}},
             [{xmerl_ucs,from_utf8,1},
              {mochijson2,json_encode_string,2},
              {mochijson2,'-json_encode_proplist/2-fun-0-',3},
              {lists,foldl,3},
              {mochijson2,json_encode_proplist,2},
              {mochijson2,'-json_encode_array/2-fun-0-',3},
              {lists,foldl,3},
              {mochijson2,json_encode_array,2}]}}

Anyway, perhaps  rabbit-server should have the name validated before
allowing the declaration.

BRs
/stone

在 2012年3月27日 下午7:27，Tony Garnock-Jones <tonygarnockjones+rabbitmq at gmail.com>
写道：

> On 27 March 2012 12:50, stone <zmstone at gmail.com> wrote:
>
>> The other day, we accidentally created queues and bindings with UTF
>> characters in the names.
>> Then the management web GUI crashed (on mochiweb level if i remember
>> correctly), so we couldn't delete the queu on GUI.
>> And there was no CLI to do it, we actually had to reset the node to get
>> rid of the bad-naming queues.
>>
>
> A test case would be extremely useful and welcome! Can you remember the
> exact bytes used in the names? And which GUI actions caused the crashes?
>
> Regards,
>   Tony
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120327/98fe0da9/attachment.htm>