Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126763
Precedence: bulk
MIME-Version: 1.0
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
 <dd61999c-1ebd-4765-9add-cd8065968965@gmail.com> <CAOV5rgYZ_s1of-igLFEK7oqqh6=3HeYv0=JvvKvvjkcp0F6Q9Q@mail.gmail.com>
 <CAH5C8xV67frqOBCvLt73RM7QO86_pu40sHP5h71_kDRbKPtA8Q@mail.gmail.com>
 <1BCB4144-231D-45EA-A914-98EE8F0F503A@automattic.com> <8E614C9C-BA85-45D8-9A4E-A30D69981C5D@automattic.com>
 <CAH5C8xV69pHnSKWJrVB8EQab7vPhcaXAwYezoG6z3Oj7ZkXBaQ@mail.gmail.com>
 <bc5472e39bc607e2c7accc9d2bd6f239@bastelstu.be> <9bf11a89-39d9-457b-b0ea-789fd07d7370@gmail.com>
 <af6314918964afe648c497fd9d9b7bd8@bastelstu.be> <CAOWwgpk=V=wg3OZC2nx_MNpU652XH7e30+x8y3fCsvTR6z_Etw@mail.gmail.com>
In-Reply-To: <CAOWwgpk=V=wg3OZC2nx_MNpU652XH7e30+x8y3fCsvTR6z_Etw@mail.gmail.com>
Date: Fri, 14 Mar 2025 20:54:22 +0100
Message-ID: <CAH5C8xXseoYsaVkxBXUOBH6w9_eU9Xii+5T_qZyQXftoDHk=nA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000c5414e063052ce32"
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--000000000000c5414e063052ce32
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Nicolas,

For now, let me just quickly respond to your question regarding
__debugInfo():

The RFC is also missing whether __debugInfo returns raw or non-raw
> components. Then, I'm wondering if we need this per-component break for
> debugging at all? It might be less confusing (on this encoding aspect) to
> dump basically what __serialize() returns (under another key than __uri o=
f
> course).
> This would also close the avenue of calling __debugInfo() directly (at th=
e
> cost of making it possibly harder to move away from parse_url(), but I
> don't think we need to make this simpler - getting familiar with the new
> API before would be required and welcome actually.)
>

I mostly have already answered this in my latest message to Ignace: yes, I
think it makes sense to provide a clear picture about the anatomy of an URL
in some cases. The method uses raw component values in order not to skew
the original data.

M=C3=A1t=C3=A9

--000000000000c5414e063052ce32
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Nicolas,<div><br></div><div>For now, l=
et me just quickly respond to your question regarding __debugInfo():</div><=
div><br></div></div><div class=3D"gmail_quote gmail_quote_container"><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(77,77,77);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">=
<div class=3D"gmail_quote"><div>The RFC is also missing whether __debugInfo=
 returns raw or non-raw components. Then, I&#39;m wondering if we need this=
 per-component break for debugging at all? It might be less confusing (on t=
his encoding aspect) to dump basically what=C2=A0__serialize() returns (und=
er another key than __uri of course).</div><div>This would also close the a=
venue of calling __debugInfo() directly (at the cost of making it possibly =
harder to move away from parse_url(), but I don&#39;t think we need to make=
 this simpler - getting familiar=C2=A0with the new API before would be requ=
ired and welcome actually.)</div><div><span style=3D"color:rgb(191,191,191)=
"></span></div></div></div></div></blockquote><div><br></div><div>I mostly =
have already answered this in my latest message to Ignace: yes, I think it =
makes sense to provide a clear picture about the anatomy of an URL in=C2=A0=
some cases. The method uses raw component values in order=C2=A0not to skew =
the=C2=A0original data.</div><div><br></div><div>M=C3=A1t=C3=A9</div></div>=
</div>

--000000000000c5414e063052ce32--