Add Limits section: why this cannot be a PSR-15 middleware - #5
Merged
Merged
Conversation
A PHP fatal is not a Throwable: no try/catch, PSR-15 pipeline included, ever intercepts it. The call stack — the pipeline itself — is destroyed before the next middleware could run. A language constraint, not a design choice.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A PHP fatal is not a
Throwable: notry/catch, PSR-15 pipeline included, ever intercepts it. PHP terminates execution immediately, and the call stack — the pipeline itself — is gone with it, before the next middleware could run. That's a constraint of the language, not a design choice.Documents this explicitly, plus why no PSR-7 either (the shutdown handler fires after the framework's own response-emission machinery may no longer be usable) and where PSR-3 does apply (the optional logger).