On 7/20/03 11:12 PM, Slava Bizyayev wrote:
Your own content-type is supposed to be overwritten only in case of the use
of
PerlSetVar UseCGIHeadersFromScript Off
in your configuration file. You might wish to comment this line in your
configuration file when your script generates correct
On 7/21/03 9:47 AM, John Siracusa wrote:
On 7/20/03 11:12 PM, Slava Bizyayev wrote:
Your own content-type is supposed to be overwritten only in case of the use
of
PerlSetVar UseCGIHeadersFromScript Off
in your configuration file. You might wish to comment this line in your
configuration
Yes John, I understand. I'm working on this now.
Slava
- Original Message -
From: John Siracusa [EMAIL PROTECTED]
To: Mod Perl Mailing List [EMAIL PROTECTED]
Sent: Monday, July 21, 2003 11:03 AM
Subject: Re: ANNOUNCE: Apache::Dynagzip 0.10
On 7/21/03 9:47 AM, John Siracusa wrote
This version is all about the unnecessary warnings on some systems.
Thanks to Rob Bloodgood and Damyan Ivanov those complained about
uninitialized value warnings from unused HTTP headers, and about the pack
mode c, which generated warnings in logs on their systems (running -w).
Everyone provided
Why does Apache/Dynagzip.pm call $r-content_type('text/html') in
several places? My apache module earlier in the Apache::Filter chain
sets $r-content_type to something else, but it then gets overridden by
Dynagzip.pm. If I comment out all the calls to
$r-content_type('text/html') in
/1.1.
Thanks,
Slava
- Original Message -
From: John Siracusa [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Slava Bizyayev [EMAIL PROTECTED]
Sent: Sunday, July 20, 2003 10:05 PM
Subject: Re: ANNOUNCE: Apache::Dynagzip 0.10
Why does Apache/Dynagzip.pm call $r-content_type('text/html
