[wp-trac] [WordPress Trac] #55610: HTTP response should not be 200 when returning error-page
WordPress Trac
noreply at wordpress.org
Fri Aug 22 13:46:08 UTC 2025
#55610: HTTP response should not be 200 when returning error-page
--------------------------+------------------------------
Reporter: april213 | Owner: (none)
Type: defect (bug) | Status: closed
Priority: normal | Milestone: Awaiting Review
Component: Database | Version:
Severity: major | Resolution: invalid
Keywords: | Focuses:
--------------------------+------------------------------
Changes (by pmbaldha):
* status: new => closed
* resolution: => invalid
Comment:
The bug can't be replicated, so I am closing the ticket as invalid.
== Bug Testing Report
=== Description
❌ The bug can not be replicated
=== Environment
- WordPress: 6.9-alpha-60093-src
- PHP: 8.2.29
- Server: nginx/1.29.1
- Database: mysqli (Server: 8.4.6 / Client: mysqlnd 8.2.29)
- Browser: Chrome 139.0.0.0
- OS: Windows 10/11
- Theme: Twenty Twenty-Five 1.3
- MU Plugins:
* test.php
- Plugins:
* Query Monitor 3.19.0
* Test Reports 1.2.0
=== Steps to Reproduce
1. Create two WordPress website.
2. Add first website's wp-content/mu-plugins/test.php file with below
content:
{{{#!php
<?php
add_action('init', function () {
$args = [
'sslverify' => false,
];
$response = wp_remote_get( 'https://contribution.onpressidium.com
/wp-admin/', $args );
$response_code = wp_remote_retrieve_response_code( $response );
var_dump($response_code);
die;
});
}}}
3. In the second website's wp-config.php file and edit database constant
credential, so second website shows the error as shown in the screenshot:
https://nimb.ws/LWS14xw
4. ✅ Run the first website in the browser, and you will see the 500
response code as shown in the screenshot: https://nimb.ws/FXMSz3Q. It is
as expected.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/55610#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list