httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ruediger Pluem <rpl...@apache.org>
Subject Re: [Fwd: Re: Apache 2.2.3 mod_proxy issue]
Date Sun, 29 Oct 2006 14:37:40 GMT


On 10/28/2006 05:26 PM, Jim Jagielski wrote:
> Ruediger Pluem wrote:
> 
>>
>>On 10/27/2006 06:20 PM, Jess Holle wrote:
>>
>>
>>>On the other hand, if I use:
>>>
>>>   ProxyPass /jsp-examples ajp://localhost:8010/jsp-examples
>>>    
>>>This works fine!
>>>
>>>I assume I should file a bug against mod_proxy -- or is this a known issue?
>>
>>At least it is known to me :-). See http://issues.apache.org/bugzilla/show_bug.cgi?id=40275#c6
>>
> 
> 
> As well as anyone who knows how the proxy module works... :)
> 
> The main issue is that with ProxyPass the proxy module knows
> that an external proxy will be used at config time and is
> able to pro-actively construct the worker and pool. With
> mod_rewrite, it's tough, since what is proxied is runtime
> determined... Now maybe one could be maintained after
> the fact, but you would need some sort of GC, esp if
> the mod_rewrite proxy is totally indeterminant.

I guess we should create a directive like DefineWorker (I do not really care about
the exact name), that enables the administrator to define / create a worker.
That would be really handy for mod_rewrite as in the reverse proxy case the number of
different backend targets are usually limited and known to the administrator.
This would avoid the need for nasty tricks like "pseudo balancers" with only one member.

Regards

RĂ¼diger



Mime
View raw message