Http Status Codes Cheat Sheet

Posted on |



When you attempt to access a URL, you will receive an HTTP (Hypertext Transfer Protocol) status code in response. The status code is issued by the server to the client that made the request. Below is a quick cheat sheet of all the HTTP status codes with links to more information about the status code.

Http Status Codes Cheat Sheet Pdf

The 1xx HTTP status codes are the informational requests that indicate that the server received and understood the request, but it needs a little longer to process the information. They include the '100 Continue', '101 Switching Protocol', and '102 Processing HTTP status codes.' The 2xx HTTP status codes are the successful requests. Army logistics, g-4 product hip-pocket guide gcss–army cheat sheet 1c - fill as requested, sub or reject if item not available 1j - fill as requested or reject if item not available 2a - item is not available through manufacturer, fabricator or procurement 2b - only requested item will suffice, do not substitute. HTTP Status Code directory, with definitions, details and helpful code references. Sponsored by Runscope — API Monitoring & Testing. HTTP Status Codes. Httpstatuses.com is an easy to reference database of HTTP Status Codes with their definitions and helpful code references all in one place. Discover the comprehensive cheat sheet of HTTP status codes for SEO with explaining of each of them: 1xx informational responses, 2xx success, 3xx redirection, 4xx client errors, 5xx server errors. Use HTTP Status Code Checker to verify a specific URL. A generic error message, given when no more specific message is suitable. Dig deeper into this article to explore a beginner’s guide to HTTP status code cheat sheet. Top 5 HTTP Status Codes Every Website Owner Should Know About. When a user explores a website or page, they either land on the requested file or faces an HTTP page. The HTTP page depicts some code and makes the user aware that their request was not.

Types of HTTP status code responses

The first digit identifies the class of the the type of status code response. If there is no HTTP status code response, then there will not be a status code.

1XX Informational Responses

Codes

The 1xx (Informational) class of status code indicates an interim response for communicating connection status or request progress prior to completing the requested action and sending a final response. 1xx responses are terminated by the first empty line after the status-line (the empty line signaling the end of the header section). Since HTTP/1.0 did not define any 1xx status codes, a server MUST NOT send a 1xx response to an HTTP/1.0 client[1].

Http Status Codes Cheat Sheet

A client MUST be able to parse one or more 1xx responses received prior to a final response, even if the client does not expect one. A user agent MAY ignore unexpected 1xx responses[2].

A proxy MUST forward 1xx responses unless the proxy itself requested the generation of the 1xx response. For example, if a proxy adds an “Expect: 100-continue” field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s)[3].

2XX Successful Responses

The 2xx Successful class of status code indicates that the client’s request was successfully received, understood, and accepted[4].

3XX Redirects

4XX Client Errors

Http Status Codes Cheat Sheet 2019

5XX Server Errors

  • 500 Internal Server Error
  • 501 Not Implemented
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout
  • 505 HTTP Version Not Supported
  • 506 Variant Also Negotiates
  • 507 Insufficient Storage (WebDAV)
  • 508 Loop Detected (WebDAV)
  • 510 Not Extended
  • 511 Network Authentication Required

References

We like to give credit where credit is due. This article contains 2 references with a total of 4 citations.

Alexa Error Code Cli 101

Sheet

  1. [1][2][3] Fielding, Roy T, And Julian F Reschke. '6.2. Informational 1xx.' HTTP/1.1 Semantics and Content, IETF Trust, 1 Jun. 2014, tools.ietf.org/html/rfc7231#section-6.2

  2. [4] Fielding, Roy T, And Julian F Reschke. '6.3. Successful 2xx.' HTTP/1.1 Semantics and Content, IETF Trust, 1 Jun. 2014, tools.ietf.org/html/rfc7231#section-6.3

E m cheat sheet

HTTP status codes and their respective Rails symbol representations. For example, :not_found can be used instead of 404 in a render call:

1xx Informational

:continue

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

:switching_protocols

The requester has asked the server to switch protocols and the server is acknowledging that it will do so.

:processing

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

2xx Success

:ok

The standard response for successful HTTP requests.

:created

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

:accepted

The request has been accepted but has not been processed yet. This code does not guarantee that the request will process successfully.

:non_authoritative_information

HTTP 1.1. The server successfully processed the request but is returning information from another source.

:no_content

The server accepted the request but is not returning any content. This is often used as a response to a DELETE request.

:reset_content

Similar to a 204 No Content response but this response requires the requester to reset the document view.

:partial_content

The server is delivering only a portion of the content, as requested by the client via a range header.

:multi_status

The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

WebDAV - RFC 4918

:already_reported

The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.

WebDAV - RFC 5842

:im_used

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

3xx Redirection

:multiple_choices

There are multiple options that the client may follow.

:moved_permanently

The resource has been moved and all further requests should reference its new URI.

:found

The HTTP 1.0 specification described this status as 'Moved Temporarily', but popular browsers respond to this status similar to behavior intended for 303. The resource can be retrieved by referencing the returned URI.

:see_other

The resource can be retrieved by following other URI using the GET method. When received in response to a POST, PUT, or DELETE, it can usually be assumed that the server processed the request successfully and is sending the client to an informational endpoint.

Destroy all monsters unblockeddefinitely not a game site. :not_modified

The resource has not been modified since the version specified in If-Modified-Since or If-Match headers. The resource will not be returned in response body.

:use_proxy

HTTP 1.1. The resource is only available through a proxy and the address is provided in the response.

:reserved

Deprecated in HTTP 1.1. Used to mean that subsequent requests should be sent using the specified proxy.

:temporary_redirect

HTTP 1.1. The request should be repeated with the URI provided in the response, but future requests should still call the original URI.

:permanent_redirect

Experimental. The request and all future requests should be repeated with the URI provided in the response. The HTTP method is not allowed to be changed in the subsequent request.

4xx Client Error

:bad_request

The request could not be fulfilled due to the incorrect syntax of the request.

:unauthorized

The requestor is not authorized to access the resource. This is similar to 402 but is used in cases where authentication is expected but has failed or has not been provided.

:payment_required

Reserved for future use. Some web services use this as an indication that the client has sent an excessive number of requests.

:forbidden

The request was formatted correctly but the server is refusing to supply the requested resource. Unlike 402, authenticating will not make a difference in the server's response.

:not_found

The resource could not be found. This is often used as a catch-all for all invalid URIs requested of the server.

:method_not_allowed

The resource was requested using a method that is not allowed. For example, requesting a resource via a POST method when the resource only supports the GET method.

:not_acceptable

The resource is valid, but cannot be provided in a format specified in the Accept headers in the request.

:proxy_authentication_required

Authentication is required with the proxy before requests can be fulfilled.

:request_timeout

The server timed out waiting for a request from the client. The client is allowed to repeat the request.

:conflict

The request cannot be completed due to a conflict in the request parameters.

:gone

The resource is no longer available at the requested URI and no redirection will be given.

:length_required

The request did not specify the length of its content as required by the resource.

:precondition_failed

The server does not meet one of the preconditions specified by the client.

:request_entity_too_large

The request is larger than what the server is able to process.

:request_uri_too_long

The URI provided in the request is too long for the server to process. This is often used when too much data has been encoded into the URI of a GET request and a POST request should be used instead.

:unsupported_media_type

The client provided data with a media type that the server does not support.

:requested_range_not_satisfiable

The client has asked for a portion of the resource but the server cannot supply that portion.

:expectation_failed

The server cannot meet the requirements of the Expect request-header field.

:unprocessable_entity

The request was formatted correctly but cannot be processed in its current form. Often used when the specified parameters fail validation errors.

WebDAV - RFC 4918

:locked

The requested resource was found but has been locked and will not be returned.

WebDAV - RFC 4918

:failed_dependency

The request failed due to a failure of a previous request.

WebDAV - RFC 4918

:upgrade_required

The client should repeat the request using an upgraded protocol such as TLS 1.0.

5xx Server Error

:internal_server_error

A generic status for an error in the server itself.

:not_implemented

The server cannot respond to the request. This usually implies that the server could possibly support the request in the future — otherwise a 4xx status may be more appropriate.

:bad_gateway

The server is acting as a proxy and did not receive an acceptable response from the upstream server.

:service_unavailable

The server is down and is not accepting requests.

:gateway_timeout

The server is acting as a proxy and did not receive a response from the upstream server.

:http_version_not_supported

The server does not support the HTTP protocol version specified in the request.

:variant_also_negotiates

Transparent content negotiation for the request results in a circular reference.

:insufficient_storage

The user or server does not have sufficient storage quota to fulfill the request.

WebDAV - RFC 4918

:loop_detected

The server detected an infinite loop in the request.

WebDAV - RFC 5842

:not_extended

Further extensions to the request are necessary for it to be fulfilled.

:network_authentication_required

The client must authenticate with the network before sending requests.

Notes

  • Based on cheat.errtheblog.com and List of HTTP status codes on Wikipedia.