PHP Wiki

query_params

kocsismate (kocsismate@undisclosed.example.com) — 2026-10-19T11:59:11+00:00

2026/10/19 07:58		current
Line 165:		Line 165:
	public function toRfc3986String(): string {}		public function toRfc3986String(): string {}

-	public function toWhatWgString(): string {}	+	public function toWhatWgUrlString(): string {}

	public function __serialize(): array {}		public function __serialize(): array {}
Line 258:		Line 258:
	$url = new Uri\WhatWg\Url("https://example.com/");		$url = new Uri\WhatWg\Url("https://example.com/");

-	$url = $url->withQuery($params->toWhatWgString()); // Success: the query is automatically percent-encoded to "%23foo=bar"	+	$url = $url->withQuery($params->toWhatWgUrlString()); // Success: the query is automatically percent-encoded to "%23foo=bar"
	</code>		</code>

Line 331:		Line 331:
	var_dump($params->getFirst("baz")); // string(3) "%GG"		var_dump($params->getFirst("baz")); // string(3) "%GG"

-	echo $params->toWhatWgString(); // foo=%25&bar=%252&baz=%25GG	+	echo $params->toWhatWgUrlString(); // foo=%25&bar=%252&baz=%25GG
	</code>		</code>

Line 356:		Line 356:
	var_dump($params->getFirst("bar")); // string(2) "é"		var_dump($params->getFirst("bar")); // string(2) "é"

-	echo $params->toWhatWgString(); // foo=%EF%BF%BD&bar=%C3%A9	+	echo $params->toWhatWgUrlString(); // foo=%EF%BF%BD&bar=%C3%A9
	</code>		</code>

Line 492:		Line 492:
	echo $params->toRfc1866String(); // foo=bar&foo=baz		echo $params->toRfc1866String(); // foo=bar&foo=baz
	echo $params->toRfc3986String(); // foo=bar&foo=baz		echo $params->toRfc3986String(); // foo=bar&foo=baz
-	echo $params->toWhatWgString(); // foo=bar&foo=baz	+	echo $params->toWhatWgUrlString(); // foo=bar&foo=baz
	</code>		</code>

-	All ''toString()'' methods (''Uri\QueryParams::toRfc1866String()'', ''Uri\QueryParams::toRfc3986String()'', ''Uri\QueryParams::toWhatWgString*()'') automatically percent-encode their output according to the rules outlined in the [[https://wiki.php.net/rfc/query_params#percent-encoding_and_decoding\|previous section]], otherwise it would be possible that an invalid output is returned.	+	All ''toString()'' methods (''Uri\QueryParams::toRfc1866String()'', ''Uri\QueryParams::toRfc3986String()'', ''Uri\QueryParams::toWhatWgUrlString*()'') automatically percent-encode their output according to the rules outlined in the [[https://wiki.php.net/rfc/query_params#percent-encoding_and_decoding\|previous section]], otherwise it would be possible that an invalid output is returned.

	<code php>		<code php>
Line 501:		Line 501:
	echo $params->toRfc1866String(); // foo%5B%5D=bar+baz		echo $params->toRfc1866String(); // foo%5B%5D=bar+baz
	echo $params->toRfc3986String(); // foo%5B%5D=bar%20baz		echo $params->toRfc3986String(); // foo%5B%5D=bar%20baz
-	echo $params->toWhatWgString(); // foo%5B%5D=bar+baz	+	echo $params->toWhatWgUrlString(); // foo%5B%5D=bar+baz
	</code>		</code>

Line 546:		Line 546:
	</code>		</code>

-	''withQueryParams()'' creates a new URI or URL with its entire query component replaced. It uses ''toRfc3986String()'' for ''Uri\Rfc3986\Uri'' and ''toWhatWgString()'' for ''Uri\WhatWg\Url''. Passing ''null'' removes the query component.	+	''withQueryParams()'' creates a new URI or URL with its entire query component replaced. It uses ''toRfc3986String()'' for ''Uri\Rfc3986\Uri'' and ''toWhatWgUrlString()'' for ''Uri\WhatWg\Url''. Passing ''null'' removes the query component.

	<code php>		<code php>
Line 564:		Line 564:
	Although preserving the original query string where possible was an important design goal, parsing and recomposing cannot always reproduce the original query string. ''QueryParams'' stores decoded parameter names and values, so the original percent-encoded representation is not retained. For example, ''x=/'' and ''x=%2F'' both produce the same parameter list, containing the name ''"x"'' and the value ''"/"'', and recomposition cannot distinguish between these original representations.		Although preserving the original query string where possible was an important design goal, parsing and recomposing cannot always reproduce the original query string. ''QueryParams'' stores decoded parameter names and values, so the original percent-encoded representation is not retained. For example, ''x=/'' and ''x=%2F'' both produce the same parameter list, containing the name ''"x"'' and the value ''"/"'', and recomposition cannot distinguish between these original representations.

-	Moreover, parsing and recomposing a WHATWG URL query string does not necessarily preserve its original string representation. The WHATWG URL specification defines different percent-encoding rules for URL query components and ''application/x-www-form-urlencoded'' data. For example, a space represented as ''%20'' in the original URL becomes ''+'' when recomposed by ''toWhatWgString()'':	+	Moreover, parsing and recomposing a WHATWG URL query string does not necessarily preserve its original string representation. The WHATWG URL specification defines different percent-encoding rules for URL query components and ''application/x-www-form-urlencoded'' data. For example, a space represented as ''%20'' in the original URL becomes ''+'' when recomposed by ''toWhatWgUrlString()'':

	<code php>		<code php>
Line 618:		Line 618:
	Therefore, callers should pass decoded names and values to these methods. For example, ''$params->append("foo[]", "abc")'' produces the expected "''foo%5B%5D=abc''" query string when recomposed.		Therefore, callers should pass decoded names and values to these methods. For example, ''$params->append("foo[]", "abc")'' produces the expected "''foo%5B%5D=abc''" query string when recomposed.

-	''append()'' and ''set()'' also preserve the bytes of string parameter names and values without UTF-8 validation or replacement. Invalid UTF-8 sequences remain in the parameter list: RFC 1866 and RFC 3986-based recomposition methods percent-encode their original bytes, while ''toWhatWgString()'' replaces them with ''U+FFFD'' when producing its output, leaving the stored data unchanged.	+	''append()'' and ''set()'' also preserve the bytes of string parameter names and values without UTF-8 validation or replacement. Invalid UTF-8 sequences remain in the parameter list: RFC 1866 and RFC 3986-based recomposition methods percent-encode their original bytes, while ''toWhatWgUrlString()'' replaces them with ''U+FFFD'' when producing its output, leaving the stored data unchanged.

	Removing parameters is possible via either the ''delete()'' or the ''deleteValue()'' method: the former one removes all occurrences of the given parameter name, while the latter one removes all occurrences of a parameter if the given name and value both match it, as demonstrated below:		Removing parameters is possible via either the ''delete()'' or the ''deleteValue()'' method: the former one removes all occurrences of the given parameter name, while the latter one removes all occurrences of a parameter if the given name and value both match it, as demonstrated below:

rfc

calvinb (calvinb@undisclosed.example.com) — 2026-10-16T19:48:36+00:00

2026/10/16 16:54		current
Line 21:		Line 21:
	This section is for RFCs that have been announced on the PHP "internals" mail list.		This section is for RFCs that have been announced on the PHP "internals" mail list.

		+	* [[rfc/pdo_binary\|PDO binary parameter support]] (Created 2026-09-29, Discussion started 2026-10-16)
	* [[rfc:case_insensitive_ini_get_all\|Case-insensitive extension names in ini_get_all()]] (Created 2026-10-17, Discussion started 2026-10-17)		* [[rfc:case_insensitive_ini_get_all\|Case-insensitive extension names in ini_get_all()]] (Created 2026-10-17, Discussion started 2026-10-17)
	* [[rfc:json_comments_trailing_commas\|Opt-in JSON Comments and Trailing Commas]] (Created 2026-10-13, Discussion started 2026-10-13)		* [[rfc:json_comments_trailing_commas\|Opt-in JSON Comments and Trailing Commas]] (Created 2026-10-13, Discussion started 2026-10-13)
Line 89:		Line 90:
	This section is for early drafts of RFCs that have NOT been announced on the PHP "internals" mail list.		This section is for early drafts of RFCs that have NOT been announced on the PHP "internals" mail list.

-	* [[rfc/pdo_binary\| PDO binary parameter support]] (Created 2026-09-29)
	* [[rfc/array_str_contains\|Add array_str_contains() function to standard library]] - Sepehr Mahmoudi		* [[rfc/array_str_contains\|Add array_str_contains() function to standard library]] - Sepehr Mahmoudi
	* [[rfc:deprecations_php_8_7\|Deprecations for PHP 8.7]] (Created 2026-08-12)		* [[rfc:deprecations_php_8_7\|Deprecations for PHP 8.7]] (Created 2026-08-12)

pdo_binary

calvinb (calvinb@undisclosed.example.com) — 2026-10-16T19:47:33+00:00

2026/10/06 20:53		current
Line 1:		Line 1:
	====== PHP RFC: PDO binary parameter support ======		====== PHP RFC: PDO binary parameter support ======
-	* Version: 0.3	+	* Version: 0.4
	* Date: 2026-09-29		* Date: 2026-09-29
	* Author: Calvin Buckley, calvinb@php.net		* Author: Calvin Buckley, calvinb@php.net
-	* Status: Draft	+	* Status: Under Discussion
	* Implementation: https://github.com/php/php-src/pull/11674		* Implementation: https://github.com/php/php-src/pull/11674
-	* Discussion thread: tbd	+	* Discussion thread: https://news-web.php.net/php.internals/132876
	* Voting thread: tbd		* Voting thread: tbd

Line 178:		Line 178:

	===== Changelog =====		===== Changelog =====
		+	* 0.4: Under Discussion
	* 0.3: Minor changes		* 0.3: Minor changes
	* 0.2: Suggestions on clarification on interactions (thanks to Saki)		* 0.2: Suggestions on clarification on interactions (thanks to Saki)
	* 0.1: Created.		* 0.1: Created.

case_insensitive_ini_get_all - update status

weilindu (weilindu@undisclosed.example.com) — 2026-10-16T16:46:22+00:00

2026/10/16 16:46		current
Line 5:		Line 5:
	* Status: Under Discussion		* Status: Under Discussion
	* Implementation: TBD		* Implementation: TBD
-	* Discussion thread: [[https://externals.io/message/132226\|Initial discussion]]	+	* Discussion thread: [[https://externals.io/message/132226\|Initial discussion]] [[https://news-web.php.net/php.internals/132875\|Official RFC thread]]

	===== Introduction =====		===== Introduction =====

throw_error_for_invalid_characters_for_number_base

sjoerd (sjoerd@undisclosed.example.com) — 2026-10-16T08:13:10+00:00

2026/10/16 07:38		current
Line 11:		Line 11:
	* https://news-web.php.net/php.internals/105740		* https://news-web.php.net/php.internals/105740
	* https://news-web.php.net/php.internals/132379		* https://news-web.php.net/php.internals/132379
-	* Voting thread: tbd	+	* Voting thread: https://news-web.php.net/php.internals/132873

	===== Introduction =====		===== Introduction =====

reldateformatter - update status

weilindu (weilindu@undisclosed.example.com) — 2026-10-14T07:02:33+00:00

2026/10/07 16:10		current
Line 3:		Line 3:
	* Date: 2026-08-09		* Date: 2026-08-09
	* Author: Weilin Du <weilindu@php.net>		* Author: Weilin Du <weilindu@php.net>
-	* Status: Under Discussion	+	* Status: Voting
	* Implementation: https://github.com/php/php-src/pull/23514		* Implementation: https://github.com/php/php-src/pull/23514
	* Discussion thread: https://externals.io/message/132187		* Discussion thread: https://externals.io/message/132187

start - old revision restored (2026/09/04 09:06)

svpernova09 (svpernova09@undisclosed.example.com) — 2026-10-13T22:23:11+00:00

2026/10/13 22:30		current
Line 1:		Line 1:
	====== The PHP.net wiki ======		====== The PHP.net wiki ======
-	Welcome to the PHP Wiki pages! This wiki is mainly used to track internal development of the PHP project, so feel free to scour the wiki and join the project	+	Welcome to the PHP Wiki pages! This wiki is mainly used to track internal development of the PHP project, so feel free to scour the wiki and join the project.

	You can view a list of [[/?do=recent\|recently changed pages]].		You can view a list of [[/?do=recent\|recently changed pages]].

json_comments_trailing_commas

otar (otar@undisclosed.example.com) — 2026-10-13T19:24:02+00:00

surface3d.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-19T13:48:10+00:00

	current

scaled_on_load_rotate.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-17T06:47:24+00:00

	current

watermarked.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-17T03:57:25+00:00

	current

scale_entropy_visual_check.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-14T03:12:03+00:00

	current

textcurve.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-10T14:08:53+00:00

1783692513	current

gradient_art.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:32:24+00:00

	current

tiger.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:32:03+00:00

	current

gradient_operators.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:31:36+00:00

	current

coroutine-lifecycle.svg - created

edmond (edmond@undisclosed.example.com) — 2025-04-16T07:24:46+00:00

	current

supervisor.svg - created

edmond (edmond@undisclosed.example.com) — 2025-03-16T08:38:59+00:00

	current

exception_flow.svg - created

edmond (edmond@undisclosed.example.com) — 2025-03-16T08:38:59+00:00

	current

resume_and_notifier.svg - created

edmond (edmond@undisclosed.example.com) — 2025-02-16T08:40:05+00:00

	current

2026/10/13 18:46		current
Line 71:		Line 71:
	The parser discards each comment, so a comment has no effect on the result. These rules apply:		The parser discards each comment, so a comment has no effect on the result. These rules apply:
	* A comment can occur at each position where JSON permits whitespace: before a value, after a value, and between two tokens.		* A comment can occur at each position where JSON permits whitespace: before a value, after a value, and between two tokens.
-	* A comment cannot occur inside a token. For example, ''%%tr//ue%%'' and ''%%-//1%%'' cause a syntax error.	+	* A comment cannot occur inside a token. For example, ''%%tr//ue%%'' and ''%%-//1%%'' cause a syntax error. A comment can directly follow a token, for example ''%%1.5/note/%%''.
	* Text inside a string is never a comment. ''%%"https://example.com/*"%%'' is a normal string.		* Text inside a string is never a comment. ''%%"https://example.com/*"%%'' is a normal string.
	* A line comment ends at a line feed (LF), at a carriage return (CR), or at CR LF. U+2028 and U+2029 do not end a line comment.		* A line comment ends at a line feed (LF), at a carriage return (CR), or at CR LF. U+2028 and U+2029 do not end a line comment.
	* Block comments do not nest. The first ''%%*/%%'' ends the comment.		* Block comments do not nest. The first ''%%*/%%'' ends the comment.
		+	* The '''' in ''%%/%%'' cannot also close the comment. Thus ''%%//1%%'' is an unterminated comment, and ''%%/*/1%%'' is the value 1.
	* The parser does not accept ''#'' comments.		* The parser does not accept ''#'' comments.
	* A comment is not a value. Input with only comments causes a syntax error, the same as empty input.		* A comment is not a value. Input with only comments causes a syntax error, the same as empty input.
-	* A comment can contain all valid UTF-8 characters. This includes the control characters U+0000 to U+001F. These characters cannot go into the result, because the parser discards the comment text. JavaScript also accepts them in comments.	+	* A comment can contain all valid UTF-8 characters except NUL (U+0000). This includes the control characters U+0001 to U+001F. These characters cannot go into the result, because the parser discards the comment text.
		+	* A NUL byte in a comment causes ''JSON_ERROR_CTRL_CHAR'' at the position of the NUL byte, the same as a NUL byte outside a comment. ''JSON_INVALID_UTF8_IGNORE'' and ''JSON_INVALID_UTF8_SUBSTITUTE'' do not change this. Some other parsers end a comment at a NUL byte. The error prevents a different result in PHP for the same input.
	* Invalid UTF-8 in a comment causes ''JSON_ERROR_UTF8'', the same as in a string. With ''JSON_INVALID_UTF8_IGNORE'' or ''JSON_INVALID_UTF8_SUBSTITUTE'', the parser ignores invalid bytes in comments. No U+FFFD goes into the result, because the parser discards the comment text.		* Invalid UTF-8 in a comment causes ''JSON_ERROR_UTF8'', the same as in a string. With ''JSON_INVALID_UTF8_IGNORE'' or ''JSON_INVALID_UTF8_SUBSTITUTE'', the parser ignores invalid bytes in comments. No U+FFFD goes into the result, because the parser discards the comment text.
	* An unterminated block comment causes ''JSON_ERROR_SYNTAX''. The error location is the position of its ''%%/*%%''.		* An unterminated block comment causes ''JSON_ERROR_SYNTAX''. The error location is the position of its ''%%/*%%''.
-	* Error locations count the lines inside comments. Thus ''near location 3:5'' always points to the correct line of the original input.	+	* Error locations count the lines inside comments. As outside comments, only LF and CR LF start a new line. A CR alone ends a line comment, but it does not start a new line. Thus ''near location 3:5'' always points to the correct line of the original input.

	==== JSON_ALLOW_TRAILING_COMMAS ====		==== JSON_ALLOW_TRAILING_COMMAS ====
Line 212:		Line 214:
	==== To Existing Extensions ====		==== To Existing Extensions ====
	Only ext/json changes. The internal C parser API (''php_json_parser_init()'') accepts the two new option bits. Other extensions that use this API see no change, unless they give the new bits.		Only ext/json changes. The internal C parser API (''php_json_parser_init()'') accepts the two new option bits. Other extensions that use this API see no change, unless they give the new bits.
		+
		+	The PR adds the macros ''PHP_JSON_ALLOW_COMMENTS'' and ''PHP_JSON_ALLOW_TRAILING_COMMAS'' to the public header ''php_json.h''. The labeler bot of php-src marks each change to this header as "ABI break". The PR does not change a struct or a function signature.

	==== To SAPIs ====		==== To SAPIs ====
Line 217:		Line 221:

	==== Performance ====		==== Performance ====
-	I have measured CPU instructions with Callgrind (Valgrind 3.22, GCC 13.3, ''-O2''). The input was a pretty-printed JSON document of 7.6 MB with 20,000 objects. The count includes only the call of ''json_decode()'' or ''json_validate()''.	+	I have measured CPU instructions with Callgrind (Valgrind 3.22, GCC 13.3, ''-O2'') on commit a4cd163 of the PR and its master base. The input was a pretty-printed JSON document of 7.6 MB with 20,000 objects. The count includes only the call of ''json_decode()'' or ''json_validate()''.

	^ Call and input ^ master ^ This RFC ^ Change ^		^ Call and input ^ master ^ This RFC ^ Change ^
-	\| ''json_decode()'', strict JSON, no new flag \| 354,777,244 \| 361,736,086 \| +1.96% \|	+	\| ''json_decode()'', strict JSON, no new flag \| 354,777,244 \| 360,436,080 \| +1.60% \|
-	\| ''json_validate()'', strict JSON, no new flag \| 333,889,491 \| 340,848,015 \| +2.08% \|	+	\| ''json_validate()'', strict JSON, no new flag \| 333,889,491 \| 339,548,009 \| +1.69% \|
-	\| ''json_decode()'', strict JSON, both new flags \| - \| 361,736,086 \| Same as without the flags \|	+	\| ''json_decode()'', strict JSON, both new flags \| - \| 360,436,080 \| Same as without the flags \|
-	\| ''json_decode()'', 10.8 MB with a line comment on each line, both new flags \| - \| 407,936,312 \| - \|	+	\| ''json_decode()'', 10.8 MB with a line comment on each line, both new flags \| - \| 405,796,303 \| - \|

-	All extra instructions are in the scanner. The Bison parser uses 0.24% fewer instructions than before. Two small scanner changes reduce the extra cost for strict JSON to +0.62% (''json_decode()'') and +0.66% (''json_validate()''). These changes do not change behavior:	+	All extra instructions are in the scanner. The Bison parser uses the same number of instructions as before. Two small scanner changes reduce the extra cost for strict JSON to +0.56% (''json_decode()'') and +0.59% (''json_validate()''). These changes do not change behavior:
-	* The scanner keeps the start position of an open block comment in the ''php_json_scanner'' struct. The current code fills three local variables at the start of each ''php_json_scan()'' call.	+	* The scanner keeps the line data of an open block comment in the ''php_json_scanner'' struct. The current code fills two local variables at the start of each ''php_json_scan()'' call. This change adds two fields to the struct.
	* After whitespace or a line break, the scanner jumps directly back to the JSON state. It does not go through the state dispatch again.		* After whitespace or a line break, the scanner jumps directly back to the JSON state. It does not go through the state dispatch again.

Line 262:		Line 266:
	===== Patches and Tests =====		===== Patches and Tests =====
	* Implementation: https://github.com/php/php-src/pull/23336		* Implementation: https://github.com/php/php-src/pull/23336
-	* The PR adds six test files to ''ext/json/tests'' and updates ''json_validate_002.phpt''. The tests cover comment positions, malformed comments, UTF-8 handling, trailing commas, other flags and error locations.	+	* The PR adds six test files to ''ext/json/tests'' and updates ''json_validate_002.phpt''. The tests cover comment positions, comment delimiters, malformed comments, NUL bytes and invalid UTF-8 in comments, trailing commas, other flags and error locations.
-	* The JSON fuzzer (''sapi/fuzzer/fuzzer-json.c'') also runs with the new flags.	+	* The JSON fuzzer (''sapi/fuzzer/fuzzer-json.c'') also runs with the new flags. Its dictionary (''sapi/fuzzer/json.dict'') contains the new tokens.
		+	* The PR adds UPGRADING notes for the two flags and the two constants.
	* Differential test: generated 120,025 inputs. The test decoded each input with ''json_decode()'' and five current flag sets, and validated it with ''json_validate()'' and two flag sets (840,175 checks). The results, error codes and error messages are the same on master and on this branch.		* Differential test: generated 120,025 inputs. The test decoded each input with ''json_decode()'' and five current flag sets, and validated it with ''json_validate()'' and two flag sets (840,175 checks). The results, error codes and error messages are the same on master and on this branch.
	* Superset test: 21,963 checks with valid strict JSON gave the same result with all three combinations of the new flags.		* Superset test: 21,963 checks with valid strict JSON gave the same result with all three combinations of the new flags.
Line 313:		Line 318:

	===== Changelog =====		===== Changelog =====
-	* 1.0 (2026-10-12): First version. After the pre-RFC thread, the RFC adds the relation to JSON5, JSONC and JWCC, the reasons for two flags, and test and performance data.	+	* 1.0 (2026-10-12): First version on the wiki. Changes after the pre-RFC thread and the first draft implementation:
		+	* The RFC explains the relation to JSON5, JSONC and JWCC.
		+	* The RFC gives the reasons for two flags, not one ''JSON_ALLOW_JSONC'' flag.
		+	* A NUL byte in a comment now causes ''JSON_ERROR_CTRL_CHAR''. The first draft accepted it as comment text.
		+	* A CR alone in a comment no longer starts a new line in error locations.
		+	* The RFC adds test results and performance measurements.