Changes between Initial Version and Version 2 of Ticket #63576
- Timestamp:
- 06/16/2025 07:25:13 PM (13 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #63576
- Property Version trunk
-
Ticket #63576 – Description
initial v2 1 In limited circumstances, HTTP requests made using wp-includes/Requests/src/Requests.phpwill incorrectly return an empty string as the response body, even though the request executed and returned a value in the response.1 In limited circumstances, HTTP requests made using `wp-includes/Requests/src/Requests.php` will incorrectly return an empty string as the response body, even though the request executed and returned a value in the response. 2 2 3 This happens when the returned value is PHP-falsey (for example, the string "0") - or in other words, when empty($value)evaluates to true in PHP.3 This happens when the returned value is PHP-falsey (for example, the string `"0"`) - or in other words, when `empty($value)` evaluates to true in PHP. 4 4 5 5 I've encountered this issue in production, so the diff we went with is attached.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)