Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 47114 invoked from network); 8 Dec 2005 02:17:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Dec 2005 02:17:09 -0000 Received: (qmail 59781 invoked by uid 500); 8 Dec 2005 02:17:05 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 59735 invoked by uid 500); 8 Dec 2005 02:17:05 -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 59724 invoked by uid 99); 8 Dec 2005 02:17:05 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2005 18:17:05 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.249.34.130] (HELO picanmix.dev.day.com) (212.249.34.130) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2005 18:17:04 -0800 Received: from eu-mail.day.com (eu-mail.dev.day.com [10.0.0.30]) by picanmix.dev.day.com (DAY) with ESMTP id jB82GgO02891 for ; Thu, 8 Dec 2005 03:16:42 +0100 (MET) Received: from [10.2.8.78] ([10.2.8.78]) by eu-mail.day.com (Lotus Domino Release 5.0.8) with ESMTP id 2005120803163959:12989 ; Thu, 8 Dec 2005 03:16:39 +0100 Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: Message-Id: From: "Roy T. Fielding" Subject: Re: AW: 2.2 mod_http_proxy and "partial" pages Date: Wed, 7 Dec 2005 18:16:42 -0800 To: dev@httpd.apache.org X-Mailer: Apple Mail (2.746.2) X-MIMETrack: Itemize by SMTP Server on eu-mail/Day(Release 5.0.8 |June 18, 2001) at 12/08/2005 03:16:39 AM, Serialize by Router on eu-mail/Day(Release 5.0.8 |June 18, 2001) at 12/08/2005 03:16:41 AM, Serialize complete at 12/08/2005 03:16:41 AM Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Dec 7, 2005, at 8:44 AM, Pl=FCm, R=FCdiger, VIS wrote: >> Nope, that's the flag we set when we want the core to drop >> the connection. I thought that it would be set by the filters >> when a connection was dropped, but, as I said earlier in this >> thread, I'm wrong. The filters will never ever set it. -- justin > > Ok. Then I withdraw my objections against the setting of c->aborted. > I just understood its purpose wrong. Thanks for clarification. No, you understood its purpose correctly. I have no idea what Justin is talking about -- maybe the proxy's connection to the outbound server? c->aborted is only set on the inbound connection when a previous write to that connection has failed. Setting the inbound c->aborted within a filter just to indicate that the outbound connection has died is wrong -- it prevents other parts of the server (that are working fine) from correctly handling the bad gateway response. -1 VETO Find another solution before the next release. I have no objection to such a workaround as a patch, but we don't introduce new spaghetti code just to fix a trivial problem. ....Roy=