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: 76.96.27.228 is neither permitted
 nor denied by domain of jim@jagunet.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: next steps for range fix in 2.2.x
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: <4E648389.9090505@gknw.net>
Date: Mon, 5 Sep 2011 09:13:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7141F94-5F06-4B5E-B55B-29FCC9CFBDC4@jaguNET.com>
References: 
 <CAKUrXK7hAMaH8pe1_hx2fCst3vMQqbCDyB-JBv-VJHFdk+9vsQ@mail.gmail.com>
 <E563FB5AB3F02844AC749BA39E494AB4053BC806@VF-MBX11.internal.vodafone.com>
 <4E648389.9090505@gknw.net>
To: dev@httpd.apache.org

I can RM 2.2.21=85 it'll be good to get my mind off some things=85

On Sep 5, 2011, at 4:08 AM, Gregg L. Smith wrote:

> On 9/5/2011 12:44 AM, "Pl=FCm, R=FCdiger, VF-Group" wrote:
>>=20
>>=20
>>> -----Original Message-----
>>> From: Jeff Trawick [mailto:trawick@gmail.com]
>>> Sent: Sonntag, 4. September 2011 17:30
>>> To: Apache HTTP Server Development List
>>> Subject: next steps for range fix in 2.2.x
>>>=20
>>> Can anyone fill in any details for the following?
>>>=20
>>> 1. Any known regressions not yet fixed in trunk?
>>> 2. Any other issues not yet fixed in trunk?
>>> a. r1163833 needs to be modified/reverted so that 200 is sent =
instead
>>> of 206 (see discussion for that commit)
>>> 3. Need patch for 2.2.x to review/test; needs r1163833 (or
>>> modification) and following from
>>> http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/http/by
>>> terange_filter.c?sortby=3Ddate&view=3Dlog
>>> 4. Wait to see if more regressions pop up in the next couple of days
>>>=20
>> I guess we should wait until mid week for further regression.
>> After that we should create a backport starting from r1163197 until =
current
>> of byterange_filter.c
>>=20
>> Regards
>>=20
>> R=FCdiger
>>=20
> +1
>=20
> regressions suck, but the killer is silenced as far as I can tell at =
this point, the script fails it's internal test, no need to rush and =
gain more regressions hurrying to fix the regressions from hurrying to =
silence the killer. My meager view anyway :)
>=20
> Regards,
>=20
> Gregg
>=20
>=20
>=20
>=20