Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 46003 invoked from network); 6 Feb 2008 15:35:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2008 15:35:25 -0000 Received: (qmail 37815 invoked by uid 500); 6 Feb 2008 15:35:15 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 37522 invoked by uid 500); 6 Feb 2008 15:35:14 -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 37511 invoked by uid 99); 6 Feb 2008 15:35:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 07:35:14 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [209.133.199.10] (HELO jimsys.jaguNET.com) (209.133.199.10) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 15:34:45 +0000 Received: from localhost (localhost [127.0.0.1]) by jimsys.jaguNET.com (Postfix) with ESMTP id AACDC5638D0 for ; Wed, 6 Feb 2008 10:34:52 -0500 (EST) Message-Id: From: Jim Jagielski To: dev@httpd.apache.org In-Reply-To: <1202241129.2426.199.camel@lost.cnet.cnwk> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Subject: Re: mod_proxy timeouts in the 2.0 Date: Wed, 6 Feb 2008 10:34:52 -0500 References: <1202241129.2426.199.camel@lost.cnet.cnwk> X-Mailer: Apple Mail (2.915) X-Virus-Checked: Checked by ClamAV on apache.org On Feb 5, 2008, at 2:52 PM, Ronald Park wrote: > > Attached is my patch to 2.0.63 to the proxy_http.c file in > modules/proxy. > I didn't see any attached patch... :/ In any case, the normal process is patch applied to trunk with then backport proposals to 2.2 and 2.0. A feature added to 2.0.x, without it being in 2.2 and trunk is likely not gonna happen.