Html Error Code List
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
Http 100 Error Code
t e This is a list of Hypertext Transfer Protocol (HTTP) response http status code method not supported status codes. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional 500 response commonly used codes. 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
Httpstatus 500
phrases used are 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
Http Status Codes Cheat Sheet
here (note that these 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 header
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 terminated by an empty line. There are no required headers for this http status code 400 class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers
Http Code 403
MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept http code 302 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. https://en.wikipedia.org/wiki/List_of_HTTP_status_codes 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 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 https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 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 only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features. 10.2 Successful 2xx This class of status code indicates that the client's request was successfully received, understood, and accepted. 10.2.1 200 OK The request has succeeded. The information returned with the resp
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 http://www.keynote.com/mykeynote/help/error_list.asp 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 status 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 status code 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
large number of detailed error types, referred to as 'internal errors' are reported in Data Feed, Data Pulse, and MyKeynote raw data downloads. These are 'bucketed' into a smaller number of 'external' errors reported in MyKeynote graphs and data tables. Only external Keynote errors are listed on this page. For a listing of internal and external errors for Transaction Perspective and Application Perspective, see Internal/External Error Code Listing. Error Descriptions for Keynote Services Transaction Perspective and Application Perspective FTP Service Mobile App Monitoring Mobile Web Perspective Mobile Device Perspective Transaction Perspective and Application Perspective Errors These error codes are assigned by Keynote to conditions detected and reported by the Keynote Transaction Perspective and Application Perspective agents. Code Name Description 449 Retry The request should be retried after doing the appropriate action. 480 Login Failed Most likely, the login name used in the transaction has changed or the login name being used in the transaction is incorrect. 801 Connection Problem Connection Problem (Mobile error.) 802 Modem in use Modem in use. The modem is in use by another process or user. (Mobile error.) 804 Cannot connect to host Cannot connect to host. Verify that the SIM card is correctly inserted and the dial number in your profile. 805 Cannot configure PPP Cannot configure the PPP layer. (Mobile error.) 806 Authentification failed Authentification failed. Make sure you have the correct login and password. (Mobile error.) 807 Cannot configure network layer Cannot configure network layer. Cannot configure the network layer protocols. (Mobile error.) 808 Connection reset by peer Connection reset by peer. Verify the APN in the profile and your subscription. (Mobile error.) 811 WTP Abort WTP Abort. (Mobile error.) 812 Not Finished Not Finished. (Mobile error.) 813 Gateway not reachable Gateway not reachable. (Mobile error.) 814 USSD Error Code USSD Error Code. (Mobile error.) 815 SMS Send Error SMS Send Error. (Mobile error.) 816 SMS Wait Error SMS Wait Error. (Mobile error.) 817 Dial Error Dial Error. (Mobile error.) 818 PressKey Error Code PressKey (DTMF) Error Code. (Mobile error.) 819 Hang Up Error Code Hang Up Error Code. (Mobile error.) 820 Invalid Profile Profile does not exist. (Mobile error.) 821 Scr