Using */* handler instead of fixups...

[Andrew <an...@aaaaaaaa.demon.co.uk>]

> FWIW, your pre-send can be done by declaring a handler for */*
> which always DECLINEs... of course, that will be called for
> server-side-included files as well (when their handlers are run;
> you can check for this case by looking at r->protocol).
> 
> rst

Damn, that's worth quite a lot to me actually.  Thanks.  Mmm, now
I get to redo all the modules I've written so far...

Ay.

Re: Using */* handler instead of fixups...

[Alexei Kosut <ak...@nueva.pvt.k12.ca.us>]

On Tue, 20 Feb 1996, Andrew wrote:

> > FWIW, your pre-send can be done by declaring a handler for */*
> > which always DECLINEs... of course, that will be called for
> > server-side-included files as well (when their handlers are run;
> > you can check for this case by looking at r->protocol).

Wait... unless the API has changed since 1.0.1, when I last looked at it, 
this won't work. The server doesn't look at */* handlers until after it 
looks at all the others. So this means that any module that did things by 
handling */* and DECLINEing wouldn't work with any of the modules that 
handle things - like CGI scripts, server-side includes, imagemaps, etc, 
etc, etc. Only the things handled by other */* handlers (currently only 
http_core) would this work for. While this might actually be desirable 
behavior for your mod_expires (since you might not want CGI script, for 
example, to get an Expires header tacked on), for mod_env, it makes it  
useless, because it would add the variables *after* the CGI script was 
run.

--/ Alexei Kosut <ak...@nueva.pvt.k12.ca.us> /--------/ Lefler on IRC
----------------------------/ <http://www.nueva.pvt.k12.ca.us/~akosut/>
The viewpoints expressed above are entirely false, and in no way
represent Alexei Kosut nor any other person or entity. /--------------