Besides, while looking why this thing is broken, I saw that this is an HTTP hook and has little to do with protocols, since its defined in include/http_protocol.h.
so? apache isn't perfectly separated, and a few of the functions are clearly misnamed or misplaced - see ap_http_method which returns the default scheme (http) and _not_ the default http method (if there is such a thing, probably GET)
So it definitely doesn't belong to the protocols documentation, but should be put together with other HTTP hooks.
right, there is no reason to hook into it if you're using http, where the defaults are specified via RFC 1700 (according to /etc/services).
but I don't see it as an http-only thing, regardless of where it happens to be defined.
it's use is in defining a default port so that Apache can create self-referential URLs - otherwise with UseCanonicalName Off and no port in the request line or headers there can be no way to determine the port for other parts of the API.
when would this happen? with mod_pop3 for one, which listens on the standard POP3 port (110) - the default port should probably be set as well (although there isn't the concept of redirects in mail, so I doubt it actually matters).
but say you implement you own protocol for xslt transformations or something (xslt://foo/). you can use a default port handler and default method handler for making sure that URL manipulation routines work properly for your application.
> Also I still fail to see its usability.
I think I've adequately answered that (and a few times, now). and besides, you or I seeing it's usability isn't the issue. in case you've lost sight
http://perl.apache.org/docs/2.0/user/design/design.html#Introduction
to me, that means this a no brainer: if it exists as a hook in apache we offer it to perl.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
