Re: [Catalyst] UTF8 and content length

John Napiorkowski writes: > So what it looks like to me is that the code that sets a content > length if one is not set by the view is not dealing with unicode > correctly. I have another unicode issue I need to look at soonish so I > try to see if we can get a test case for

Re: [Catalyst] UTF8 and content length

So what it looks like to me is that the code that sets a content length if one is not set by the view is not dealing with unicode correctly.  I have another  unicode issue I need to look at soonish so I try to see if we can get  a test case for this.  -jnap On Wednesday, July 20, 2016 8:18

Re: [Catalyst] UTF8 and content length

Looks like to a bug to me, although I'm not personally keen on the auto length setting in Catalyst it should be corrected.  I'm happy to get a patch, or at the very least give me a broken test case (checkout  https://github.com/perl-catalyst/catalyst-runtime/blob/master/t/utf_incoming.t  and see

Re: [Catalyst] UTF8 and content length

>> The clean way to do this is to simply encode the data before you put it in the body: I fogot or, most likely, didn't realise I need to encode to utf-8 string wich is already utf8 in sources. I still need to think over this tricky rocket science, but your solution is working. σας

Re: [Catalyst] UTF8 and content length

* Kroshka Yenot [2016-07-15 13:12]: > Hi! > > if content type is 'application/json' or 'application/json; > charset=utf-8' Catalyst sets content length in chars, NOT IN BYTES and > I'm getting > > {"id":1, "msg":"В Питере > > if content type is 'text/html' Catalyst sets content