HTTP Durum Kodları

The server has received the request headers. The client should proceed to send the request body.

The server is switching protocols as requested by the client (e.g., upgrading to WebSocket).

The server has received and is processing the request, but no response is available yet.

Used to return some response headers before final HTTP message. Allows preloading resources.

The request has succeeded. The meaning depends on the HTTP method used.

The request has been fulfilled and a new resource has been created.

The request has been accepted for processing, but processing is not yet complete.

The returned metadata is from a local or third-party copy, not the origin server.

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

The server is delivering only part of the resource due to a range header sent by the client.

Conveys information about multiple resources in situations where multiple status codes might be appropriate.

The resource has been permanently moved to a new URL. Future requests should use the new URL.

The resource resides temporarily under a different URL. The client should continue to use the original URL.

The response to the request can be found at another URL using a GET method.

The resource has not been modified since the last request. The client can use its cached version.

The request should be repeated with another URL, but future requests should still use the original URL. Method must not change.

The resource has been permanently moved. Similar to 301 but the method must not change.

The server cannot process the request due to something perceived to be a client error (malformed syntax, invalid parameters).

Authentication is required. The client must authenticate itself to get the requested response.

Reserved for future use. Some APIs use this for rate limiting or payment-gated features.

The client does not have permission to access this resource, even with authentication.

The requested resource could not be found on the server. The URL may be incorrect or the resource deleted.

The HTTP method used is not supported for this resource (e.g., POST on a read-only endpoint).

The server cannot produce a response matching the Accept headers sent by the client.

The server timed out waiting for the request. The client may repeat the request.

The request conflicts with the current state of the server (e.g., duplicate resource, edit conflict).

The resource is no longer available and will not be available again. Unlike 404, this is permanent.

The request entity is larger than the server is willing or able to process.

The URI provided was too long for the server to process.

The media type of the request data is not supported by the server.

The request was well-formed but semantically incorrect. Common in API validation errors.

The user has sent too many requests in a given time period (rate limiting).

The resource is unavailable due to legal demands (censorship, court order).

A generic error message when the server encounters an unexpected condition.

The server does not support the functionality required to fulfill the request.

The server, acting as a gateway, received an invalid response from an upstream server.

The server is temporarily unable to handle the request (overloaded or under maintenance).

The server, acting as a gateway, did not receive a timely response from an upstream server.

The server is unable to store the representation needed to complete the request.

The server detected an infinite loop while processing the request.