HTTP Durum KodlarıGeliştirme

Tüm HTTP durum kodları için hızlı başvuru

1xx

Informational

4 kod
KodAdAçıklama
ContinueThe server has received the request headers and the client should proceed to send the request body.
Switching ProtocolsThe requester has asked the server to switch protocols and the server has agreed to do so.
ProcessingThe server has received and is processing the request, but no response is available yet.
Early HintsUsed to return some response headers before the final HTTP message.
2xx

Success

10 kod
KodAdAçıklama
OKThe request has succeeded. The meaning of success depends on the HTTP method.
CreatedThe request has been fulfilled and a new resource has been created.
AcceptedThe request has been accepted for processing, but processing has not been completed.
Non-Authoritative InformationThe server successfully processed the request but is returning information from another source.
No ContentThe server successfully processed the request and is not returning any content.
Reset ContentThe server successfully processed the request and asks the requester to reset its document view.
Partial ContentThe server is delivering only part of the resource due to a range header sent by the client.
Multi-StatusThe response body contains multiple separate response codes for batch operations.
Already ReportedThe members of a DAV binding have already been enumerated in a preceding part of the response.
IM UsedThe server has fulfilled a request and the response is the result of instance manipulations on the current instance.
3xx

Redirection

7 kod
KodAdAçıklama
Multiple ChoicesIndicates multiple options for the resource from which the client may choose.
Moved PermanentlyThis and all future requests should be directed to the given URI.
FoundThe resource is temporarily located at a different URI.
See OtherThe response to the request can be found under another URI using the GET method.
Not ModifiedThe resource has not been modified since the version specified by the request headers.
Temporary RedirectThe request should be repeated at another URI, but future requests should still use the original URI.
Permanent RedirectThe request and all future requests should be repeated using another URI, preserving the HTTP method.
4xx

Client Error

40 kod
KodAdAçıklama
Bad RequestThe server cannot process the request due to a client error, such as malformed syntax.
UnauthorizedAuthentication is required and has failed or has not been provided.
Payment RequiredReserved for future use, originally intended for digital payment systems.
ForbiddenThe server understood the request but refuses to authorize it.
Not FoundThe requested resource could not be found but may be available in the future.
Method Not AllowedThe request method is not supported for the requested resource.
Not AcceptableThe server cannot produce a response matching the acceptable values in the request headers.
Proxy Authentication RequiredThe client must first authenticate itself with the proxy.
Request TimeoutThe server timed out waiting for the request.
ConflictThe request could not be processed because of a conflict with the current state of the resource.
GoneThe resource requested was previously in use but is no longer available and will not be available again.
Length RequiredThe server refuses to accept the request without a defined Content-Length header.
Precondition FailedThe server does not meet one of the preconditions specified in the request headers.
Content Too LargeThe request body is larger than the server is willing or able to process.
URI Too LongThe URI provided was too long for the server to process.
Unsupported Media TypeThe request entity has a media type which the server or resource does not support.
Range Not SatisfiableThe client has asked for a portion of the file, but the server cannot supply that portion.
Expectation FailedThe server cannot meet the requirements of the Expect request-header field.
I'm a TeapotDefined in RFC 2324 as an April Fools' joke; a teapot refuses to brew coffee.
Enhance Your CalmTwitter/XRate limiting response. Non-standard; superseded by 429 Too Many Requests.
Misdirected RequestThe request was directed at a server that is not able to produce a response.
Unprocessable ContentThe request was well-formed but could not be followed due to semantic errors.
LockedThe resource that is being accessed is locked.
Failed DependencyThe request failed because it depended on another request that failed.
Too EarlyThe server is unwilling to risk processing a request that might be replayed.
Upgrade RequiredThe client should switch to a different protocol, such as TLS/1.3.
Precondition RequiredThe origin server requires the request to be conditional to prevent conflicts.
Too Many RequestsThe user has sent too many requests in a given amount of time (rate limiting).
Request Header Fields Too LargeThe server is unwilling to process the request because the header fields are too large.
Login TimeoutIISThe client's session has expired and must log in again.
No ResponsenginxCloses the connection without sending any response, typically used to deny malicious requests.
Retry WithIISThe server requires the client to resend the request with more information.
Unavailable For Legal ReasonsThe server is denying access to the resource as a consequence of a legal demand.
Client Closed ConnectionAWSThe client closed the connection before the load balancer could send the request to the target.
Too Many IP AddressesAWSThe X-Forwarded-For header contains more than 30 IP addresses.
Request Header Too LargenginxThe request headers exceed the server's configured limit.
SSL Certificate ErrornginxAn error occurred while verifying the client SSL certificate.
SSL Certificate RequirednginxThe client did not provide a required SSL certificate.
HTTP Request Sent to HTTPS PortnginxA plain HTTP request was sent to an HTTPS port.
Client Closed RequestnginxThe client closed the connection before the server could send a response.
5xx

Server Error

21 kod
KodAdAçıklama
Internal Server ErrorA generic error message when the server encounters an unexpected condition.
Not ImplementedThe server does not recognize the request method or lacks the ability to fulfill it.
Bad GatewayThe server, acting as a gateway or proxy, received an invalid response from the upstream server.
Service UnavailableThe server is temporarily unable to handle the request, due to overload or scheduled maintenance.
Gateway TimeoutThe server, acting as a gateway or proxy, did not receive a timely response from the upstream server.
HTTP Version Not SupportedThe server does not support the HTTP version used in the request.
Variant Also NegotiatesTransparent content negotiation for the request results in a circular reference.
Insufficient StorageThe server is unable to store the representation needed to complete the request.
Loop DetectedThe server detected an infinite loop while processing the request.
Not ExtendedFurther extensions to the request are required for the server to fulfill it.
Network Authentication RequiredThe client needs to authenticate to gain network access (e.g., captive portal).
Web Server Returns an Unknown ErrorCloudflareThe origin server returned an empty, unknown, or unexpected response.
Web Server Is DownCloudflareThe origin server refused the connection.
Connection Timed OutCloudflareThe TCP handshake with the origin server timed out.
Origin Is UnreachableCloudflareCannot reach the origin server, possibly due to DNS resolution failure.
A Timeout OccurredCloudflareA TCP connection was established but the origin server did not reply in time.
SSL Handshake FailedCloudflareThe SSL handshake with the origin server failed.
Invalid SSL CertificateCloudflareCould not validate the SSL certificate on the origin server.
Railgun ErrorCloudflareThe Railgun connection to the origin server was interrupted (deprecated feature).
Origin DNS ErrorCloudflareCannot resolve the origin server's DNS, usually accompanied by a 1xxx error.
UnauthorizedAWSThe identity provider returned an error code during authentication.