Http 400 Error 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 This is a list of Hypertext Transfer Protocol (HTTP) response status codes. It
Http Status Codes Cheat Sheet
includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional http response example commonly used codes. The first digit of the status code specifies one of five classes of response; an HTTP client must recognise
Http Error Wordpress
these five classes at a minimum. 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 http code 403 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 actual HTTP status code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 5xx Server Error 6 http code 302 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 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 lon
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 Transfer Protocol (HTTP) response status codes. It includes codes from IETF
Http 422
internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. The first http 404 digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum.
Http 502
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 https://en.wikipedia.org/wiki/List_of_HTTP_status_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 Internet Information Services 6.2 nginx 6.3 Cloudflare 7 See https://en.wikipedia.org/wiki/List_of_HTTP_status_codes 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 request, but no response is available y
/sponsored-data-tutorials/portal /sponsored-data-tutorials/csr /sponsored-data-tutorials/dns /sponsored-data-tutorials/onboarding /sponsored-data-tutorials/docs /sponsored-data-tutorials/faq /sponsored-data-tutorials/simulator/video-1 /sponsored-data-tutorials/simulator/video-2 /sponsored-data-tutorials/simulator/video-3 /sponsored-data-tutorials/simulator/video-4 /sponsored-data-tutorials/simulator/video-5 /sponsored-data-tutorials/simulator/video-6 /sponsored-data-tutorials/simulator/video-7 /sponsored-data-tutorials/simulator/video-8 /sponsored-data-tutorials/simulator/video-9 /sponsored-data-tutorials/simulator/ineligible-1 /sponsored-data-tutorials/simulator/ineligible-2 /sponsored-data-tutorials/simulator/ineligible-3 /sponsored-data-tutorials/simulator/ineligible-4 /sponsored-data-tutorials/simulator/ineligible-5 /sponsored-data-tutorials/simulator/ineligible-6 /sponsored-data-tutorials/simulator/ineligible-7 /sponsored-data-tutorials/simulator/ineligible-8 /sponsored-data-tutorials/simulator/ineligible-9 /sponsored-data-tutorials/examples /sponsored-data-tutorials/examples/tunnel /sponsored-data-tutorials/examples/video-download /sponsored-data-tutorials/examples/cdn /sponsored-data-tutorials/examples/ssl /sponsored-data-tutorials/examples/chunked /sponsored-data-tutorials/examples/management /sponsored-data-tutorials/examples/upload Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox The MMS API was deprecated on July 29, 2015. Get more information about our supported APIs. x /apis/sms-mms /apis/mms/docs The Device Capabilities API was deprecated on July 29, 2015. Get more information about our supported APIs. x /apis/device-capabilities /apis/device-capabilities/docs Sign In Download AT&T ARO AT&T Application Resource Optimizer Tour Docs Best Practices News Blog Forums /site/website/application-resource-optimizer/docs/best-practices/http-400-and-500-error-codes/index.xml HTTP 400 and 500 Status Codes Introduction The AT&T Application Resource Optimizer (ARO) specifically identifies all HTTP 400 and 500 Status