Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Tue, 1 Feb 2005 21:24:43 +0000
From: Joe Orton <jorton@redhat.com>
To: dev@httpd.apache.org
Subject: Re: mod_proxy and friends, FIX_15207
Message-ID: <20050201212443.GA23023@redhat.com>
Mail-Followup-To: dev@httpd.apache.org
References: <ca97c578d4915e2d2a8f53edb8e1bd6c@jaguNET.com>
 <200502012115.j11LFl28016549@mx1.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <200502012115.j11LFl28016549@mx1.redhat.com>
User-Agent: Mutt/1.4.1i

On Tue, Feb 01, 2005 at 08:23:38PM +0100, Sander Striker wrote:
> > From: Jim Jagielski [mailto:jim@jaguNET.com] 
> > Sent: Tuesday, February 01, 2005 8:03 PM
> 
> > It's been on my table to attack the FIX_15207 fooishness, but neither
> > keeping the define nor commenting it out results in expected, correct
> > behavior :(...
> 
> For my specific use case (mod_rewrite, mod_proxy_ajp, mod_cache) commenting
> it out did the trick.
> 
> What are you running into?  Might be an idea to create a list of things
> that work/don't work and thus need work?

There are now tests for both PR 32459 and PR 15207 in httpd-test's
t/modules/proxy.t; the former fails at the moment in 2.1 and the latter
should fail instead if you flip the silly #define.

joe