18 MOST COMMON HTTP
STATUS CODES
Satyender Sharma
200 - OK
Meaning: The request has succeeded.
Common Use Cases: Standard response
for successful HTTP requests.
201 - Created
Meaning: The request has been fulfilled, and a new
resource has been created.
Common Use Cases: Used in response to POST
requests, typically when a new resource is created.
202 - Accepted
Meaning: The request has been accepted for processing,
but the processing has not been completed.
Common Use Cases: Often used in asynchronous
processing scenarios.
18 MOST COMMON HTTP
STATUS CODES
Satyender Sharma
204 No Content
Meaning: The request was successful, but there is no
content to return.
Use Case: Deleting a resource where no content
needs to be returned.
301 - Moved Permanently
Meaning: The requested resource has been moved
to a new URL permanently.
Common Use Cases: Redirects for URLs that have
permanently changed.
302 - Found
Meaning: The requested resource is temporarily
located at a different URL.
Common Use Cases: Temporary redirects, where
the URL might change back to the original.
18 MOST COMMON HTTP
STATUS CODES
Satyender Sharma
304 - Not Modified
Meaning: Indicates that the resource has not been
modified since the last request.
Common Use Cases: Helps optimize performance by using
cached resources.
307 Temporary Redirect
Meaning: The request should be repeated with a different
URL, but the method remains unchanged.
Use Case: Temporarily moving resources during a site
update, ensuring the HTTP method is preserved.
400 - Bad Request
Meaning: The server could not understand the
request due to invalid syntax.
Common Use Cases: Invalid data submitted by the
client.
18 MOST COMMON HTTP
STATUS CODES
Satyender Sharma
401 - Unauthorized
Meaning: The request requires user authentication.
Common Use Cases: Accessing resources that
require login.
403 - Forbidden
Meaning: The server understood the request but refuses
to authorize it.
Common Use Cases: Accessing a resource that the user
does not have permission to view.
404 - Not Found
Meaning: The server can't find the requested
resource.
Common Use Cases: Incorrect URLs or when
resources are not available.
18 MOST COMMON HTTP
STATUS CODES
Satyender Sharma
405 - Method Not Allowed
Meaning: The HTTP method used is not supported by
the resource.
Common Use Cases: Sending a POST request to a
resource that only supports GET.
409 Conflict
Meaning: The request could not be processed due to a
conflict with the current state of the resource.
Use Case: Attempting to update a resource that has
already been modified by another request.
500 - Internal Server Error
Meaning: A generic error message when the server
encounters an unexpected condition.
Common Use Cases: Unhandled exceptions or
server misconfigurations.
18 MOST COMMON HTTP
STATUS CODES
Satyender Sharma
502 - Bad Gateway
Meaning: The server, while acting as a gateway or
proxy, received an invalid response from the
upstream server.
Common Use Cases: Issues with load balancers or
proxy servers.
503 Service Unavailable
Meaning: The server is currently unable to handle the
request, usually due to being overloaded or under
maintenance.
Use Case: Server downtime or maintenance periods.
504 - Gateway Timeout
Meaning: The server, while acting as a gateway or proxy, did
not receive a timely response from the upstream server.
Common Use Cases: Long-running processes in upstream
servers that exceed time limits.
