On Wed, 17 May 2000, Geoffrey Young wrote:
> after reading about it again, it looks like something of a misnomer - like
> it does less parsing of the header and more making it available for
> manipulation. but I was able to change $r->uri during PostReadRequest
> anyway. it does make sense that all the headers must be read and available
> before translation I think, and this is what I've seen in practice...
>
> anyway, at this point I default to those who were around earlier and
> understand where the HeaderParser phase gets its name/roots... :)
yeah, the name is a little misleading. it's original intent was to allow
modules to take action based on the already parsed headers early on in
the request. which PostReadRequest can also do (and was introduced long
after HeaderParser), but is per-server, whereas HeaderParser is
per-{location,file,directory,etc}
