httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: mod_proxy: proposal for v2.0
Date Thu, 27 Jan 2000 09:22:57 GMT
As I stated during the previous thread...

I would like to see the removal of the forward-proxy code (saving on
continued maintenance); we can easily refer people to other proxy code,
such as Squid.

Other features that can be trimmed are fine with me. But hey... your call
on what you'd like to do. I'll support any reduction in this area because
I believe it is somewhat duplicative of other open-source efforts.

I recall the prior discussion did come up with a few design points (such
as a general page cache and generalized remote page fetching).


On Thu, 27 Jan 2000, Graham Leggett wrote:

> Hi all,
> This has been brought up before, so with the previous discussions in
> mind, I would like to put forward the following proposal for the future
> of mod_proxy within v2.x.
> I would like to propose the deprecation of the "forward proxy"
> functionality of the mod_proxy module, reverting it to purely a "reverse
> proxy" implementation.
> I have found (and fixed) a few more bugs in the existing code, and plan
> to do a major rewrite of it in the next few weeks. What will make my job
> easier is to focus on the reverse proxy and caching behavior within the
> code, which has become really convoluted and confusing.
> My plans include:
> - a shared memory cache in addition to the disk cache.
> - upgrade to HTTP/1.1.
> - extend functionality to cache (in memory) local objects in addition to
> remote ones.
> Does anyone violently oppose what I'm trying to do? Am I on the wrong
> track here?
> Regards,
> Graham
> -- 
> -----------------------------------------
>		"There's a moon
> 					over Bourbon Street
> 						tonight...

Greg Stein,

View raw message