feat: add custom error page for 500 errors #58495
Merged
+4
−1
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 new sad bee page was created specifically for 500s to instruct the user to sign out, clear cookies, and run other troubleshooting steps that most commonly resolve 500 errors. However, this page does not apply to other error codes (503, 504, 404, etc.) as we don't necessarily want users to be signing out when the server is timing out or having other issues.
Testing story
Created adhoc with
adhoc:cdn:start
Updated
config/adhoc.yml.erb
and setcustom_error_response
totrue
. Observed updated distribution error page configurationDeployment strategy
Follow-up work
Privacy
Security
Caching
PR Checklist: