Separate maintenance mode (503) from infrastructure/application errors #1
+908
−0
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.