AkousaHTTP Status CodesInfo
100100 Continue
The server has received the request headers and the client should proceed to send the request body.
browsernodeserver
View details Browse all 70 HTTP Status Codes error codes with causes, fixes, and examples.
100The server has received the request headers and the client should proceed to send the request body.
101The server is switching protocols as requested by the client via an Upgrade header.
102The server has received and is processing the request, but no response is available yet (WebDAV).
103The server sends preliminary response headers to allow the client to start preloading resources before the final response.
200The request has succeeded. The meaning of the success depends on the HTTP method used.
201The request has been fulfilled and a new resource has been created as a result.
202The request has been accepted for processing, but the processing has not been completed yet.
203The response has been modified by a transforming proxy and differs from what the origin server sent.
204The server successfully processed the request but is not returning any content in the response body.
205The server tells the client to reset the document view, such as clearing a form after submission.
206The server is delivering only part of the resource due to a Range header sent by the client.
207The response provides status for multiple independent operations in a single response (WebDAV).
208The members of a DAV binding have already been enumerated in a previous part of the response, and are not included again.
226The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
300The request has more than one possible response and the user or user agent should choose one of them.
301The requested resource has been permanently moved to a new URL, and future requests should use the new URL.
302The requested resource temporarily resides at a different URL. Future requests should continue to use the original URL.
303The response to the request can be found at a different URL using a GET method.
304The resource has not been modified since the last request, so the client can use its cached copy.
305The requested resource must be accessed through the proxy specified in the Location header. This status code is deprecated.
307The request should be repeated with the same method at the URL in the Location header. Unlike 302, the request method must not change.
308The resource has permanently moved to a new URL, and the request method must not change when following the redirect.
400The server cannot process the request due to a client error, such as malformed syntax, invalid parameters, or corrupt data.
401The request requires user authentication. The client must provide valid credentials to access the resource.
402The request requires payment. This status code is reserved for future use but is used by some APIs to indicate billing issues.
403The server understood the request but refuses to authorize it. Unlike 401, re-authenticating will not help.
404The server cannot find the requested resource. The URL may be incorrect or the resource may have been deleted.
405The HTTP method used is not supported for the requested resource.
406The server cannot produce a response matching the list of acceptable values defined in the request's Accept headers.
407The client must first authenticate with the proxy before the request can be forwarded to the target server.
408The server timed out waiting for the client to complete the request.
409The request conflicts with the current state of the server resource.
410The resource is no longer available and has been permanently removed. Unlike 404, this indicates intentional removal.
411The server requires a Content-Length header in the request but none was provided.
412One or more conditions specified in the request headers evaluated to false on the server.
413The request body exceeds the size limit configured on the server.
414The request URL is longer than the server is willing to interpret.
415The server refuses the request because the Content-Type of the request body is not supported.
416The client requested a range that is not available for the given resource.
417The server cannot meet the expectation specified in the Expect request header.
418The server refuses the request because it is, permanently, a teapot. An April Fools' joke from RFC 2324.
421The request was directed at a server that is not able to produce a response for the combination of scheme and authority in the request URI.
422The server understands the content type and syntax but cannot process the contained instructions due to semantic errors.
423The resource being accessed is locked and cannot be modified (WebDAV).
424The request failed because it depended on another request that failed (WebDAV).
425The server is unwilling to process a request that might be replayed, to avoid potential replay attacks.
426The server refuses to perform the request using the current protocol and requires the client to upgrade.
428The server requires the request to be conditional to prevent the 'lost update' problem.
429The user has sent too many requests in a given amount of time (rate limiting).
431The server refuses the request because one or more header fields are too large.
451The resource is unavailable due to legal demands, such as censorship or court orders.
500The server encountered an unexpected condition that prevented it from fulfilling the request.
501The server does not support the functionality required to fulfill the request.
502A gateway or proxy server received an invalid response from the upstream server.
503The server is temporarily unable to handle the request due to maintenance or overloading.
504A gateway or proxy server did not receive a timely response from the upstream server.
505The server does not support the HTTP protocol version used in the request.
506The server has an internal configuration error where the chosen variant resource is configured to engage in content negotiation itself.
507The server cannot store the representation needed to complete the request (WebDAV).
508The server detected an infinite loop while processing the request (WebDAV).
510The server requires further extensions to the request in order to fulfill it.
511The client needs to authenticate to gain network access, typically for captive portals.
520Cloudflare received an unexpected or empty response from the origin server.
521The origin web server has refused the connection from Cloudflare.
522Cloudflare could not negotiate a TCP handshake with the origin server.
523Cloudflare could not reach the origin server, typically due to DNS issues.
524Cloudflare established a TCP connection but the origin server did not respond with an HTTP response in time.
525Cloudflare could not complete an SSL/TLS handshake with the origin server.
526Cloudflare could not validate the SSL certificate on the origin server.
527A Cloudflare Railgun connection error occurred between the Cloudflare edge and the Railgun listener.