Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124004
Content-Type: multipart/alternative; boundary=Apple-Mail-9F8AE4B0-FF6F-435B-8501-4C63F2E19673
Content-Transfer-Encoding: 7bit
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
Date: Fri, 28 Jun 2024 18:28:36 -0500
Message-ID: <2BFBF080-B17B-415E-87CE-4A68C34F06DE@benramsey.com>
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
In-Reply-To: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
To: =?utf-8?Q?M=C3=A1t=C3=A9_Kocsis?= <kocsismate90@gmail.com>
From: ben@benramsey.com (Ben Ramsey)


--Apple-Mail-9F8AE4B0-FF6F-435B-8501-4C63F2E19673
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

> On Jun 28, 2024, at 15:09, M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail.com> w=
rote:
>=20
> =EF=BB=BF
> Hi Everyone,
>=20
> I've been working on a new RFC for a while now, and time has come to prese=
nt it to a wider audience.
>=20
> Last year, I learnt that PHP doesn't have built-in support for parsing URL=
s according to any well established standards (RFC 1738 or the WHATWG URL li=
ving standard), since the parse_url() function is optimized for performance i=
nstead of correctness.
>=20
> In order to improve compatibility with external tools consuming URLs (like=
 browsers), my new RFC would add a WHATWG compliant URL parser functionality=
 to the standard library. The API itself is not final by any means, the RFC o=
nly represents how I imagined it first.
>=20
> You can find the RFC at the following link: https://wiki.php.net/rfc/url_p=
arsing_api
>=20
> Regards,
> M=C3=A1t=C3=A9


The RFC states:

<snip>
The Url\Url class is intentionally compatible with the PSR-7 UriInterface.
</snip>

It mirrors the interface, but it can=E2=80=99t be swapped out for a UriInter=
face instance, especially since it can=E2=80=99t be extended, so I wouldn=E2=
=80=99t consider it compatible. I would still need to write a compatibility l=
ayer that composes Url\Url and implements UriInterface.

<snip>
This makes it possible for a next iteration of the PSR-7 standard to use Url=
\Url directly instead of requiring implementations to provide their own Psr\=
Http\Message\UriInterface implementation.
</snip>

Since PSRs are concerned with shared interfaces and this class is final and d=
oes not implement any interfaces, I=E2=80=99m not sure how you envision =E2=80=
=9Ca next iteration=E2=80=9D of PSR-7 to use this directly, unless what you m=
ean is that UriInterface would be deprecated and applications would type dir=
ectly against Url\Url.

Cheers,
Ben


--Apple-Mail-9F8AE4B0-FF6F-435B-8501-4C63F2E19673
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"><blockquote type=3D"cite">=
On Jun 28, 2024, at 15:09, M=C3=A1t=C3=A9 Kocsis &lt;kocsismate90@gmail.com&=
gt; wrote:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"l=
tr">=EF=BB=BF<div dir=3D"ltr">Hi Everyone,<div><br></div><div>I've been work=
ing on a new RFC for a while now, and time has come to present it to a wider=
 audience.</div><div><br></div><div>Last year, I learnt that PHP doesn't hav=
e built-in support for parsing URLs according to any well established&nbsp;s=
tandards (RFC&nbsp;1738 or the WHATWG URL living standard), since the parse_=
url() function is optimized for performance instead of correctness.</div><di=
v><br></div><div>In order to improve compatibility with external tools consu=
ming&nbsp;URLs (like browsers), my new RFC would add a WHATWG compliant URL p=
arser functionality to the standard library. The API itself is not final by a=
ny means, the RFC only represents how I imagined it first.</div><div><br></d=
iv><div>You can find the RFC at the following link:&nbsp;<a href=3D"https://=
wiki.php.net/rfc/url_parsing_api">https://wiki.php.net/rfc/url_parsing_api</=
a></div><div><br></div><div>Regards,</div><div>M=C3=A1t=C3=A9</div><div></di=
v></div></div></blockquote><br><div><br></div><div><div dir=3D"auto" style=3D=
"font-size: 1rem; -webkit-text-size-adjust: auto; font-family: -apple-system=
, &quot;helvetica neue&quot;; word-spacing: 1px; border-color: rgb(49, 49, 4=
9); color: rgb(49, 49, 49);"><div dir=3D"auto" style=3D"font-size: 1rem; bor=
der-color: rgb(49, 49, 49);">The RFC states:</div><div dir=3D"auto" style=3D=
"font-size: 1rem; border-color: rgb(49, 49, 49);"><br></div><div dir=3D"auto=
" style=3D"font-size: 1rem; border-color: rgb(49, 49, 49);">&lt;snip&gt;</di=
v><div dir=3D"auto" style=3D"font-size: 1rem; border-color: rgb(49, 49, 49);=
">The Url\Url class is intentionally compatible with the PSR-7 UriInterface.=
</div><div dir=3D"auto" style=3D"font-size: 1rem; border-color: rgb(49, 49, 4=
9);">&lt;/snip&gt;</div><div dir=3D"auto" style=3D"font-size: 1rem; border-c=
olor: rgb(49, 49, 49);"><br></div><div dir=3D"auto" style=3D"font-size: 1rem=
; border-color: rgb(49, 49, 49);">It mirrors the interface, but it can=E2=80=
=99t be swapped out for a UriInterface instance, especially since it can=E2=80=
=99t be extended, so I wouldn=E2=80=99t consider it compatible. I would stil=
l need to write a compatibility layer that composes Url\Url and implements U=
riInterface.</div><div dir=3D"auto" style=3D"font-size: 1rem; border-color: r=
gb(49, 49, 49);"><br></div><div dir=3D"auto" style=3D"font-size: 1rem; borde=
r-color: rgb(49, 49, 49);">&lt;snip&gt;</div><div dir=3D"auto" style=3D"font=
-size: 1rem; border-color: rgb(49, 49, 49);">This makes it possible for a ne=
xt iteration of the PSR-7 standard to use Url\Url directly instead of requir=
ing implementations to provide their own Psr\Http\Message\UriInterface imple=
mentation.</div><div dir=3D"auto" style=3D"font-size: 1rem; border-color: rg=
b(49, 49, 49);">&lt;/snip&gt;</div><div dir=3D"auto" style=3D"font-size: 1re=
m; border-color: rgb(49, 49, 49);"><br></div><div dir=3D"auto" style=3D"font=
-size: 1rem; border-color: rgb(49, 49, 49);">Since PSRs are concerned with s=
hared interfaces and this class is final and does not implement any interfac=
es, I=E2=80=99m not sure how you envision =E2=80=9Ca next iteration=E2=80=9D=
 of PSR-7 to use this directly, unless what you mean is that UriInterface wo=
uld be deprecated and applications would type directly against Url\Url.</div=
><div dir=3D"auto" style=3D"font-size: 1rem; border-color: rgb(49, 49, 49);"=
><br></div><div dir=3D"auto" style=3D"font-size: 1rem; border-color: rgb(49,=
 49, 49);">Cheers,</div><div dir=3D"auto" style=3D"font-size: 1rem; border-c=
olor: rgb(49, 49, 49);">Ben</div><div><br></div></div></div></body></html>=

--Apple-Mail-9F8AE4B0-FF6F-435B-8501-4C63F2E19673--