Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124054
Content-Type: text/plain;
	charset=us-ascii
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
In-Reply-To: <45d5a1cc-cb14-4e88-a202-a81554f06979@gmail.com>
Date: Sat, 29 Jun 2024 12:35:46 -0500
Cc: PHP internals <internals@lists.php.net>,
 =?utf-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <E9DF2F8D-50D6-4AB8-B8E0-0BE4A7D7C5F8@benramsey.com>
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
 <45d5a1cc-cb14-4e88-a202-a81554f06979@gmail.com>
To: nyamsprod@gmail.com
From: ben@benramsey.com (Ben Ramsey)

> On Jun 29, 2024, at 03:20, nyamsprod the funky webmaster =
<nyamsprod@gmail.com> wrote:
>=20
> Therefore, I would rather suggest we ALSO include support for RFC3986 =
and RFC3987 specification properly and give both specs a go (at the same =
time!) and a clear way to instantiate your `Url` with one or the other =
spec.
> In clear, my ideal situation would be to add to the parser at least 2 =
named constructors `UrlParser::fromRFC3986` and `UrlParser::fromWHATWG`
> or something similar (name can be changed or improved).
>=20
> While this is an old article by Daniel Stenberg =
(https://daniel.haxx.se/blog/2017/01/30/one-url-standard-please/), it =
conveys with more in depth analysis my issues with the WHATWG spec and =
its usage in PHP if it were to be use as the ONLY available parser in =
PHP core for URL.


I agree that I would love to see a more general IRI parser, with maybe a =
URI parser being a subtype of an IRI parser.

Cheers,
Ben