If PHP throws a FATAL error, a 200 response will be returned.
This could mean that the 200 'OK' response gets cached by a browser, a reverse proxy, or a CDN.
I was sure PHP could return a 500 is maybe display_errors were turned off, but from testing this wasn't happening for me.
If we set the status code to 500 in index.php, before any other code is run, we can ensure that PHP will return a 500 response code for FATAL errors. All other cases will be handled by a Response object, so will have the correct/intended status code
Needs work
11.0 🔥
base system
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Same problem on PHP 8.2. Drupal 10.2.8.
Any plan?
Adding triage comments per #33:
cilefen
@catch, @effulgentsia, @xjm and I discussed this issue and we agree that it is properly prioritized at major because the framework is not producing the correct status codes. @Cottser and @alexpott supported the decision in separate communications.