Read HTTP and DNS errors separately
03HTTP status describes the HTTP exchange; DNS RCODE describes the embedded DNS result.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 4.2.1 ↗
RFC 8484 · § 4.2.1EXAMPLE
3 / 3
03
Keep an HTTP transport failure separate from that valid DNS negative answer.
Keep an HTTP transport failure separate from that valid DNS negative answer.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
A valid DNS error response can be carried in a successful HTTP 2xx response.
- A valid DNS error response can be carried in a successful HTTP 2xx response.
- An HTTP failure is not itself a DNS NXDOMAIN result.
The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy