Repository navigation
feat(edge): implement RFC 7807 problem+json error handlers and diagnostic inspector - #11
Merged
ATLURI0001 merged 1 commit intoNov 20, 2026
Conversation
ATLURI0001
deleted the
feat/edge-rfc7807-error-responses-and-diagnostics
branch
November 20, 2026 11:53
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.
Architectural Specification & Diagnostic Framework
Edge reverse proxies must provide deterministic, machine-readable fault disclosures without leaking internal server topologies, stack traces, or upstream daemon details. Default Nginx error responses produce raw HTML pages that break programmatic JSON clients and hinder automated client-side retry decisions.
This PR introduces RFC 7807
application/problem+jsonerror representations for HTTP 429 (rate limiting) and 502/503/504 (upstream failures), alongside an automated edge architecture diagnostic inspection engine inscripts/diagnostics.py.Diagnostic Component Specification & Telemetry Schema
{ "type": "https://httpstatuses.com/429", "title": "Too Many Requests", "status": 429, "detail": "Rate limit exceeded", "requestId": "$request_id" }{ "type": "https://httpstatuses.com/502", "title": "Bad Gateway", "status": 502, "detail": "Upstream service temporarily unavailable", "requestId": "$request_id" }RK-TLS-001: Validates exclusion of legacy TLS protocols (SSLv3, TLSv1.0, TLSv1.1), shared session cache (shared:SSL:10m), and ticket disabling.RK-SEC-002: Checks required security headers (X-Content-Type-Options,X-Frame-Options,Referrer-Policy,Content-Security-Policy,X-Request-ID).RK-BUF-003: Confirms proxy buffering invariants and temp file storage prevention (proxy_max_temp_file_size 0;).RK-ERR-004: Validates interception of upstream errors and mapping to compliant problem+json handlers.Verification Results
Executed via pytest runner:
CLI diagnostics check (
python scripts/diagnostics.py):{ "totalRules": 4, "passed": 4, "failed": 0, "healthy": true }