Look up common HTTP status codes, what they mean, and what to do next.
200 OK
The request succeeded.
Read the response body.
201 Created
The server created a resource.
Follow the Location header when one is present.
204 No Content
The request succeeded and there is no body.
Do not expect a response body.
301 Moved Permanently
The resource has a new permanent URL.
Update stored links to the new URL.
302 Found
The resource is temporarily at another URL.
Follow the redirect for this request only.
400 Bad Request
The server could not understand the request.
Check the syntax and required fields.
401 Unauthorized
Authentication is missing or rejected.
Send valid credentials. Do not confuse this with permissions.
403 Forbidden
The server understood the request and refused it.
Check permissions for this identity.
404 Not Found
No resource matches this URL.
Check the path and whether the resource was deleted.
409 Conflict
The request conflicts with the current state.
Reload the resource and retry the change.
429 Too Many Requests
The client sent requests too quickly.
Wait and retry. Honor Retry-After when it is present.
500 Internal Server Error
The server failed while handling the request.
Retry later. Inspect server logs if you operate the service.
502 Bad Gateway
A proxy received an invalid response upstream.
Retry, then check the upstream service.
503 Service Unavailable
The server is temporarily unable to handle the request.
Retry later. Check maintenance windows.
504 Gateway Timeout
A proxy timed out waiting for upstream.
Retry. If it persists, increase the upstream timeout or fix the slow service.
Your data stays in this browser and is not uploaded.
Search by number or name.
Filter by class, such as 4xx.
Read the meaning and the usual next action.
No. It covers the codes developers meet most often, not the full IANA registry.