[Catalyst] View::TT FILTERS and utf-8

Bernard FRIT bernard.frit at gmail.com
Mon Jan 9 14:13:08 CET 2006


2006/1/6, Matt S Trout <dbix-class at trout.me.uk>:
> On Fri, Jan 06, 2006 at 03:32:20PM +0000, Carl Franks wrote:
> > > The problem occurs only when using mod_perl.
> >
> > I suggest you view the pages using a tool which lets you view the full
> > response header, as well  as the body - it sounds like apache might be
> > adding an encoding header that is messing things up.
> >
> > Compare the response header between responses from mod_perl and the
> > standalone server (or some other webserver).
>
> PerlSendHeader Off
>
> is at the top of most of my mod_perl-served <Location> blocks, although I
> forget exactly what brokenness this prevented.

I tried this but without any effect.

Even if setting up charset to iso-8559-1 solved the problem, I 'm
concerned by the fact that the output is not html safe. It produces
chars > 127 in place of escaped html chars as &eacute;...

The weird thing is the build'in server produces correctly escaped
chars but not the mod_perl one. I can't figure out what's going on :
is TT2 behavior different when invoked from catalyst or when invoked
from mod_perl ?

I didn't find any mod_perl directive to set up charset.

Any hint will be greatly apreciated.

--
Bernard FRIT



More information about the Catalyst mailing list