Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API
| From: | Tim Düsterhus | Date: | Sun, 30 Mar 2025 11:25:15 +0000 |
| Subject: | Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-126977@lists.php.net to get a copy of this message | ||
Hi
On 3/22/25 15:01, Paul M. Jones wrote:
However, WHATWG-URL consistently calls itThis makes sense to me. The WHATWG URL standard usesusername, putting the URL portion of the RFC at odds with the WHATWG-URL spec. Calling itusernamewould be more in line with the spec. That would likely mean calling itusernamein the URI portion of the RFC as well.
username, RFC 3986 uses user, but considers that deprecated in favor of the generic userinfo. user along might be somewhat ambiguous since it could refer to the entire userinfo section or to just the part before the first colon.
Best regards
Tim Düsterhus