Http Status Code 503 Error
Contents |
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 class of status code. Since HTTP/1.0 did
503 Error Iis
not define any 1xx status codes, servers MUST NOT send a 1xx response to an http error 503 service unavailable 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 http 504 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
503 Service Unavailable Fix
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 inform the client that the initial part of the request has been received and has not yet been rejected by the
Http 502
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 response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any messag
response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and how to fix http error 503. the service is unavailable is terminated by an empty line. There are no required headers for
Http Code 302
this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT http status codes cheat sheet 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 https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 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 itself requested the generation of the 1xx response. (For example, if a https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 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 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 prot
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 https://en.wikipedia.org/wiki/List_of_HTTP_status_codes This is a list of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. http://www.iana.org/assignments/http-status-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 phrases used are the http status 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 sub-codes http status code 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 the request's hea
1xx: Informational - Request received, continuing process 2xx: Success - The action was successfully received, understood, and accepted 3xx: Redirection - Further action must be taken in order to complete the request 4xx: Client Error - The request contains bad syntax or cannot be fulfilled 5xx: Server Error - The server failed to fulfill an apparently valid request Available Formats CSV Value Description Reference 100 Continue [RFC7231, Section 6.2.1] 101 Switching Protocols [RFC7231, Section 6.2.2] 102 Processing [RFC2518] 103-199 Unassigned 200 OK [RFC7231, Section 6.3.1] 201 Created [RFC7231, Section 6.3.2] 202 Accepted [RFC7231, Section 6.3.3] 203 Non-Authoritative Information [RFC7231, Section 6.3.4] 204 No Content [RFC7231, Section 6.3.5] 205 Reset Content [RFC7231, Section 6.3.6] 206 Partial Content [RFC7233, Section 4.1] 207 Multi-Status [RFC4918] 208 Already Reported [RFC5842] 209-225 Unassigned 226 IM Used [RFC3229] 227-299 Unassigned 300 Multiple Choices [RFC7231, Section 6.4.1] 301 Moved Permanently [RFC7231, Section 6.4.2] 302 Found [RFC7231, Section 6.4.3] 303 See Other [RFC7231, Section 6.4.4] 304 Not Modified [RFC7232, Section 4.1] 305 Use Proxy [RFC7231, Section 6.4.5] 306 (Unused) [RFC7231, Section 6.4.6] 307 Temporary Redirect [RFC7231, Section 6.4.7] 308 Permanent Redirect [RFC7538] 309-399 Unassigned 400 Bad Request [RFC7231, Section 6.5.1] 401 Unauthorized [RFC7235, Section 3.1] 402 Payment Required [RFC7231, Section 6.5.2] 403 Forbidden [RFC7231, Section 6.5.3] 404 Not Found [RFC7231, Section 6.5.4] 405 Method Not Allowed [RFC7231, Section 6.5.5] 406 Not Acceptable [RFC7231, Section 6.5.6] 407 Proxy Authentication Required [RFC7235, Section 3.2] 408 Request Timeout [RFC7231, Section 6.5.7] 409 Conflict [RFC7231, Section 6.5.8] 410 Gone [RFC7231, Section 6.5.9] 411 Length Required [RFC7231, Section 6.5.10] 412 Precondition Failed [RFC7232, Section 4.2] 413 Payload Too Large [RFC7231, Section 6.5.11] 414 URI Too Long [RFC7231, Section 6.5.12] 415 Unsupported Media Type [RFC7231, Section 6.5.13][RFC7694, Section 3] 4