httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ruediger Pluem <rpl...@apache.org>
Subject Re: Rephrasing " worker already used"
Date Tue, 10 Aug 2010 18:30:59 GMT


On 08/10/2010 07:55 PM, Jim Jagielski wrote:
> On Aug 5, 2010, at 7:32 AM, Plüm, Rüdiger, VF-Group wrote:
> 
>>
>>> -----Original Message-----
>>> From: Rainer Jung 
>>> Sent: Donnerstag, 5. August 2010 13:14
>>> To: dev@httpd.apache.org
>>> Subject: Rephrasing " worker already used"
>>>
>>> The message "worker ... already used by another worker" seems 
>>> to not say 
>>> what's actually happening.
>>>
>>> Situation:
>>>
>>> ProxyPass /X http://a.b.c.d/A
>>> ProxyPass /Y http://a.b.c.d/AB
>>>
>>> Wouldn't a message
>>>
>>> worker "http://a.b.c.d/A" will also be used for URL "/Y"
>>>
>>> be more correct?
>>>
>>> In addition: we do overwrite the worker config (additional 
>>> attributes) 
>>> when parsing the second ProxyPass. Should we add a message
>>>
>>> Merging configuration for worker "http://a.b.c.d/A"
>> Actually it doesn't merge the configuration. For some parameters like
>> timeout they get overwritten with the defaults if not configured again in the
>> ProxyPass directive. So
>>
>> ProxyPass /X http://a.b.c.d/A timeout=5
>> ProxyPass /Y http://a.b.c.d/AB
>>
>> Will result in a worker http://a.b.c.d/A with timeout set to the default value
>> (ProxyTimeout / Timeout).
>>
> 
> The question is whether this should be expected... I feel that

IMHO this is not expected. Rainer already indicted that he intends to change this.
I think if we do not create a new worker in this situation, but using the existing
one we should at most overwrite the explicitly set parameters, but do not reset
parameters to default values.

Regards

Rüdiger


Mime
View raw message