Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 68460 invoked from network); 24 Apr 2006 11:47:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Apr 2006 11:47:57 -0000 Received: (qmail 86628 invoked by uid 500); 24 Apr 2006 11:47:38 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 86591 invoked by uid 500); 24 Apr 2006 11:47:38 -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 86580 invoked by uid 99); 24 Apr 2006 11:47:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Apr 2006 04:47:38 -0700 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 [80.229.52.226] (HELO asgard.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Apr 2006 04:47:36 -0700 Received: from asgard (asgard [192.168.10.2]) by asgard.webthing.com (Postfix) with ESMTP id AC7F06451C for ; Mon, 24 Apr 2006 12:47:14 +0100 (BST) From: Nick Kew Organization: WebThing Ltd To: dev@httpd.apache.org Subject: Re: Mod_proxy_http ProxyErrorOverride eating cookies Date: Mon, 24 Apr 2006 12:47:11 +0100 User-Agent: KMail/1.8.3 References: <44311DB6.2010603@hippo.nl> <444CA770.7070908@hippo.nl> In-Reply-To: <444CA770.7070908@hippo.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604241247.13552.nick@webthing.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Monday 24 April 2006 11:24, Bart van der Schans wrote: > Hi all, > > I'm quite new to the list, so I'm just wondering how it works. Jeff > Tharp and I created a bug report and proposed a patch to fix it: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=39245 > > To me it's seems to be a quite trivial patch for something that is just > working incorrectly. It looks like "nothing is happening" :( It neither > accepted nor denied.. To break back-compatibility as suggested there would be wrong. But what you suggest makes sense if we make it a configuration option, maybe by updating the ProxyErrorOverride directive to enable options to treat redirects either as errors or non-errors. -- Nick Kew