Problem/Motivation

Follow up from #2828706: ExceptionLoggingSubscriber should not log HTTP 4XX errors using PHP logger channel From @chi

+ 502 => 'php',

I know this issue is specifically about 4xx errors, but i'd like to point that 5xx errors shouldn't be always logged in PHP channel. For example I have a project where Drupal serves as a gateway to another site. So when the upstream site fails Drupal returns 502 exception. That's part of normal workflow and has nothing to do with PHP.

I think PHP channel should only be used for exceptions that got 500 status code in FinalExceptionSubscriber. That might need a separate issue.

Steps to reproduce

TBD

Proposed resolution

TBD

Remaining tasks

Determine if we don't want to log 5xx

User interface changes

TBD

API changes

TBD

Data model changes

TBD

Release notes snippet

TBD

Comments

smustgrave created an issue. See original summary.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.