Joe Orton wrote: > On Mon, Oct 11, 2004 at 09:26:37AM -0400, Geoffrey Young wrote: > >>Joe Orton wrote: >> >>>as far as the fact that mod_proxy in HEAD refuses to >>>act as a forward proxy unless "ProxyRequests On" has been configured. >>>So adding "ProxyRequests On" as below fixes the test but whether this >>>should actually be considered a mod_proxy bug or not, I'm not sure. >> >>well it's certainly an important change in behavior. and it kinda feels odd >>- I know that mod_perl has been doing this kind of proxy thing forever but >>we're always doing unusual stuff :) > > > I think it's a bit odd for mod_perl to be asking the server to act as a > forward proxy for a particular request; I'm not sure that really makes > sense.
actually, putting mod_perl in control of dispatching a forward proxy is pretty powerful (and interesting). however, I think there is a valid point here - while mod_perl ought to be able to handle some of the proxy foo for mod_proxy, it might not make sense to be able to do it dynamically. that is, requiring ProxyRequests On might make sense from a security standpoint here since mod_perl is not _entirely_ in control, but rather dispatches a large part of the work over to mod_proxy and, thus, it should respect its rules. oddly enough, the cookbook mentions requiring ProxyRequests On, while the eagle book does not. go figure ;) > It does make sense for a module to want the server to act as a > *reverse* proxy on a per-request basis (an important mod_rewrite feature > if nothing else), and it looks like that must be broken too. gak, that would be bad. > So I'll verify that and then continue this on [EMAIL PROTECTED] as necessary... > but probably mod_perl should be setting ->proxyreq = PROXYREQ_REVERSE > anyway in this case. yes, I noticed that we were using the wrong hard-coded value in the test case as well. once we get everything here figured out we'll move to a named constant, maybe even the right one :) --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
