HTTP status 200 returned for ”Additional uncaught exception thrown while handling exception”

Does Drupal 8 do the same thing?

Ran into this as well. One common way you might hit this is if you have a cache class that throws an exception in the page cache bootstrap phase (e.g. Redis cannot connect or server goes away). This will cause the error logger to attempt to load the maintenance theme, which will attempt to load modules/themes, which will eventually result in a cache_get() attempt (which will throw another exception).

Moving back to needs work as you would want to set response code to 500 regardless of whether or not errors can be displayed.

Patch to account for that, with explanation text.

Updated patch with minor change to status text to better align with HTTP standards.

Tested and it works great, thanks!

We've just deployed this patch into production for all of our sites (we're using docker with Redis pods, and they'll generate 500's on respawn which were being occasionally cached at the edge as 200's before this patch).

Given the relatively low complexity of the patch and large upside in these scenarios, we'd support this patch making it's way into core.

Hi all,

I would like to push this patch forward.
Do you know if it's already in D8?

Thanks.

I mostly sure that this is already in D8, see core/includes/errors.inc, around line 265.

RTBC + 1, let get this in -- it's a good stepping stone (incidentally I also ran into this yesterday)

Fixed! Thanks all !