Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 5875 invoked from network); 5 Aug 2010 11:14:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Aug 2010 11:14:58 -0000 Received: (qmail 29193 invoked by uid 500); 5 Aug 2010 11:14:57 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 28909 invoked by uid 500); 5 Aug 2010 11:14:55 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 28901 invoked by uid 99); 5 Aug 2010 11:14:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Aug 2010 11:14:54 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rainer.jung@kippdata.de designates 195.227.30.149 as permitted sender) Received: from [195.227.30.149] (HELO mailserver.kippdata.de) (195.227.30.149) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Aug 2010 11:14:45 +0000 Received: from [195.227.30.209] (notebook-rj [195.227.30.209]) by mailserver.kippdata.de (8.13.5/8.13.5) with ESMTP id o75BEOnj020138 for ; Thu, 5 Aug 2010 13:14:24 +0200 (CEST) Message-ID: <4C5A9D0B.1020709@kippdata.de> Date: Thu, 05 Aug 2010 13:14:19 +0200 From: Rainer Jung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 MIME-Version: 1.0 To: "dev@httpd.apache.org" Subject: Rephrasing " worker already used" Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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" Finally: I guess we need to document the behaviour, especially that you have the option to reuse/overwrite or use separate workers, depending on the order of the ProxyPass statements. Any opinion? Regards, Rainer