Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API
| From: | Ben Ramsey | Date: | Sat, 29 Jun 2024 17:35:46 +0000 |
| Subject: | Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124054@lists.php.net to get a copy of this message | ||
> On Jun 29, 2024, at 03:20, nyamsprod the funky webmaster <nyamsprod@gmail.com> wrote:
>
> 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 5 )
> ® únÞ6ã3åôUrlParser::fromRFC3986 and
> UrlParser::fromWHATWG
> or something similar (name can be changed or improved).
>
> 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