httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: [Bug 8407] - reverse proxy return FORBIDDEN all the time
Date Wed, 24 Apr 2002 15:08:44 GMT
At 08:55 AM 4/24/2002, Bill Stoddard wrote:

> > On Tue, 23 Apr 2002, Bill Stoddard wrote:
> >
> > > We have the exact same issue with mod_cache
> > > (mod_mem_cache/mod_disk_cache).  What do you think about hiding the load
> > > of the protocol modules behind a config directive?
> >
> > I don't have a conceptual problem with that, though it would mean
> > hardcoding the path to the DSO, right?
>I haven't given much thought about how to implement this.  Could we make 
>the assumption
>that the protocol modules are in the same location as mod_proxy?

That's the hassle.  Plus, you lose some 'plugability' in terms of choosing 

I expect a warning message that "No proxy agents are loaded" is probably
more useful, ultimately, than attempting to co-load the modules.

The question is, how to determine?  Look for modules named "mod_proxy_*"?
I believe it's probably better to check that some other modules register 
against the appropriate proxy hooks or optional functions, so we pick up future
replacement modules for the agents without fighting namespace collisions
(modules that -look- like proxy agent names, but aren't, and modules that
don't appear to be agents, but are.)


View raw message