Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129486
Precedence: list
MIME-Version: 1.0
Date: Mon, 1 Dec 2025 21:50:48 +0100
Message-ID: <CAH5C8xXUPKgd0wWwLC3G2Ye=kRZN58gK3DY82v5GoduBNNtb5A@mail.gmail.com>
Subject: [PHP-DEV] [RFC] [Discussion] Followup Improvements for ext/uri
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ef3ec70644ea228c"
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--000000000000ef3ec70644ea228c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Everyone,

I'd like to introduce my latest RFC that I've been working on for a while
now: https://wiki.php.net/rfc/uri_followup.

It proposes 5 followup improvements for ext/uri in the following areas:
- URI Building
- Query Parameter Manipulation
- Accessing Path Segments as an Array
- Host Type Detection
- URI Type Detection
- Percent-Encoding and Decoding Support

I did my best to write an RFC that was at least as extensive as
https://wiki.php.net/rfc/url_parsing_api had become by the end. Despite my
efforts,
there are still a couple things which need a final decision, or which
need to be polished/improved. Some examples:

- How to support array/object values for constructing query strings? (
https://wiki.php.net/rfc/uri_followup#type_support)
- How to make the UriQueryParams and UrlQueryParams classes more
interoperable with the query string component (mainly with respect to
percent-encoding)? (
https://wiki.php.net/rfc/uri_followup#percent-encoding_and_decoding)
- Exactly how the advanced percent-decoding capabilities should work? Does
it make sense to support all the possible modes (UriPercentEncodingMode)
for percent-decoding as well (
https://wiki.php.net/rfc/uri_followup#percent-encoding_and_decoding_support=
)
- etc.

Regards,
M=C3=A1t=C3=A9

--000000000000ef3ec70644ea228c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Everyone,<div><br></div><div>I&#39;d like to introduce =
my latest RFC that I&#39;ve been working on for a while now: <a href=3D"htt=
ps://wiki.php.net/rfc/uri_followup">https://wiki.php.net/rfc/uri_followup</=
a>.</div><div><br></div><div>It proposes 5=C2=A0followup=C2=A0improvements =
for ext/uri in the following areas:</div><div>- URI Building<br>- Query Par=
ameter Manipulation<br>- Accessing Path Segments as an Array<br>- Host Type=
 Detection<br>- URI Type Detection<br>- Percent-Encoding and Decoding Suppo=
rt</div><div><br></div><div>I did my best to write an RFC that was at least=
 as extensive as=C2=A0<a href=3D"https://wiki.php.net/rfc/url_parsing_api">=
https://wiki.php.net/rfc/url_parsing_api</a> had become by the end. Despite=
 my efforts,</div><div>there are still a couple things which need=C2=A0a fi=
nal decision, or which need=C2=A0to be polished/improved. Some examples:</d=
iv><div><br></div><div>- How to support array/object values for constructin=
g query strings? (<a href=3D"https://wiki.php.net/rfc/uri_followup#type_sup=
port">https://wiki.php.net/rfc/uri_followup#type_support</a>)</div><div>- H=
ow to make the UriQueryParams and=C2=A0UrlQueryParams classes more interope=
rable with the query string component (mainly with respect to percent-encod=
ing)? (<a href=3D"https://wiki.php.net/rfc/uri_followup#percent-encoding_an=
d_decoding">https://wiki.php.net/rfc/uri_followup#percent-encoding_and_deco=
ding</a>)</div><div>- Exactly how the advanced percent-decoding capabilitie=
s should work? Does it make sense to support all the possible modes (UriPer=
centEncodingMode) for percent-decoding as well (<a href=3D"https://wiki.php=
.net/rfc/uri_followup#percent-encoding_and_decoding_support">https://wiki.p=
hp.net/rfc/uri_followup#percent-encoding_and_decoding_support</a>)</div><di=
v>- etc.</div><div><br></div><div>Regards,</div><div>M=C3=A1t=C3=A9</div></=
div>

--000000000000ef3ec70644ea228c--