HTTP Status Codes مرجع

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

The requester has asked the server to switch protocols.

Standard response for successful HTTP requests.

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

The request has been accepted for processing but not completed.

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

This and all future requests should be directed to the given URI.

Temporary redirect — the client should follow this redirect.

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

Like 302 but the method must be preserved on the redirect.

Like 301 but the method must be preserved on the redirect.

The server cannot process the request due to a client error.

Authentication is required and has failed or not been provided.

The request was valid, but the server is refusing action.

The requested resource could not be found.

The request method is known but is not supported by the target resource.

The server timed out waiting for the request.

Indicates request conflict with current state of the target resource.

Indicates the resource is no longer available and will not be available again.

Yes, this is real — RFC 2324. The server refuses to brew coffee with a teapot.

The server understands the content type but cannot process the request.

The user has sent too many requests in a given time.

A generic error message — something has gone wrong on the server.

The server does not support the functionality required.

The server received an invalid response from an upstream server.

The server is unable to handle the request right now.

An upstream server failed to respond in time.

The HTTP version used in the request is not supported.