Actually, Apache has:
AddDefaultCharset ISO-8859-1
And my content-type header meta tag in the HTML output also reads
Header looks like this under regular CGI:
HTTP/1.1.200.OK(CR)(LF)
Date:.Tue,.13.Feb.2007.23:21:28.GMT(CR)(LF)
Server:.Apache(CR)(LF)
Set-Cookie:.publish=;.domain=.lfpress.com;.p
> Foo JH wrote:
>> Hi all,
>>
>> Can anyone point me in the right direction? I am expecting POST with
>> XML content, so the usual parser won't work...I think.
FYI, The libapreq (aka, Apache::Request) API (at least, the C API) lets
you define your own parsers. See
http://httpd.apache.org/apreq/do
Hi there:
I'm using Apache2 and mod_perl 2.0.2 on a Debian Etch server, and just
ran into trouble when trying to run an unaltered CGI script using
ModPerl::PerlRun. The script I'm using is UseMod 0.92
(http://www.usemod.com/cgi-bin/wiki.pl?UseModWiki/OldVersions).
This particular script cal
Just to clarify:
On Feb 8, 2007, at 3:03 PM, Aaron Hawryluk wrote:
Our publishing system doesn't use any strange character sets -
Your system is working with data in one character set, and publishing
it to the web in another character set. The fix is *likely* just
setting the right char
Foo JH wrote:
Hi all,
Can anyone point me in the right direction? I am expecting POST with XML
content, so the usual parser won't work...I think.
I've used $r->read() in the past to do exactly what you are specifying.
http://perl.apache.org/docs/2.0/api/Apache2/RequestIO.html#C_read_
Hi all,
Can anyone point me in the right direction? I am expecting POST with XML
content, so the usual parser won't work...I think.
Hope this helps.
