tlm
2006-04-26 16:55:52 UTC
Hi!
The following question is not strictly about CGIP, but about a problem other
users of CGIP may have run into.
I'm finding that if I use the standard
[% self.CGI.header %]
at the top of my templates, Apache disregards the resulting "Content-Type:
text/html; charset=ISO-8859-1" header, and inexplicably sends out
Content-Type: application/x-perl
which, of course, freaks out the browser.
Everything works almost* fine if I stick this
print $self->reflect->object->CGI->header;
in my render_enter() override, even though the output now includes a
duplicated "Content-Type: text/html; charset=ISO-8859-1" at the top. This
suggests to me that my code is fine, and the problem is with Apache somehow.
Does anyone know why Apache is doing this and/or how to fix it?
Thanks!
tlm
* I say "almost" fine because, of course, the displayed page shows the now
superfluous "Content-Type: text/html; charset=ISO-8859-1" at the top, coming
from the template.
The following question is not strictly about CGIP, but about a problem other
users of CGIP may have run into.
I'm finding that if I use the standard
[% self.CGI.header %]
at the top of my templates, Apache disregards the resulting "Content-Type:
text/html; charset=ISO-8859-1" header, and inexplicably sends out
Content-Type: application/x-perl
which, of course, freaks out the browser.
Everything works almost* fine if I stick this
print $self->reflect->object->CGI->header;
in my render_enter() override, even though the output now includes a
duplicated "Content-Type: text/html; charset=ISO-8859-1" at the top. This
suggests to me that my code is fine, and the problem is with Apache somehow.
Does anyone know why Apache is doing this and/or how to fix it?
Thanks!
tlm
* I say "almost" fine because, of course, the displayed page shows the now
superfluous "Content-Type: text/html; charset=ISO-8859-1" at the top, coming
from the template.