> On 23 Apr 2002 [EMAIL PROTECTED] wrote: > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8407 > > reverse proxy return FORBIDDEN all the time > > > > ------- Additional Comments From [EMAIL PROTECTED] 2002-04-23 17:25 >------- > > I loaded additionnal mod_proxy modules (mod_proxy_http.so, mod_proxy_ftp.so, > > and/or mod_proxy_connect.so )and it works now... > > the error log said nothing. > > We should consider having mod_proxy issue a warning at startup if it's > loaded as a DSO but none of the protocol handlers (mod_proxy_*.so) are > loaded. I think you get an message when you try the connect, but that > might only show up at high LogLevels (not sure on that one... I've seen > it, this guy didn't). Anyway, this problem has bitten me before when I > switched from a static mod_proxy [where the mod_proxy_foo's are built in > by default] to a shared one, where they're built by default but you have > to LoadModule them individually. >
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? Eg ProxyRemote * would load underthe coveres all the protocol modules. Similarly for mod_cache: "EnableCache disk" would automagically load mod_disk_cache and "EnableCache mem" would load mod_mem_cache. The directives are probably not right but hopefully I've explained the idea well enough to give you the right idea... Bill
