[Catalyst] Fix for content-length issue introduced with Catalyst 5.8.x

Bill Moseley moseley at hank.org
Tue Feb 21 03:02:52 GMT 2012

On Fri, Feb 17, 2012 at 8:23 PM, Dominic Germain
<mailinglists at sogetel.com>wrote:

> Using Catalyst::Plugin::Unicode::Encoding instead of "hacking" Catalyst.pm
> works, but it brakes some other parts of our code (form posted containing
> some accent are screwed up).
> Reverting Catalyst.pm to old fashion bytes::length() is way simpler...
> Anyone aware of drawback using it instead of length()?

None, although I would expect to see you again here with other problems
related to encoding in the future. ;)

Honestly, you should just fix it right.  Decode ALL input and encode all
output.  Once you have that set up you will never[1] fight encoding issues

[1] for some value of never.

-- =

Bill Moseley
moseley at hank.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20120221/5cb1d=

More information about the Catalyst mailing list