[rabbitmq-discuss] Unicode handling changed between 2.5.1 and 2.6.1?
majek04 at gmail.com
Fri Sep 16 10:28:43 BST 2011
On Fri, Sep 16, 2011 at 08:31, Toby Corkindale
<toby.corkindale at strategicdata.com.au> wrote:
> On 16/09/11 17:20, Toby Corkindale wrote:
>> I upgraded from RabbitMQ + STOMP plugin, from version 2.5.1 to 2.6.1.
>> Now I am seeing a bunch of double-encoding of unicode characters.
>> I wondered if there have been any changes to RabbitMQ or the STOMP
>> plugin between those versions that could have caused this?
>> (It's possible it's coming from somewhere else, but I didn't change much
>> else here..)
> I found a place in my code where I was doing UTF8 conversion, and after
> removing that, I'm not getting double-encoded UTF8 any more. However the
> code definitely used to require it.
> I guess something relating to unicode was fixed in the stomp or rabbit
See this discussion:
AFAIR nothing substantial was changed, only the fact that we don't
add content-type by default.
Is it possible that this is what you see?
More information about the rabbitmq-discuss