httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <Ken.C...@Golux.Com>
Subject Re: Thoughts on filter-chain composition
Date Mon, 11 Sep 2000 18:42:33 GMT
TOKILEY@aol.com wrote:
> 
> Say someone writes a CGI program that is supposed to take
> care of the encoding ( let's stick with gzip since it's so easily
> understandable ) of the outbound body data. If it's using standard
> Content-encoding then the only thing that's going to tell you that's
> what happened  will be the addition of the 'Content-Encoding: gzip'
> response header field.
> 
> As per RFC, the IMT is going to remain text/html just the way it
> was on entry to the filter and so is the file extension.
> Just looking at those 2 response fields can never really tell you
> what happened during the CGI pass.

Good point.

> Would it be up to each and every filter to check for the existence
> of the 'Content-encoding' field when the buckets start showing up
> and then do its own response field checking to see if it knows how
> to handle whatever that might be?

I believe so, yes.

> We are right back to the slippery slopes of who's responsible
> for tracking all filter 'dependencies' again. Does the filtering
> engine have any responsibility or is the onus always going
> to be on the filter write to check for ALL possible 'no can do'
> scenarios?

I think the latter.  That's modular and extensible.
-- 
#ken    P-)}

Ken Coar                    <http://Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed"   <http://ApacheUnleashed.Com/>

Mime
View raw message