Http Error Numbers
Contents |
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e This is a list of http status codes cheat sheet Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETF internet
Http Code 302
standards, other IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies http response example one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human-readable alternative can be provided. Unless
Http Code 403
otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information,[3] but not all of those are here (note that these sub-codes only appear in the response payload and in documentation; not in the place of an http 422 actual HTTP status code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 5xx Server Error 6 Unofficial codes 6.1 Internet Information Services 6.2 nginx 6.3 Cloudflare 7 See also 8 Notes 9 References 10 External links 1xx Informational[edit] Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. The response 417 Expec
response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
Http Error Wordpress
terminated by an empty line. There are no required headers for this
Http 404
class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send http 502 a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, https://en.wikipedia.org/wiki/List_of_HTTP_status_codes even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) 10.1.1 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. 10.1.2 101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. The protocol SHOULD be switched on
code via httpstatuses.com/code or browse the list below. @ https://httpstatuses.com/ Share on Twitter★ Star on GitHub⊕ Add to Pinboard 1×× Informational 100 Continue 101 Switching Protocols 102 Processing 2×× Success 200 OK https://documentation.cpanel.net/display/CKB/HTTP+Error+Codes+and+Quick+Fixes 201 Created 202 Accepted 203 Non-authoritative Information 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status 208 Already Reported 226 http error IM Used 3×× Redirection 300 Multiple Choices 301 Moved Permanently 302 Found 303 See Other 304 Not Modified 305 Use Proxy 307 Temporary Redirect 308 Permanent Redirect 4×× Client Error 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method http error numbers Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Payload Too Large 414 Request-URI Too Long 415 Unsupported Media Type 416 Requested Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 421 Misdirected Request 422 Unprocessable Entity 423 Locked 424 Failed Dependency 426 Upgrade Required 428 Precondition Required 429 Too Many Requests 431 Request Header Fields Too Large 444 Connection Closed Without Response 451 Unavailable For Legal Reasons 499 Client Closed Request 5×× Server Error 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 508 Loop Detected 510 Not Extended 511 Network Authentication Required 599 Network Connect Timeout Error
Knowledge BasePagesBlogPage tree Browse pagesConfigureSpace tools Attachments (0) Page History Page Information Resolved comments Link to this Page… View in Hierarchy View Source Export to PDF Export to Word Pages cPanel Knowledge Base WebServices Skip to end of banner JIRA links Go to start of banner HTTP Error Codes and Quick Fixes Skip to end of metadata Created by Doc User, last modified on Aug 19, 2016 Go to start of metadata OverviewHTTP codes describe the status of a URL when a visitor attempts to access it. HTTP codes include error messages that describe the problems that visitors encounter. The codes are three-digit numbers.The following table represents the five classes of HTTP codes, divided into categories, by the first digit:First DigitDescription1, 2, or 3A fully functional request.4A client-side error. The most common codes span 400 to 404.5A server-side error. The most common codes span 500 to 510.Note: For more information, read Wikipedia's List of HTTP status codes article.ErrorsErrorDescription4xx ErrorsThese errors result due to a problem with the client's request (for example, the browser), but often point to a problem on a website. For example, if a faulty link exists on your home page, and visitors click it, they receive a 404 error.We strongly suggest that you monitor these errors and investigate their causes. Because visitors most often see this error, we suggest that you customize these error pages in cPanel's Error Pages interface (Home >> Advanced >> Error Pages).400 Bad RequestThe user's request contains an incorrect syntax.401 UnauthorizedThe requested file requires authentication (a username and password).403 ForbiddenThe server will not allow the visitor to access the requested file. If a visitor receives this code in error, check the file's permission settings. You can also confirm whether the system protects the file in cPanel's Indexes interface (Home >> Advanced >> Indexes).404 Not FoundThe server did not find a visitor's requested file. This error commonly occurs when a visitor mistypes a URL.5xx ErrorsThese errors occur when a server cannot fulfill an apparently-valid request from a visitor. To resolve these issues, contact your system administrator.It is also important to consider that many times, a chain of servers handles an HTTP request. This means that the returned error may come from a different web server and not your own.500 Internal Serve ErrorThe server encountered an unexpected condition. This multipurpose error displays when the server cannot gather any specific information about the problem. This erro