Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123998
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 22:21:33 +0200
Message-ID: <CADyq6s+2rXorYK2j+KmitbazTKYJxKaAHa__EcGNzo3EgXF5eg@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="0000000000002314ee061bf8ff1b"
From: ocramius@gmail.com (Marco Pivetta)

--0000000000002314ee061bf8ff1b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey M=C3=A1t=C3=A9,

On Fri, 28 Jun 2024, 22:06 M=C3=A1t=C3=A9 Kocsis, <kocsismate90@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
>

So far, amazing ! =F0=9F=91=8F

--0000000000002314ee061bf8ff1b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hey M=C3=A1t=C3=A9,<br><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, 28 Jun 2024, 22:06 M=C3=A1t=
=C3=A9 Kocsis, &lt;<a href=3D"mailto:kocsismate90@gmail.com">kocsismate90@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr">Hi Everyone,<div><br></div><div>I&#39;ve been working on a new RFC fo=
r a while now, and time has come to present it to a wider audience.</div><d=
iv><br></div><div>Last year, I learnt that PHP doesn&#39;t have built-in su=
pport for parsing URLs according to any well established=C2=A0standards (RF=
C=C2=A01738 or the WHATWG URL living standard), since the parse_url() funct=
ion is optimized for performance instead of correctness.</div><div><br></di=
v><div>In order to improve compatibility with external tools consuming=C2=
=A0URLs (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 only represents how I imagined it first.</div><div><br></div=
><div>You can find the RFC at the following link:=C2=A0<a href=3D"https://w=
iki.php.net/rfc/url_parsing_api" target=3D"_blank" rel=3D"noreferrer">https=
://wiki.php.net/rfc/url_parsing_api</a></div><div><br></div><div>Regards,</=
div><div>M=C3=A1t=C3=A9</div><div></div></div></blockquote></div></div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">So far, amazing ! =F0=9F=91=8F</d=
iv></div>

--0000000000002314ee061bf8ff1b--