Status codes & redirects
08Status codes report progress, success, redirection, client errors, or server errors.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 15 ↗
RFC 9110 · § 15EXAMPLE
4 / 4
04
Handle redirects with method rules.
When redirected, reconstruct the request and assess fields and credentials for the new target.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Interpret the status before acting on content.
- 1xx is informational, 2xx successful, 3xx redirection, 4xx client error, and 5xx server error.
- 201 indicates creation; 202 means accepted for processing, without promising completion; 204 has no content.
- 303 directs retrieval elsewhere. 307 and 308 preserve the method; 301 and 302 allow a historical POST-to-GET change.
A redirect creates a new request with its own authority and credential considerations. Do not indiscriminately forward sensitive fields to a different origin.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy