Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
MIME-Version: 1.0
In-Reply-To: <CALK=YjNf7C=D_reDUBUs0Ua0Yr_d8OV6TN70qMtSqXWtJbJP+w@mail.gmail.com>
References: <CACsi2515co=FUC4GVmqFKgx8pBVrfGUNsYaJrnMQiMcogow1dQ@mail.gmail.com>
 <4DA8177D-CA1E-4488-90AD-D84D3AE3D113@gbiv.com> <CACsi250oRvhFzsQ1kX8XtcO70nKcBh6p2CAd0kTuxOOcSqrqUA@mail.gmail.com>
 <F663A3B9-5EFF-404B-AB05-05B5ED537CA9@gbiv.com> <5686A40D-D50D-46C6-905F-6D253BF3DF62@jaguNET.com>
 <CACsi252NWrS+GXeW8VuuyKwq=itWev=-kn0vAMKEWsHDT0A+MA@mail.gmail.com> <CALK=YjNf7C=D_reDUBUs0Ua0Yr_d8OV6TN70qMtSqXWtJbJP+w@mail.gmail.com>
From: William A Rowe Jr <wrowe@rowe-clan.net>
Date: Thu, 11 Aug 2016 11:59:02 -0500
Message-ID: <CACsi253shi8NNKo-+BG2BLF2rwGsu6aAh7wbt41qgCr6HN340A@mail.gmail.com>
Subject: Re: HTTP/1.1 strict ruleset
To: httpd <dev@httpd.apache.org>
Content-Type: multipart/alternative; boundary=001a113df448db86890539ceae0f
archived-at: Thu, 11 Aug 2016 16:59:15 -0000

--001a113df448db86890539ceae0f
Content-Type: text/plain; charset=UTF-8

On Thu, Aug 11, 2016 at 11:54 AM, Eric Covener <covener@gmail.com> wrote:

> On Thu, Aug 11, 2016 at 12:44 PM, William A Rowe Jr <wrowe@rowe-clan.net>
> wrote:
> > Just to be clear, that is now 2 votes for eliminating the 'classic
> parser'
> > from all
> > of trunk, 2.4.x and 2.2.x branches, and using only the strict parser,
> > unconditionally.
> >
> > That's actually 3 votes for removing it from trunk, which I planned to do
> > already,
> > after 2.4 and 2.2 backports are in-sync with trunk.
>
> Without yet reviewing the votes, I would (personally) think this kind
> of split makes it your call as the one neck deep in the issue & doing
> all the work.    Thank you for your work on this.
>
> Maybe one last summary of your call, and a short window for strong
> objection/veto?
>

Certainly, that's what the backport proposal of everything from the initial
commit by sf all the way to the present state will accomplish in STATUS.

With so many evolutions of various bits, a summary patch will be provided,
of course. But it's helpful to me to know the opinions of Jim and Roy and
everyone else in advance of proposing that backport.

--001a113df448db86890539ceae0f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Aug 11, 2016 at 11:54 AM, Eric Covener <span dir=3D"ltr">&lt;<a href=3D=
"mailto:covener@gmail.com" target=3D"_blank">covener@gmail.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Thu, Aug 11=
, 2016 at 12:44 PM, William A Rowe Jr &lt;<a href=3D"mailto:wrowe@rowe-clan=
.net">wrowe@rowe-clan.net</a>&gt; wrote:<br>
&gt; Just to be clear, that is now 2 votes for eliminating the &#39;classic=
 parser&#39;<br>
&gt; from all<br>
&gt; of trunk, 2.4.x and 2.2.x branches, and using only the strict parser,<=
br>
&gt; unconditionally.<br>
&gt;<br>
&gt; That&#39;s actually 3 votes for removing it from trunk, which I planne=
d to do<br>
&gt; already,<br>
&gt; after 2.4 and 2.2 backports are in-sync with trunk.<br>
<br>
</span>Without yet reviewing the votes, I would (personally) think this kin=
d<br>
of split makes it your call as the one neck deep in the issue &amp; doing<b=
r>
all the work.=C2=A0 =C2=A0 Thank you for your work on this.<br>
<br>
Maybe one last summary of your call, and a short window for strong<br>
objection/veto?<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Certainly, that&#39=
;s what the backport proposal of everything from the initial</div><div clas=
s=3D"gmail_extra">commit by sf all the way to the present state will accomp=
lish in STATUS.</div><div class=3D"gmail_extra"><br></div><div class=3D"gma=
il_extra">With so many evolutions of various bits, a summary patch will be =
provided,</div><div class=3D"gmail_extra">of course. But it&#39;s helpful t=
o me to know the opinions of Jim and Roy and</div><div class=3D"gmail_extra=
">everyone else in advance of proposing that backport.</div><div class=3D"g=
mail_extra"><br></div><div class=3D"gmail_extra"><br></div></div>

--001a113df448db86890539ceae0f--