Http Error 402
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 http code 403 of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETF http code 302 internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status http error wordpress code specifies 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
Http Status Codes Cheat Sheet
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 sub-codes only appear in the response payload and in documentation; not in the http 422 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 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http response example Learn more about Stack Overflow the company Business Learn more about hiring developers
Http 502
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack
Http 404
Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Difference between http response status code 402 https://en.wikipedia.org/wiki/List_of_HTTP_status_codes and 403 up vote 6 down vote favorite Friends and fellow users, We have both 402 and 403 http response codes. Though, 402 is reserved for future use. What is (or would be) the difference between these two. Payment not received should be equal to not authorized, shouldn't it? EDIT:I would like to know the answers on a "Why 402 is required when we already have 403" http://stackoverflow.com/questions/1270759/difference-between-http-response-status-code-402-and-403 angle. http httpresponse http-status-codes http-status-code-403 share|improve this question edited Sep 25 '12 at 12:57 kmindi 96811231 asked Aug 13 '09 at 8:25 rest_day 559924 add a comment| 3 Answers 3 active oldest votes up vote 5 down vote accepted 403 Forbidden The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Dots this help? share|improve this answer answered Aug 13 '09 at 8:36 Shoban 20.3k74998 Thanks Shoban, But I was looking at a "Why 402 is required when we already have 403" angle. –rest_day Aug 13 '09 at 8:40 2 Because 402 will mean (in the future) that the request MAY be repeated if the payement problem is somehow solved. –Tomas Dec 1 '10 at 12:59 add a comment| up vote 7 down vote The HTTP Statuscode
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 any 1xx status codes, servers http://www.restapitutorial.com/httpstatuscodes.html 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 and its client has been closed, or unless the proxy http error 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. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx http error 402 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 status code is received in response before continuing (or receive 417 Expectation Failed and not continue). 101 Switching Protocols The server understands and is willing to comply with the client'