Re: Calling mod-proxy directly from another module

mod_include just executes subrequests for all of it's virtual includes, I haven't tried it with proxied content but it should work.

One thing to note about doing subrequests of proxied content in your own modules is that you can't get the remote status unless you fully execute the request. Therefore, if the remote server gives you a 404 error page, that's what mod_include is gonna serve in place of your include statement.

For local content, you can call ap_sub_req_lookup_uri() or ap_sub_req_lookup_file() and that will give you the status of your subrequest before your run it via ap_run_sub_req(). Basically this works running through the whole request cycle but stopping after fixup. Since mod_proxy does all of it's action in the content handler, you cannot see the status until it's too late.

It might be nice to have mod_proxy do the remote connect, and at least retrieve the status line in the fixup such that the subrequest api would work with proxied content. Or perhaps we could have mod_proxy call ap_is_initial_req() and if it isn't, do a HEAD request in the fixup phase and fill out at least the status line before executing the handler.

I've thought about this problem a lot and can't really come up with a good solution for it, so I haven't offered any fixes for it. Perhaps somebody else has a solution to it.

-bmd

On Tue, Apr 24, 2001 at 12:19:55AM +0200, Graham Leggett wrote:
> Ian Holsman wrote:
Received on Mon Apr 23 22:54:04 2001

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek