NETWORK PROTOCOL REFERENCE

HTTP Status Codes

Comprehensive architectural and diagnostic index for standard HTTP response status codes, error remediation, and RESTful specifications.

100
RFC 9110

Continue

Initial part of a request has been received and client may continue.

Inspect Protocol
101
RFC 9110

Switching Protocols

Requester has asked the server to switch protocols.

Inspect Protocol
200
RFC 9110

OK

Standard response for successful HTTP requests.

Inspect Protocol
201
RFC 9110

Created

The request has been fulfilled, resulting in the creation of a new resource.

Inspect Protocol
202
RFC 9110

Accepted

The request has been accepted for processing, but processing has not finished.

Inspect Protocol
204
RFC 9110

No Content

The server successfully processed the request and is not returning any content.

Inspect Protocol
301
RFC 9110

Moved Permanently

The requested URI has been permanently assigned a new URI.

Inspect Protocol
302
RFC 9110

Found (Temporary Redirect)

The target resource resides temporarily under a different URI.

Inspect Protocol
304
RFC 9110

Not Modified

Indicates that the resource has not been modified since the last request.

Inspect Protocol
400
RFC 9110

Bad Request

Server cannot process request due to apparent client error (invalid syntax, malformed framing).

Inspect Protocol
401
RFC 9110

Unauthorized

Request lacks valid cryptographic authentication credentials.

Inspect Protocol
403
RFC 9110

Forbidden

Server understands request but refuses authorization.

Inspect Protocol
404
RFC 9110

Not Found

The server cannot find the requested resource or endpoint path.

Inspect Protocol
405
RFC 9110

Method Not Allowed

The request method is understood but not supported by target resource.

Inspect Protocol
408
RFC 9110

Request Timeout

The server timed out waiting for the client to complete its request.

Inspect Protocol
409
RFC 9110

Conflict

Request could not be processed due to a conflict with current resource state.

Inspect Protocol
422
RFC 9110

Unprocessable Content

Server understands content-type and syntax, but contained semantic errors.

Inspect Protocol
429
RFC 6585

Too Many Requests

The user has sent too many requests in a given amount of time (Rate Limited).

Inspect Protocol
500
RFC 9110

Internal Server Error

Generic error indicating the server encountered an unexpected condition.

Inspect Protocol
502
RFC 9110

Bad Gateway

Server, while acting as a gateway or proxy, received an invalid response from upstream.

Inspect Protocol
503
RFC 9110

Service Unavailable

The server is currently unable to handle the request due to temporary overloading or maintenance.

Inspect Protocol
504
RFC 9110

Gateway Timeout

Server acting as a gateway did not receive a timely response from the upstream server.

Inspect Protocol

HTTP Status Class Architecture

1xx Informational

Request received, continuing process.

2xx Successful

Action successfully received and accepted.

3xx Redirection

Further action required to complete request.

4xx Client Error

Request contains bad syntax or unauthorized access.

5xx Server Error

Server failed to fulfill an apparently valid request.