Resent-Date: Sat, 03 Aug 2024 14:33:37 +0000
Resent-Message-Id: <E1saFpB-00Dbji-36@mab.w3.org>
Received-SPF: pass (pan.w3.org: domain of gmail.com designates 2001:4860:4864:20::34 as permitted sender) client-ip=2001:4860:4864:20::34; envelope-from=joshco@gmail.com; helo=mail-oa1-x34.google.com;
MIME-Version: 1.0
References: <CAF3KT4QZzx+FXOUHZoy+gPqJjQ+4KdOC+_29vbUANNtZQS4c+A@mail.gmail.com>
 <ba56fad8-e121-4c06-9a2d-783ef82471e0@gmx.de> <CAJV+MGz8hUTqar51V9wV=WPnWETDK+ECjWCTXYS92xXM5HEF_w@mail.gmail.com>
 <cd25a358-1e8a-43b7-ba61-3d16ad28b1e4@gmx.de> <CAF3KT4Q=ezzA2aCHyPg=k583n6vP4gTGP+wxKz+sQezD=GnowQ@mail.gmail.com>
 <CAJV+MGxH4wPK__Z4mGfD3j-KaHpSVjQBFLyM1u+ZwfaSsZGMRQ@mail.gmail.com>
 <247701dae3b2$a1ea1f50$e5be5df0$@gmail.com> <CAJV+MGwZmeAhxK9ooOXJr_jdkqN-Mk_oLS8pWAsdTSCwToaAdg@mail.gmail.com>
 <CAF3KT4Qaw+0LJtgL5=+ojOsmpgz2SUa1=Oz6QTA2=xE6Fy-KMw@mail.gmail.com>
 <026321eb-057c-4f5c-9e2a-4d4b7b290a2d@gmx.de> <CAF3KT4Tm4wHRi3J6A2JEb2329o=prBh4UiUVx_eqOUVkN-ZoiA@mail.gmail.com>
 <47e8c96b-7afa-4d5b-aed2-db7a17f8d087@gmx.de>
In-Reply-To: <47e8c96b-7afa-4d5b-aed2-db7a17f8d087@gmx.de>
From: Josh Cohen <joshco@gmail.com>
Date: Sat, 3 Aug 2024 10:33:19 -0400
Message-ID: <CAF3KT4TmTVL5vm7HStgtXDpXtPJXW7prK+=nFc8AQhn5=B4TNw@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary="000000000000ef61a9061ec853e8"
Subject: Re: Method Mania
Archived-At: <https://www.w3.org/mid/CAF3KT4TmTVL5vm7HStgtXDpXtPJXW7prK+=nFc8AQhn5=B4TNw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

--000000000000ef61a9061ec853e8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks, I was just pondering potential ways to deal with middle boxes or
other infrastructure by detecting their support.

On Sat, Aug 3, 2024 at 3:45=E2=80=AFAM Julian Reschke <julian.reschke@gmx.d=
e> wrote:

> On 02.08.2024 21:44, Josh Cohen wrote:
> > Thanks for the clarification.  Looking at the http2 rfc9113[1], bottom
> > of section 8.3.1, says:
> > "Individual HTTP/2 requests do not carry an explicit indicator of
> > protocol version. All HTTP/2 requests implicitly have a protocol versio=
n
> > of "2.0""
> >
> > So, there's no longer an explicit version string, or header.
> >
> > The reason I asked was when considering new methods.  The option of
> > revving the version of the messaging/semantics layer isn't feasible.
> >
> > https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1
> > <https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1>
>
> There's no problem introducing new methods. The method registry is
> completely orthogonal to the HTTP version.
>
> Best regards, Julian
>
>
>

--=20

---
*Josh Co*hen

--000000000000ef61a9061ec853e8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, I was just pondering potential ways to deal with m=
iddle boxes or other infrastructure by detecting their support.</div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Aug =
3, 2024 at 3:45=E2=80=AFAM Julian Reschke &lt;<a href=3D"mailto:julian.resc=
hke@gmx.de">julian.reschke@gmx.de</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On 02.08.2024 21:44, Josh Cohen wrote:<br>
&gt; Thanks for the clarification.=C2=A0 Looking at the http2 rfc9113[1], b=
ottom<br>
&gt; of section 8.3.1, says:<br>
&gt; &quot;Individual HTTP/2 requests do not carry an explicit indicator of=
<br>
&gt; protocol version. All HTTP/2 requests implicitly have a protocol versi=
on<br>
&gt; of &quot;2.0&quot;&quot;<br>
&gt;<br>
&gt; So, there&#39;s no longer an explicit version string, or header.<br>
&gt;<br>
&gt; The reason I asked was when considering new methods.=C2=A0 The option =
of<br>
&gt; revving the version of the messaging/semantics layer isn&#39;t feasibl=
e.<br>
&gt;<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/htm=
l/rfc9113#section-8.3.1</a><br>
&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/html/rfc9113#section-8=
.3.1" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc=
/html/rfc9113#section-8.3.1</a>&gt;<br>
<br>
There&#39;s no problem introducing new methods. The method registry is<br>
completely orthogonal to the HTTP version.<br>
<br>
Best regards, Julian<br>
<br>
<br>
</blockquote></div><br clear=3D"all"><div><br></div><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr"><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D=
"ltr"><div dir=3D"ltr"><span></span><div><p><font face=3D"monospace, monosp=
ace">---</font><span style=3D"font-family:monospace,monospace"><br></span><=
b><span style=3D"font-family:Calibri,sans-serif">Josh Co</span></b><span st=
yle=3D"font-family:Calibri,sans-serif">hen=C2=A0</span></p><p style=3D"back=
ground-image:initial;background-position:initial;background-repeat:initial"=
><span style=3D"font-family:Arial,sans-serif"></span></p><p></p></div></div=
></div></div></div></div></div></div></div></div></div></div></div>

--000000000000ef61a9061ec853e8--