This is the HTTP Response Status Codes Table Cheat Sheet. Included in this post are the known Hypertext Transfer Protocol (HTTP) response status codes. It also include the status codes from the IETF internet standards as well as other RFCs, specifications and other commonly used codes.
- HTTP Status Codes for Rails Enjoy this cheat sheet at its fullest within Dash, the macOS documentation browser. HTTP status codes and their respective Rails symbol representations. For example,:notfound can be used instead of 404 in a render call: render file: '404.html.erb', status::notfound. 1xx Informational.
- Want the info on this page in a pretty little cheat sheet? Get your copy here. One of the most important parts of a successful website is how that site responds to requests. Everything may look good in your browser, but unless you know what response code those pages are sending back, it.
- Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection. 498 Token expired/invalid (Esri) Returned by ArcGIS for Server. A code of 498 indicates an expired or otherwise invalid token.
These status codes forms part of the HTTP/1.1 standard (RFC 7231 ).IANA is the sole organization which maintains the official records of all the HTTP status codes. Microsoft IIS also provides their own decimal subcodes for further labelling of information.
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. Types of HTTP status code responses.
1xx Informational
Request received, continuing process. The following class of status codes indicate that there is a response which consists of the Status-Line and optional headers that terminates via an empty line. Because HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under testing conditions.
Continue
Switching Protocols
Processing
The following class of status codes indicates the action requested by the client was completely received, understood, accepted and processed successfully.
OK
Created
Accepted
Non-Authoritative Information (since HTTP/1.1)
No Content
Reset Content
Partial Content
Multi-Status
Already Reported
IM Used
The following class of status code indicates the client is required to make additional action in order to complete the request. These status codes are usually utilized for URL redirection. User agents may carry out the additional action with no user interaction provided the method used in the second request is GET or HEAD. A UA should not automatically redirect a request more than five (5) times. It is deemed that such redirections may indicate an infinite loop.
Multiple Choices
Moved Permanently
Found
See Other
Not Modified
Use Proxy
Switch Proxy
Temporary Redirect
Permanent Redirect
These are your usual error status codes, better known for the 4xx number combination. Except when responding to a HEAD request, the server is required to include an entity containing details of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. UAs should display any included entity to the user.
Bad Request
Unauthorized
Payment Required
Forbidden
Not Found
Method Not Allowed
Not Acceptable
Proxy Authentication Required
Request Timeout
Conflict
Gone
Length Required
Precondition Failed
Payload Too Large
URI Too Long
Unsupported Media Type
Range Not Satisfiable
Expectation Failed
I’m a teapot
Authentication Timeout
Misdirected Request
Unprocessable Entity
Locked
Failed Dependency
Upgrade Required
Precondition Required
Too Many Requests
Request Header Fields Too Large
Unavailable For Legal Reasons
These status codes informs you that the server failed to complete an apparently valid request. Response status codes starting with number “5” indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server must include an entity detailing the error situation, and indicate whether it is a temporary or permanent condition. Likewise, UAs are required to display any included entity to the user. These response codes are applicable to any request method.
Internal Server Error
Not Implemented
Bad Gateway
Service Unavailable
Gateway Timeout
HTTP Version Not Supported
Variant Also Negotiates
Insufficient Storage
Loop Detected
Not Extended
Network Authentication Required
Non-standard, these status codes are not specified by any RFC, but are used by third-party services to provide semantic or RESTful error responses
checkpoint
Method Failure (Spring Framework)
Enhance Your Calm (Twitter)
Blocked by Windows Parental Controls (Microsoft)
Invalid Token (Esri)
Token Required (Esri)
Bandwidth Limit Exceeded (Apache Web Server/cPanel)
The IIS expands the 4xx error space to signal errors with the client’s request.
Login Timeout
Retry With
Redirect
The Nginx web server software expands the 4xx error space to signal issues with the client’s request.
No Response
SSL Certificate Error
SSL Certificate Required
HTTP Request Sent to HTTPS Port
Client Closed Request
CloudFlare’s (CDN Service) reverse proxy service expands the 5xx error space to signal issues with the origin server.
Unknown Error
Web Server Is Down
Connection Timed Out
Origin Is Unreachable
A Timeout Occurred
Http Response Codes Cheat Sheet Printable
SSL Handshake Failed
Invalid SSL Certificate
Http Response Codes Cheat Sheet Template
posted February 25, 2016 by THE11thROCK for TeraBlitz.com
FAIR USE DISCLAIMER: The following data is for educational, scholarship review and archiving purposes only. By viewing this information, you release the website and its authors from any responsibility or liabilities. Though we verify and maintain the accuracy of the provided data, the absence of unintented typographical and factual errors cannot be guaranteed. Use the page at your own risk. For any suggestions, updates, credits or correction requests, Contact Us: terablitz.rock@gmail.com
TeraBlitz Steam Header Custom Grid Gloss Pack Download