[9.x] Add support for 4xx/5xx fallback error views #38877
Merged
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.
We can render a custom HTTP error page by creating view file for a specific status code (eg:
errors/404.blade.php
). This PR adds support for a fallback if the exact status code does not have a view:errors/4xx.blade.php
One of my projects has views defined for most status codes. Each view shows a helpful friendly message in Dutch. Yesterday my customer ran into a 405 error that did not have a view. This scary English error was displayed:

With this PR, I can create
errors/4xx.blade.php
anderrors/5xx.blade.php
views to ensure that I always render a helpful custom error page.