I suppose it's cleaner, but special cases the ; in URLs...
[extra stats]
* This was what I saw as problmatic also. But, in fact, that isn't the way
* that NCSA httpd, at least, works (as Guy Descoux pointed out). What it
* does is read some magic names (like "cgi-bin") from a configuration file
* and assume that the first thing in the path after the magic name is a
* script and anything else is info. It is not necessary to stat anything.
No, it doesn't, that's what Charles is talking about. Currently it assumes
nothing about the path and stats each level until it finds something it can
use.
* This is workable, but less clean than either Charles suggestion or my
* earlier one (the maintainer has to set up and maintain the magic
* names, for example). I also agree with Charles that embedding
* information in a path is "really poor", primarily because it is
* potentially confusing.
*/
Well, confusing yes, but it makes for some interesting filters, such as
/cgi-bin/get-annotations/foo/bar/foo.html
which, with PATH_TRANSLATED, allows you to seamlessly get group annotations
for a document.
--Rob