Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Tue, 16 Jun 2009 16:21:01 +0100
From: Nick Kew <nick@webthing.com>
To: dev@httpd.apache.org
Subject: Re: DO NOT REPLY [Bug 16142] MUST use strong comparison for Range
 requests
Message-ID: <20090616162101.1971c004@grimnir>
In-Reply-To: <cc67648e0906160814l3931fc9dr6e9c5572f43ee9f6@mail.gmail.com>
References: <bug-16142-7868@https.issues.apache.org/bugzilla/>
	<20090616145431.6F95D234C045@brutus.apache.org>
	<cc67648e0906160814l3931fc9dr6e9c5572f43ee9f6@mail.gmail.com>
Organization: WebThing
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 16 Jun 2009 11:14:16 -0400
Jeff Trawick <trawick@gmail.com> wrote:

> IMO potential HTTP violations should remain open until somebody can
> evaluate them and fix it or explain why the report isn't valid.
> Thoughts?

+1.

Similar applies (less strongly) to other old bugs that haven't been
evaluated just 'cos noone has found a round tuit.

For some bugs like these, a great exercise might be to restructure
them, perhaps with use of meta-bugs like PR 43454.  That makes
things easier as and when someone does find time to hack it.


-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/