<much snippage and a frivolous/facetious reply ahead> > then execute a mod_proxy handled subrequest. This works in 1.3.X, I mean, > I've never tried it, well, maybe once, but I didn't like it. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The man has a career as a President or member of Congress. :)
> the fact that it forwards all of the requesting client's headers. It might > be better just to have some functionality like that in libghttpd that could > be used when you wanted to use http requests to get data for your handler. Exactly what I would recommend. > If I'm totally off and what you are really thinking of is a way for a > handler to decide that it cannot satisfy the request and conditionally hand > the request over to mod_proxy, this is possible but tricky. mod_rewrite > does this, and it involves something like tacking "proxy:" onto the request > uri and setting the content handler to mod_proxy's handler. You might need > an internal redirect somewhere in there if you tried to do this after fixup > though. Mrph. Expect the "proxy:" hack to disappear before too long. Victor -- Victor J. Orlikowski ====================== [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
