HTTP contracts
Reference · HTTP contracts
Reference purpose — Document the wire behavior that clients and intermediaries actually observe.Predictable methods, status codes, headers, body rules, OPTIONS, HEAD, and malformed input responses.
Key concepts
OPTIONS
Capability discovery
HEAD
Metadata without body
400
Malformed request
Reference model
Contract summary
Interpretation
HTTP details are compatibility surface; a small inconsistency can break caches, SDKs, proxies, or browser behavior.Reference note HTTP correctness is part of the framework API, even when the application code is only a few lines.
Implementation notes
Decision lens
Related topics
- brackets-curly · Implement contracts — Read the focused guide for this boundary.
- route · Resolve paths — Read the focused guide for this boundary.
- shield-halved · Secure responses — Read the focused guide for this boundary.