httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: [PATCH] Reverse proxy and authentication
Date Sun, 16 May 1999 23:53:33 GMT
[Hey Graham, it's more convenient if you send one attachment with the
whole patch rather than an individual attachments each with one-file
attachments, thanks.]

As Roy might say, "there is no such thing as a reverse proxy".  He's
referring to the fact that if you read the rfc you won't find mention of a
"reverse proxy", only of a proxy.  And strictly speaking, a proxy requires
absolute URIs, for example, so this application is definately not an
*http* proxy.  The core's concept of proxy is closer to that of an http

The problem I see here is that really what the proxy module is being used
as here is as a special purpose database for fetching response objects. 
Why does it set proxyreq = 1?  If there were a module which was fetching
objects from a db and caching them locally we wouldn't be setting proxyreq
= 1 for that module... how is this "reverse proxy" different? 


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message