httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [PATCH] another mod_deflate vs 304 response case
Date Mon, 22 Nov 2004 17:30:04 GMT

> At 10:26 AM 11/22/2004, Cliff Woolley wrote:
>>>>>>On Mon, 22 Nov 2004, Joe Orton wrote:
>>> There's another mod_deflate vs 304 response problem which is being
>>> triggered by ViewCVS on when a CGI script gives a
>>> "Status: 304" response the brigade contains a CGI bucket then the EOS,
>>> so fails the "if this brigade begins with EOS do nothing" test added for
>>> the proxied-304 case.
>>Okay, but why the next three lines?  Why would Content-Encoding: gzip
>>*ever* be set on a 304?
>Let me expand on this question...
>... we've all seen broken browsers.  Why attempt to gzip non-2xx
>responses at all?  I'd prefer (at least on servers with modest error
>message responses) to ensure the user can *read* any error response,
>in spite of any broken browser behavior w.r.t. deflate.
>It seems like a flag (even default) dropping gzip from non-2xx class
>responses could be a very useful thing.  At least, if the browser
>results are a mess, it's due to a good response.

Because some custom error response pages on some
sites are HUGE... and they WANT to compress them.

For a while there ( especially in Europe and most notably
in Germany ) it seemed like there was a contest going on
to see who could come up with the most bloated and 
complicated error response pages for their Web farm/
commercial Server. Tons of javascript and flashing lights
and bouncing balls and advertising links, you name it.

I have seen some base error templates exceed 200,000 bytes
of HTML and javascript just to say 'We're sorry... that page
can't be found'.

Bottom line: If someone WANTS to be doing this sort of thing
and they WANT to compress the responses they certainly
should be able to and it should all work.

Anything that prevents it from working is still just a bug that's
being ignored.

Suggestion: Make sure someone can compress any response
they want via config but then make sure to NOT recommend
doing certain things and let them swim at their own risk.
No lifeguard on duty.

Kevin Kiley

View raw message