Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124000
Precedence: bulk
MIME-Version: 1.0
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
In-Reply-To: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
Date: Fri, 28 Jun 2024 23:02:08 +0200
Message-ID: <CANS-=pfwCwfqdo_HPPB6RKf5hGU9gnY_xyu+Ta4q9rsBQPKs+A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000021ec01061bf991e4"
From: kjarli@gmail.com (Lynn)

--00000000000021ec01061bf991e4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 28, 2024 at 10:08=E2=80=AFPM M=C3=A1t=C3=A9 Kocsis <kocsismate9=
0@gmail.com> wrote:

> Hi Everyone,
>
> I've been working on a new RFC for a while now, and time has come to
> present it to a wider audience.
>
> Last year, I learnt that PHP doesn't have built-in support for parsing
> URLs according to any well established standards (RFC 1738 or the WHATWG
> URL living standard), since the parse_url() function is optimized for
> performance instead of correctness.
>
> In order to improve compatibility with external tools consuming URLs (lik=
e
> browsers), my new RFC would add a WHATWG compliant URL parser functionali=
ty
> to the standard library. The API itself is not final by any means, the RF=
C
> only represents how I imagined it first.
>
> You can find the RFC at the following link:
> https://wiki.php.net/rfc/url_parsing_api
>
> Regards,
> M=C3=A1t=C3=A9
>
>
This is a great addition to have! I see there's nothing specifically about
`__toString` in the RFC, is this aiming to do the same as PSR-7?

--00000000000021ec01061bf991e4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun 28, 2024 at 10:08=E2=80=
=AFPM M=C3=A1t=C3=A9 Kocsis &lt;<a href=3D"mailto:kocsismate90@gmail.com">k=
ocsismate90@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div dir=3D"ltr">Hi Everyone,<div><br></div><div>I&#39=
;ve been working 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&#39;t have built-in support for parsing URLs according to any wel=
l established=C2=A0standards (RFC=C2=A01738 or the WHATWG URL living standa=
rd), since the parse_url() function is optimized for performance instead of=
 correctness.</div><div><br></div><div>In order to improve compatibility wi=
th external tools consuming=C2=A0URLs (like browsers), my new RFC would add=
 a WHATWG compliant URL parser functionality to the standard library. The A=
PI itself is not final by any means, the RFC only represents how I imagined=
 it first.</div><div><br></div><div>You can find the RFC at the following l=
ink:=C2=A0<a href=3D"https://wiki.php.net/rfc/url_parsing_api" target=3D"_b=
lank">https://wiki.php.net/rfc/url_parsing_api</a></div><div><br></div><div=
>Regards,</div><div>M=C3=A1t=C3=A9</div><div><br></div></div></blockquote><=
div><br></div><div>This is a great addition to have! I see there&#39;s noth=
ing specifically about `__toString` in the RFC, is this aiming to do the sa=
me as PSR-7?</div></div></div>

--00000000000021ec01061bf991e4--