HTTP Status Code Codex

UtilityStable
100
Continue
RFC 9110, Section 15.2.1
101
Switching Protocols
RFC 9110, Section 15.2.2
200
OK
RFC 9110, Section 15.3.1
201
Created
RFC 9110, Section 15.3.2
204
No Content
RFC 9110, Section 15.3.5
301
Moved Permanently
RFC 9110, Section 15.4.2
304
Not Modified
RFC 9110, Section 15.4.5
400
Bad Request
RFC 9110, Section 15.5.1
401
Unauthorized
RFC 9110, Section 15.5.2
403
Forbidden
RFC 9110, Section 15.5.4
404
Not Found
RFC 9110, Section 15.5.5
418
I'm a teapot
RFC 2324 (HTCPCP/1.0)
429
Too Many Requests
RFC 6585, Section 4
500
Internal Server Error
RFC 9110, Section 15.6.1
502
Bad Gateway
RFC 9110, Section 15.6.3
503
Service Unavailable
RFC 9110, Section 15.6.4
504
Gateway Timeout
RFC 9110, Section 15.6.5
200

OK

RFC 9110, Section 15.3.1
Standard Definition

The request has succeeded. The payload sent depends on the request method (GET returns representation, POST returns action status).

Typical Causes & Scenarios
  • Normal successful HTTP query or operation completion.
Caching Behavior
Cacheable by default unless Cache-Control header states otherwise.
Associated Headers
Content-Type
Cache-Control: max-age=3600
ETag
Client Verification Code
// Test HTTP Status in Fetch
const res = await fetch("https://httpbin.org/status/200");
console.log(res.status, res.statusText); // 200 OK