Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123997
Precedence: bulk
MIME-Version: 1.0
Date: Fri, 28 Jun 2024 22:06:14 +0200
Message-ID: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
Subject: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000036d808061bf8c8ba"
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--00000000000036d808061bf8c8ba
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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 (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.

You can find the RFC at the following link:
https://wiki.php.net/rfc/url_parsing_api

Regards,
M=C3=A1t=C3=A9

--00000000000036d808061bf8c8ba
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<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 audien=
ce.</div><div><br></div><div>Last year, I learnt that PHP doesn&#39;t have =
built-in support for parsing URLs according to any well established=C2=A0st=
andards (RFC=C2=A01738 or the WHATWG URL living standard), since the parse_=
url() function is optimized for performance instead of correctness.</div><d=
iv><br></div><div>In order to improve compatibility with external tools con=
suming=C2=A0URLs (like browsers), my new RFC would add a WHATWG compliant U=
RL parser functionality to the standard library. The API itself is not fina=
l 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://wiki.php.net/rfc/url_parsing_api">https://wiki.php.net/rfc/url_pars=
ing_api</a></div><div><br></div><div>Regards,</div><div>M=C3=A1t=C3=A9</div=
><div><br></div></div>

--00000000000036d808061bf8c8ba--