feat: serve lightweight HTML page on 503 errors - #60
Merged
Conversation
When the service is under memory pressure and returns 503s, browser clients now receive a minimal static HTML fallback page (no JS, no external resources) instead of a raw JSON error. API clients continue to receive JSON responses. Handles the health-check and Stripe 503 paths via the new global errorhandler. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
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.
Summary
templates/503.htmlfallback page (no JS, no external resources, ~800 bytes inline CSS)@app.errorhandler(503)inerror_handler.pythat serves the HTML page to browser clients and JSON to API clients, using theAcceptheader to distinguishTest plan
Accept: application/jsonrequest to a 503 endpoint still returns JSON{"error": "Service unavailable", ...}🤖 Generated with Claude Code