Home > Error Codes > Cat Html Error Codes

Cat Html Error Codes

404 405 html cat symbol 406 408 409 410 411 412 413 414 415 416 417 418 420 422423 424 425 426 429 431 444 450 451 500 502 503 504 506 507 508 509 599HTTP CatsVersió CatalàDeveloped by @rogeriopvl. Images from Tomomi Imura.

Contents

with your friends! Tweet

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 Hypertext have a peek here Transfer Protocol (HTTP) response status codes. It includes codes from IETF https://en.wikipedia.org/wiki/List_of_HTTP_status_codes internet standards, other IETF RFCs, other specifications, and some additional 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. http://mashable.com/2011/12/17/http-status-cats/ The 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 Error Codes 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 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 599 Network connect timeout error 6.2 Internet Information Services Cat Html Error 6.3 nginx 6.4 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 Expectation Failed indicates the request should not be continued.[2] 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so.[5] 102 Processing (WebDAV; RFC 2518) A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the reque

Media Tech Business Entertainment World Lifestyle Watercooler Shop More Channels Videos Social Media Tech Business Entertainment World Lifestyle Watercooler Shop CompanyAbout UsLicensing & ReprintsArchiveMashable Careers ContactContact UsSubmit News AdvertiseAdvertise LegalPrivacy PolicyTerms of UseCookie Policy AppsiPhone / iPadAndroid ResourcesSubscriptions SitesMashable ShopJob BoardSocial Good Summit Tech Like Follow Follow HTTP Status Cats: Hilarious Motivational Posters [PICS] 4.2k Shares Share Tweet Share What's This? By Charlie White2011-12-17 21:13:51 UTC Catastrophic Status Messages 100 Continue Image ©Tomomi Imura, used with permission 200 OK Image ©Tomomi Imura, used with permission 206 Partial Content Image ©Tomomi Imura, used with permission 207 Multi-Status Image ©Tomomi Imura, used with permission 300 Multiple Choices Image ©Tomomi Imura, used with permission 301 Moved Permanently Image ©Tomomi Imura, used with permission 302 Found Image ©Tomomi Imura, used with permission 303 See Other Image ©Tomomi Imura, used with permission 307 Temporary Redirect Image ©Tomomi Imura, used with permission 401 Unauthorized Image ©Tomomi Imura, used with permission 402 Payment Required Image ©Tomomi Imura, used with permission 403 Forbidden Image ©Tomomi Imura, used with permission 404 Not Found Image ©Tomomi Imura, used with permission 405 Method Not Allowed Image ©Tomomi Imura, used with permission 406 Not Acceptable Image ©Tomomi Imura, used with permission 408 Request Timeout Image ©Tomomi Imura, used with permission 409 Conflict Image ©Tomomi Imura, used with permission 410 Gone Image ©Tomomi Imura, used with permission 413 Request Entity Too Large Image ©Tomomi Imura, used with permission 414 Request-URI Too Long Image ©Tomomi Imura, used with permission 416 Requested Range Not Satisfiable Image ©Tomomi Imura, used with permission 417 Expectation Failed Image ©Tomomi Imura, used with permission 422 Unprocessable Entity Image ©Tomomi Imura, used with permission 423 Locked Image ©Tomomi Imura, used with permission 424 Failed Dependency Image ©Tomomi Imura