مرجع کدهای وضعیت HTTP
مرجع قابل جستجوی تمام کدهای وضعیت
Search for a command to run...
مرجع قابل جستجوی تمام کدهای وضعیت
52 نتیجه
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before the final HTTP message, allowing the client to start preloading resources.
The request has succeeded. The meaning of success depends on the HTTP method used.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but the processing has not been completed.
The server is a transforming proxy that received a 200 OK from the origin, but is returning a modified version.
The server successfully processed the request and is not returning any content.
The server successfully processed the request and asks the requester to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
Indicates multiple options for the resource from which the client may choose.
This and all future requests should be directed to the given URI.
Tells the client to look at (browse to) another URL. Has been superseded by 303 and 307.
The response to the request can be found under another URI using a GET method.
Indicates that the resource has not been modified since the version specified by request headers.
The request should be repeated with another URI; the method must not change.
The request and all future requests should be repeated using another URI; the method must not change.
The server cannot or will not process the request due to an apparent client error.
Authentication is required and has failed or has not yet been provided.
Reserved for future use. Some APIs use this for rate-limiting or quota exceeded errors.
The request was valid but the server is refusing action. The user might not have permissions.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource.
The requested resource is capable of generating only content not acceptable according to the Accept headers.
The client must first authenticate itself with the proxy.
The server timed out waiting for the request. The client may repeat the request without modifications.
Indicates that the request could not be processed because of conflict in the current state of the resource.
Indicates that the resource requested is no longer available and will not be available again.
The request did not specify the length of its content, which is required by the resource.
The server does not meet one of the preconditions that the requester put on the request header fields.
The request is larger than the server is willing or able to process.
The URI provided was too long for the server to process.
The request entity has a media type which the server or resource does not support.
The client has asked for a portion of the file but the server cannot supply that portion.
The server cannot meet the requirements of the Expect request-header field.
The server refuses the attempt to brew coffee with a teapot. (RFC 2324 April Fools joke, widely implemented.)
The request was well-formed but was unable to be followed due to semantic errors.
Indicates that the server is unwilling to risk processing a request that might be replayed.
The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.
The origin server requires the request to be conditional to prevent lost-update problems.
The user has sent too many requests in a given amount of time (rate limiting).
The server is unwilling to process the request because its header fields are too large.
A server operator has received a legal demand to deny access to a resource or set of resources.
A generic error message given when an unexpected condition was encountered on the server.
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server cannot handle the request (because it is overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
The server is unable to store the representation needed to complete the request.
The client needs to authenticate to gain network access.