httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: Allowing modules to add input filters is broken
Date Sat, 19 May 2001 12:14:57 GMT
Graham Leggett wrote:

> > The output filters should *always* run, if at least to send an EOS bucket.
> > That EOS is actually what triggers the delivery of the headers to the
> > network (or at least to the CORE filter for output buffering into the next
> > request).
> >
> > So if you're not seeing output filters run, then a bug exists.

Hmmm - looking at this some more something weird is going on.

When a normal 200 response is served, the output filter is run
correctly, the header values are modified, and the modified header
reaches the browser.

When a 304 is served however, the output filter is run correctly, the
header values are modified, but the modified header never reaches the
browser.

It seems the headers are handled differently when the response is a
header only, as opposed to when there are headers and a body.

Does this make sense to anyone?

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."
Mime
View raw message