[Mod_gzip] handlers and missing directories
mod_gzip@lists.over.net
mod_gzip@lists.over.net
Mon, 31 Mar 2003 13:11:54 EST
--part1_bc.35e854ab.2bb9deea_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
> Gareth wrote...
>
> Not an error message.
> Full blown page.
So who or what is turning an actual 'file not found' situation
( Error 404 ) back into a 'real' response ( 200 )?
Is there something 'intercepting' normal Apache 'file not found'
errors and converting them to '200 responses'?
Do you have some kind of generic 302 redirect to another
page for all 'file not found' errors? Or are you doing this
with CGI?
> If I request:
> test/res.html
> Then I get the same as
> test/x/res.html
> except the specifics of x are loaded into res.html.
> It's a quirk of one of our systems.
>
> Nice try though ;-)
What do your own log files say?
Turn on full mod_gzip log and tell us what mod_gzip itself
has to say about WHY it chooses not to compress.
mod_gzip will always give a REASON when it decides something
is not eligible for compression.
The entry in the log will look something like this...
mod_gzip: DECLINED:SEND_AS_IS_NO_200
or perhaps
mod_gzip: DECLINED:EXCLUDED
If you are passing the errors off to some .ASP script
and you haven't included .ASP as an eligible input
file type for compression then it will probably say
'DECLINED:EXCLUDED' because mod_gzip hasn't
been told to compress the output from .ASP scripts.
These kind of 'pass offs' result in a whole new 'request'
flowing through Apache Server ( they call it an internal
redirect or sub-request ) and the same eligibility rules
apply to these 'internal' requests.
Gareth
In a message dated 3/31/2003 10:30:29 AM Central Standard Time,
gbjk@thermeoneurope.com writes:
> Not an error message.
> Full blown page.
>
> If I request:
> test/res.html
> Then I get the same as
> test/x/res.html
> except the specifics of x are loaded into res.html.
> It's a quirk of one of our systems.
>
> Nice try though ;-)
>
> Gareth
>
--part1_bc.35e854ab.2bb9deea_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2><BR>
> Gareth wrote...<BR>
><BR>
> Not an error message.<BR>
> Full blown page.<BR>
<BR>
So who or what is turning an actual 'file not found' situation<BR>
( Error 404 ) back into a 'real' response ( 200 )?<BR>
<BR>
Is there something 'intercepting' normal Apache 'file not found'<BR>
errors and converting them to '200 responses'?<BR>
<BR>
Do you have some kind of generic 302 redirect to another<BR>
page for all 'file not found' errors? Or are you doing this<BR>
with CGI?<BR>
<BR>
> If I request:<BR>
> test/res.html <BR>
> Then I get the same as <BR>
> test/x/res.html<BR>
> except the specifics of x are loaded into res.html.<BR>
> It's a quirk of one of our systems.<BR>
><BR>
> Nice try though ;-)<BR>
<BR>
What do your own log files say?<BR>
<BR>
Turn on full mod_gzip log and tell us what mod_gzip itself<BR>
has to say about WHY it chooses not to compress.<BR>
<BR>
mod_gzip will always give a REASON when it decides something<BR>
is not eligible for compression.<BR>
<BR>
The entry in the log will look something like this...<BR>
<BR>
mod_gzip: DECLINED:SEND_AS_IS_NO_200<BR>
or perhaps<BR>
mod_gzip: DECLINED:EXCLUDED<BR>
<BR>
If you are passing the errors off to some .ASP script <BR>
and you haven't included .ASP as an eligible input<BR>
file type for compression then it will probably say<BR>
'DECLINED:EXCLUDED' because mod_gzip hasn't<BR>
been told to compress the output from .ASP scripts.<BR>
<BR>
These kind of 'pass offs' result in a whole new 'request'<BR>
flowing through Apache Server ( they call it an internal<BR>
redirect or sub-request ) and the same eligibility rules<BR>
apply to these 'internal' requests.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Gareth<BR>
<BR>
<BR>
<BR>
<BR>
In a message dated 3/31/2003 10:30:29 AM Central Standard Time, gbjk@thermeo=
neurope.com writes:<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Not an error message.<BR>
Full blown page.<BR>
<BR>
If I request:<BR>
test/res.html <BR>
Then I get the same as <BR>
test/x/res.html<BR>
except the specifics of x are loaded into res.html.<BR>
It's a quirk of one of our systems.<BR>
<BR>
Nice try though ;-)<BR>
<BR>
Gareth<BR>
</BLOCKQUOTE><BR>
<BR>
</FONT></HTML>
--part1_bc.35e854ab.2bb9deea_boundary--