Error Page Codes
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 http status codes cheat sheet This is a list of Hypertext Transfer Protocol (HTTP) response status codes. http error wordpress It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. http code 403 The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are
Http Code 302
the standard wordings, but any human-readable alternative can be provided. Unless 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 http response example sub-codes only appear in the response payload and in documentation; not in the place of an 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 t
Guide cPanel WebHost Manager (WHM) Plesk SSL Certificates Specialized Help Offers & Bonuses Website Design Affiliates Helpful Resources Account Addons Billing System HostGator Blog HostGator Forums Video Tutorials Contact Us Interact and Engage Put two or more words in quotes to search for a http 422 phrase: "name servers" Prepend a plus sign to a word or phrase to require its
Error Code 500
presence in an article: +cpanel Prepend a minus sign to a word or phrase to require its absence in an article: -windows
Error Code List
Words of less than three characters are ignored. All searches are case-insensitive. Search [?] Support Portal Home » cPanel » Error Page Codes Error Page Codes Overview cPanel Plesk on Windows Plesk 10 VPS What are Error https://en.wikipedia.org/wiki/List_of_HTTP_status_codes Codes? All HTTP requests (the type of requests generated by your browser when you attempt to load a page) generate a status code. However, your browser will generally only display a status code associated with an error after an attempted action fails. There are 5 classes of status codes, and the term error codes specifically refers to the two classes of status codes that indicate these errors. This article will cover the following codes: http://support.hostgator.com/articles/cpanel/error-page-codes What is a Client Error Code? 400 : Bad Request 401 : Authorization Required 403 : Forbidden 404 : Not Found 405 : Method Not Allowed 406 : Not Acceptable (encoding) 407 : Proxy Authentication Required 408 : Request Timed Out 409 : Conflicting Request 410 : Gone 411 : Content Length Required 412 : Precondition Failed 413 : Request Entity Too Long 414 : Request URI Too Long 415 : Unsupported Media Type 421 : Too Many Connections What is a Server Error Code? 500 : Internal Server Error 501 : Not Implemented 502 : Bad Gateway 503 : Service Unavailable 504 : Gateway Timeout 505 : HTTP Version Not Supported Custom Error Pages What is a Client Error Code? Client Error Codes begin with the number 4, such as 404 or 403 (two of the most common client side errors). A Client Error Code indicates that there is an issue with the request, and that the request itself must be changed in order to get a different result. For example, if you get a 404 error code, it means the resource you requested does not exist. The request may be incorrect or the resource may have been removed, but the server is functioning correctly and the error is that the user is requesting something that is not th
consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define http://www.restapitutorial.com/httpstatuscodes.html any 1xx status codes, servers MUST NOT send 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, 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 http code and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) Wikipedia 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. error page codes Since 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 experimental conditions. 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. Wikipedia This means that the server has received the request headers, and that 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). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue