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

Mark Blackman m.blackman at fairfx.com
Mon Feb 20 16:52:04 GMT 2012

On 17 Feb 2012, at 13:23, Dominic Germain 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()?

No short-term drawback, but Catalyst::Plugin::Unicode::Encoding should
take care of decoding your inputs (your forms) *and* encoding your
outputs. If your forms are breaking, it sounds you might not be encoding
your data when it's written to the database where the form data is

- Mark

More information about the Catalyst mailing list