Separate maintenance mode (503) from infrastructure/application errors#1
Draft
Separate maintenance mode (503) from infrastructure/application errors#1
Conversation
- Separate maintenance mode (503) from other errors - Add distinct error pages for 502, 504, 500, 429 - Include maintenance flag file approach - Add comprehensive documentation Co-authored-by: JacobZwang <59858341+JacobZwang@users.noreply.github.com>
- Add nginx-standalone.conf for complete testing setup - Create automated test script (test-config.sh) - Update README with test instructions - Clarify nginx.conf is a server block snippet - All tests passing successfully Co-authored-by: JacobZwang <59858341+JacobZwang@users.noreply.github.com>
- Remove unused /503.html location blocks from both configs - Maintenance mode uses @maintenance named location instead - Addresses code review feedback - All tests still passing Co-authored-by: JacobZwang <59858341+JacobZwang@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix maintenance page logic for error handling
Separate maintenance mode (503) from infrastructure/application errors
Jan 22, 2026
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.
HTTP 503 was overloaded - used for both scheduled maintenance and backend failures/timeouts, causing users to see the maintenance page inappropriately.
Changes
NGINX configuration examples (
examples/nginx/)/var/www/maintenance.flag)proxy_*_timeoutsettings)@maintenancefor 503 handlingError pages (
examples/nginx/error-pages/)Configuration variants
nginx.conf: Server block snippet for inclusionnginx-standalone.conf: Complete config for testing/validationtest-config.sh: Automated syntax and structure validationExample
Maintenance control:
Original prompt
Created from VS Code.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.