httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: [PATCH] another mod_deflate vs 304 response case
Date Mon, 22 Nov 2004 17:02:37 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.



View raw message