httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@engelschall.com (Ralf S. Engelschall)
Subject Re: [PATCH] Apache as a Reverse Proxy
Date Mon, 30 Mar 1998 07:34:10 GMT

In article <3.0.3.32.19980329225831.00936e00@localhost> you wrote:

> old mail day!

> At 04:03 PM 2/12/98 +0100, Ralf S. Engelschall wrote:

>>Apache as a Reverse Proxy

> I see this got implemented; great!  

<grin> Yes, a long time ago, Brian ;-)

> One question though, why two separate
> directives, "ProxyPass" and "ProxyPassReverse"?  What situation would one
> specify a ProxyPass section of their site, and *not* want the
> redirect-rewriting that PPR does?  I suggest in the interests of directive
> simplicity that the functionality of PPR be merged into the code for
> ProxyPass.

Hmmm..... yes and no. When you look at my article in the current WEBTechniques
4/98 you see that my Reverse Proxy configuration uses RewriteRule ... [P] plus
ProxyPassReverse. No ProxyPass itself because it is too less powerful. Here
the merging would be confusing and perhaps leads to problems.

On the other hand, yes: When one uses ProxyPass he usually(!) wants the
reverse proxing functionality, too. For the redirects! So I think although
ProxyPassReverse has its use as a stand-alone option perhaps it can be really
useful to implicitly force a ProxyPassReverse for any ProxyPass directive.

This should be trivial to add because both use the same arguments.  The
command handler function of ProxyPass just has to setup the same stuff as the
handler for ProxyPassReverse or even call it directly. Comments?

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message