4xx client error – the request contains bad syntax or cannot be fulfilled; 5xx server error – the server failed to fulfil an apparently. 1. Unable to execute the job, ending with. 210. Different contents between the server and the client.(WebDav Extension). ; Redirections ; 300. Multiple choice.The server has different answers, so it must.
Similar videoHow to fix the 0x80070021 CMon 19.8 website load error * * * EMPTY * * *
HTTP Status Codes
500's - Server Error Responses
Internal Server Error
Server encountered an unexpected condition that prevented request fulfillment.
Request is unrecognizable or server lacks ability to fulfill it
Server received an invalid response from an upstream server and could not fulfill request
Server is currently unavailable
Server did not receive a timely response from upstream server
HTTP Version Not Supported
Server does not support the HTTP protocol used in request
Variant Also Negotiates
Content negotiation results in circular reference
Server detected an infinite loop while processing request
Bandwidth Limit Exceeded
Apache extension not defined in RFC's to communicate bandwidth allocation exceeded
Further extensions to the request are required to fulfill it
Network Authentication Required
Client is required to authenticate to gain network access
Network Read Timeout Error
Client behind proxy experiences network read timeout error
Network Connect Timeout Error
Client behind proxy experiences network connect timeout error
List of HTTP status codes
Response codes of the Hypertext Transfer Protocol
This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in internal error code 210 common applications of the HTTP. The first digit of the status code specifies one of netlib_recv failed, error=10058 standard classes of responses. The message phrases shown are typical, but any human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).
The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.
All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role. There are five classes defined by the standard:
- 1xx informational response – the request was received, continuing process
- 2xx successful – the request was successfully received, understood, internal error code 210, and accepted
- 3xx redirection – further action needs to 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 fulfil an apparently valid request
1xx informational response
An informational response indicates that the request was received and understood. It is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty error loading operating system windows xp. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.
- 100 Continue
- The server has received the request headers and the internal error code 210 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 as a header in its initial request and receive a status code in response before sending the body. If the client receives an error code such as 403 (Forbidden) or 405 (Method Not Allowed) then it should not send the request's body. The response indicates that the request should be repeated internal error code 210 the header as it indicates that the server does not support expectations (this is the case, for example, of HTTP/1.0 servers).
- 101 Switching Protocols
- The requester has asked the server to switch protocols and the server has agreed to do so.
- 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 yet. This prevents the client from timing out and assuming the request was lost.
- 103 Early Hints (RFC 8297)
- Used to return some response headers before final HTTP message.
This class of status codes indicates the action requested by the client was received, understood, and accepted.
- 200 OK
- Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
- 201 Created
- The request has been fulfilled, resulting in the creation of a new resource.
- 202 Accepted
- The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.
- 203 Non-Authoritative Information (since HTTP/1.1)
- The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.
- 204 No Content
- The server successfully processed the request, and is not returning any content.
- 205 Reset Content
- The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.
- 206 Partial Content (RFC 7233)
- The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
- 207 Multi-Status (WebDAV; RFC 4918)
- The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
- 208 Already Reported (WebDAV; RFC 5842)
- The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, internal error code 210, and are not being included again.
- 226 IM Used (RFC 3229)
- The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection.
A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD, internal error code 210. A user agent may automatically redirect a request. A user agent should detect and intervene to prevent cyclical redirects.
- 300 Multiple Choices
- Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.
- 301 Moved Permanently
- This and all future requests should be directed to the given URI. 
- 302 Found (Previously "Moved temporarily")
- Tells the client to look at (browse to) another URL. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect with the same method (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 redirects by changing the method to GET. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.
- 303 See Other (since HTTP/1.1)
- The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI.
- 304 Not Modified (RFC 7232)
- Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.
- 305 Use Proxy (since HTTP/1.1)
- The requested resource is available only through a proxy, the address for which is provided in the response. For security reasons, many HTTP clients (such as Mozilla Firefox and Internet Explorer) do not obey this status code.
- 306 Switch Proxy
- No longer used. Originally meant "Subsequent requests should use the specified proxy."
- 307 Temporary Redirect (since HTTP/1.1)
- In this case, the request should be repeated with another URI; however, future requests should still use the original URI, internal error code 210. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.
- 308 Permanent Redirect (RFC 7538)
- This and all future requests should be directed to the given URI. 308 parallel the behaviour of 301, but does not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.
4xx client errors
This class of status code is intended for situations in which the error seems to have been caused by the client. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user.
- 400 Bad Request
- The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
- 401 Unauthorized (RFC 7235)
- Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. 401 semantically means "unauthorised", the user does not have valid authentication credentials for the target resource.
- Note: Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.
- 402 Payment Required
- Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler, but that has not yet happened, and this code is not widely used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.Sipgate uses this code if an account does iphone error 1015 have sufficient funds to start a call.Shopify uses this code when the store has not paid their fees and is temporarily disabled.Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments.
- 403 Forbidden
- The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). This code is also typically used if the request provided authentication by answering the WWW-Authenticate header field challenge, but the server did not accept that authentication. The request should not be repeated.
- 404 Not Found
- The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
- 405 Method Not Allowed
- A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.
- 406 Not Acceptable
- The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. Error 10022 miranda Content negotiation.
- 407 Proxy Authentication Required (RFC 7235)
- The client must first authenticate itself with the proxy.
- 408 Request Timeout
- The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."
- 409 Conflict
- Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.
- 410 Gone
- Indicates that the resource requested was previously in use but is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
- 411 Length Required
- The request did not specify the length of its content, which is required by the requested resource.
- 412 Precondition Failed (RFC 7232)
- The server does not meet one of the preconditions that the requester put on the request header fields.
- 413 Payload Too Large (RFC 7231)
- The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".
- 414 URI Too Long (RFC 7231)
- The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously.
- 415 Unsupported Media Type (RFC 7231)
- The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
- 416 Range Not Satisfiable (RFC 7233)
- The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously.
- 417 Expectation Failed
- The server cannot meet the requirements of the Expect request-header field.
- 418 I'm a teapot (RFC 2324, RFC 7168)
- This code was defined in 1998 as one of the traditional IETFApril Fools' jokes, in RFC 2324, internal error code 210 Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee. This HTTP status is used as an Easter egg in some websites, such as Google.com's "I'm a teapot" easter egg.
- 421 Misdirected Request (RFC 7540)
- The request was directed at a server that is not able to produce a response (for example because of connection reuse).
- 422 Unprocessable Entity (WebDAV; RFC 4918)
- The request was well-formed but was unable to be followed due to semantic errors.
- 423 Locked (WebDAV; RFC 4918)
- The resource that is being accessed is locked.
- 424 Failed Dependency (WebDAV; RFC 4918)
- The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).
- 425 Too Early (RFC 8470)
- Indicates that the server is unwilling to risk processing a request that might be replayed.
- 426 Upgrade Required
- The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.
- 428 Precondition Required (RFC 6585)
- The internal error code 210 server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
- 429 Too Many Requests (RFC 6585)
- The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.
- 431 Request Header Fields Too Large (RFC 6585)
- The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
- 451 Unavailable For Legal Reasons (RFC 7725)
- A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource. The code 451 was chosen as a reference to the novel Fahrenheit 451 (see the Acknowledgements in the RFC).
5xx server errors
The server failed to fulfil a request.
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.
- 500 Internal Server Error
- A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
- 501 Not Implemented
- The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).
- 502 Bad Gateway
- The server was acting as a gateway or proxy and received an invalid response from the upstream server.
- 503 Service Unavailable
- The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.
- 504 Gateway Timeout
- The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
- 505 HTTP Version Not Supported
- The server does not support the HTTP protocol version used in the request.
- 506 Variant Also Negotiates (RFC 2295)
- Transparent content negotiation for the request results in a circular reference.
- 507 Insufficient Storage (WebDAV; RFC 4918)
- The server is unable to store the representation needed to complete the request.
- 508 Loop Detected (WebDAV; RFC 5842)
- The server detected an infinite internal error code 210 while processing the request (sent instead of 208 Already Reported).
- 510 Not Extended (RFC 2774)
- Further extensions to the request are required for the server to fulfil it.
- 511 Network Authentication Required (RFC 6585)
- The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used internal error code 210 require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).
The following codes are not specified by any standard.
- 419 Page Expired (Laravel Framework)
- Used by the Laravel Framework when a CSRF Token is missing or expired.
- 420 Method Failure (Spring Framework)
- A deprecated response used by the Spring Framework when a method has failed.
- 420 Enhance Your Calm (Twitter)
- Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the 429 Too Many Requests response code instead. The phrase "Enhance your calm" comes from the 1993 movieDemolition Man, and its association with this number is likely a reference to cannabis.
- 430 Request Header Fields Internal error code 210 Large (Shopify)
- Used by Shopify, instead of the 429 Too Many Requests response code, when too many URLs are requested within a certain time frame.
- 450 Blocked by Windows Parental Controls (Microsoft)
- The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.
- internal error code 210 Invalid Token (Esri)
- Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.
- 499 Token Required (Esri)
- Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted.
- 509 Bandwidth Limit Exceeded (Apache Web Server/cPanel)
- The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.
- 529 Site is overloaded
- Used by Qualys in the SSLLabs server testing API to signal that the site can't process the request.
- 530 Site is frozen
- Used by the Pantheon web platform to indicate a site that has been frozen due to inactivity.
- 598 (Informal convention) Network read timeout error
- Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.
- 599 Network Connect Timeout Error
- An error used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.
Internet Information Services
Microsoft's Internet Information Services (IIS) web server expands the 4xx error space to signal errors with the client's request.
- 440 Login Time-out
- The client's session has expired and must log in again.
- 449 Retry With
- The server cannot honour the request because the user has not provided the required information.
- 451 Redirect
- Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users' mailbox. The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.
IIS sometimes uses additional decimal sub-codes for more specific information, however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code.
The nginx web server software expands the 4xx error space to signal issues with the client's request.
- 444 No Response
- Used internally to instruct the server to return no information to the client and close the connection immediately.
- 494 Request header too large
- Client sent too large request or too long header line.
- 495 SSL Certificate Error
- An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.
- 496 SSL Certificate Required
- An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.
- 497 HTTP Request Sent to HTTPS Port
- An expansion of the 400 Bad Request response code, used when the client has made internal error code 210 HTTP request to a port listening for HTTPS requests.
- 499 Client Closed Request
- Used when the client has closed the request before the server could send a response.
Cloudflare's reverse proxy service expands the 5xx series of errors space to signal issues with the origin server.
- 520 Web Server Returned an Unknown Error
- The origin server returned an empty, unknown, or unexpected response to Cloudflare.
- 521 Web Server Is Down
- The origin server refused connections from Cloudflare. Security solutions at the origin may be blocking legitimate connections from certain Cloudflare IP addresses.
- 522 Connection Timed Out
- Cloudflare timed out contacting the origin server.
- 523 Origin Is Unreachable
- Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect or missing.
- 524 A Timeout Occurred
- Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response.
- 525 SSL Handshake Failed
- Cloudflare could not negotiate a SSL/TLS handshake with the origin server.
- 526 Invalid SSL Certificate
- Cloudflare could not validate the SSL certificate on the origin web server. Also used by Cloud Foundry's gorouter.
- 527 Railgun Error
- Error 527 indicates an interrupted connection between Cloudflare and the origin server's Railgun server.
- Error 530 is returned along with a 1xxx error.
AWS Elastic Load Balancer
Amazon's Elastic Load Balancing adds a few custom return codes
- Client closed the connection with the load balancer before the idle timeout period elapsed. Typically when client timeout is sooner than the Elastic Load Balancer's timeout.
- The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.
- 561 Unauthorized
- An error around authentication returned by a server registered with a load balancer. You configured a listener rule to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user.
Caching warning codes
The following caching related warning codes are specified under RFC 7234. Unlike the other status codes above, these are not sent as internal error code 210 response status in the HTTP protocol, but as part of the "Warning" HTTP header. Since this header is often neither sent by servers nor acknowledged by clients, it was obsoleted by internal error code 210 HTTP Working Group with RFC 9111.
- 110 Response is Stale
- The response provided by a cache is stale (the content's age exceeds a maximum age set by a Cache-Control header or heuristically chosen lifetime).
- 111 Revalidation Failed
- The cache was unable to validate the response, due to an inability to reach the origin server.
- 112 Disconnected Operation
- The cache is intentionally disconnected from the rest internal error code 210 the network.
- 113 Heuristic Expiration
- The cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24 hours.
- 199 Miscellaneous Warning
- Arbitrary, non-specific warning. The warning text may be logged or presented to the user.
- 214 Transformation Applied
- Added by a proxy if it applies any transformation to the representation, such as changing the content encoding, media type or the like.
- 299 Miscellaneous Persistent Warning
- Same as 199, but indicating a persistent warning.
- ^Emphasised words and phrases such as must and should represent interpretation guidelines as given by RFC 2119
- ^"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". IETF. Archived from the original on May 25, 2017. Retrieved December 16, 2017.
- ^ abc"Hypertext Transfer Protocol (HTTP) Status Code Registry". Iana.org. Archived from the original on December 11, 2011. Retrieved January 8, 2015.
- ^"10 Status Code Definitions". W3. Archived from the original on March 16, 2010. Retrieved October 16, 2015.
- ^"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content – 5.1.1. Expect". Archived from the original on May 25, 2017. Retrieved September 27, 2017.
- ^"101". httpstatus. Archived from the original on October 30, 2015. Retrieved October 16, 2015.
- ^Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (February 1999). HTTP Extensions for Distributed Authoring – WEBDAV. IETF. doi:10.17487/RFC2518. RFC2518. Retrieved October 24, 2009.
- ^Oku, Kazuho (December 2017). An HTTP Status Code for Indicating Hints. IETF. doi:10.17487/RFC8297. RFC8297. Retrieved December 20, 2017.
- ^"200 OK". Hypertext Transfer Protocol – HTTP/1.1. IETF. June 1999. sec. 10.2.1. doi:10.17487/RFC2616. RFC2616. Retrieved August 30, 2016.
- ^Stewart, Mark; djna. "Create request with POST, which response codes 200 or 201 and content". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
- ^"202 Accepted". httpstatuses.com. Retrieved February 23, 2022.
- ^"RFC 7231, Section 6.3.4". Archived from the original on May 25, 2017.
- ^"RFC 7230, Section 5.7.2". Archived from the original on February 3, 2016. Retrieved February 3, 2016.
- ^Simmance, Chris. "Server Response Codes And What They Mean". koozai. Archived from the original on September 26, 2015. Retrieved October 16, 2015.
- ^"IETF RFC7231 section 6.3.6. – 205 Reset Content". IETF.org, internal error code 210. Archived from the original on May 25, 2017. Retrieved September 6, 2018.
- ^"diff --git a/linkchecker.module b/linkchecker.module". Drupal. Archived from the original on March 4, 2016. Retrieved October 16, 2015.
- ^ abcdeDusseault, Lisa, ed. (June 2007). HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV). IETF. doi:10.17487/RFC4918. RFC4918. Retrieved October 24, 2009.
- ^Delta encoding in HTTP. IETF. January 2002. doi:10.17487/RFC3229. RFC3229. Retrieved February 25, 2011.
- ^"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". IETF. Archived from the original on May 25, 2017. Retrieved February 13, 2016.
- ^"300". httpstatus. Archived from the original on October 17, 2015. Retrieved October 16, 2015.
- ^"301". httpstatus. Archived from the original on October 27, 2015. Retrieved October 16, 2015.
- ^Berners-Lee, Tim; Fielding, Roy T.; Nielsen, Henrik Frystyk (May 1996). Hypertext Transfer Protocol – HTTP/1.0. IETF. doi:10.17487/RFC1945. RFC1945. Retrieved October 24, 2009.
- ^"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4". IETF. Archived from the original on May 25, 2017. Retrieved June 12, 2014.
- ^"303". httpstatus. Archived from the original on October 22, 2015. Retrieved October 16, 2015.
- ^"304 Not Modified". Mozilla Developer Network. Archived from the original on July 2, 2017. Retrieved July 6, 2017.
- ^Cohen, Josh. "HTTP/1.1 305 and 306 Response Codes". HTTP Working Group. Archived from the original on September 8, 2014. Retrieved September 8, 2014.
- ^"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4.7 307 Temporary Redirect". IETF. 2014. Archived from the original on May 25, 2017. Retrieved September 20, 2014.
- ^"The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)". Internet Engineering Task Force. April 2015. Archived from the original on April 16, 2015. Retrieved April 6, 2015.
- ^"E Explanation of Failure Codes". Oracle. Archived from the original on February 16, 2015. Retrieved October 16, 2015.
- ^"RFC7231 on code 400". Tools.ietf.org. Archived from the original on May 25, 2017. Retrieved January 8, 2015.
- ^"401". httpstatus. Archived from the disk error press any key to restart on October 17, 2015. Retrieved October 16, 2015.
- ^"RFC7235 on code 401". Tools.ietf.org, internal error code 210. Archived from the original on February 7, 2015. Retrieved February 8, 2015.
- ^"The GNU Taler tutorial for PHP Web shop developers 0.4.0". docs.taler.net. Archived from the original on November 8, 2017. Retrieved October 29, 2017.
- ^"Google API Standard Error Responses". 2016, internal error code 210. Archived from the original on May 25, 2017. Retrieved June 21, 2017.
- ^"Sipgate API Documentation". Archived from the original on July 10, 2018. Retrieved July 10, 2018.
- ^"Shopify Documentation". Archived from the original on July 25, 2018. Retrieved July 25, 2018.
- ^"Stripe API Reference – Errors". stripe.com. Internal error code 210 October 28, 2019.
- ^Singh, Prabhat; user1740567. "Spring 3.x JSON status 406 "characteristics not acceptable according to the request "accept" headers ()"", internal error code 210. Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
- ^"407". httpstatus. Archived from the original on October 11, 2015. Retrieved October 16, 2015.
- ^"408". httpstatus, internal error code 210. Archived from the original on October 31, 2015. Retrieved October 16, 2015.
- ^"Does Google treat 404 and 410 status codes differently? (Youtube)", internal error code 210. 2014. Archived from the original on January 8, 2015. Retrieved February 4, 2015.
- ^"List of HTTP status codes". Google Books. Retrieved October 16, 2015.
- ^"RFC7232, section 4.2". Archived from the original on June 26, 2019. Retrieved June 20, 2019.
- ^"RFC2616 on status 413". Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved November 11, internal error code 210, 2015.
- ^user27828. "GET Request – Why is my URI so long?". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, internal error code 210, 2015.
- ^"RFC2616 on status 414". Tools.ietf.org. Archived from the original on Internal error code 210 7, 2011. Retrieved November 11, 2015.
- ^"RFC7231 on status 415". Tools.ietf.org. Archived from the original on May 25, 2017. Retrieved May 2, 2019.
- ^Sigler, Chris. "416 Requested Range Not Satisfiable". GetStatusCode. Archived from the original on October 22, 2015. Retrieved October 16, 2015.
- ^"RFC2616 on status 416". Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved November 11, 2015.
- ^TheDeadLike. "HTTP/1.1 Status Codes 400 and 417, cannot choose which". serverFault, internal error code 210. Archived from the original on October 10, 2015. Retrieved October 16, 2015.
- ^Larry Masinter (April 1, 1998). Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). doi:10.17487/RFC2324. RFC2324.
- ^I'm a teapot
- ^Barry Schwartz (August 26, 2014). "New Google Easter Egg For SEO Geeks: Server Status 418, I'm A Teapot". Search Engine Land. Archived from the original on November 15, 2015. Retrieved November 4, 2015.
- ^"Google's Teapot". Retrieved October 23, 2017.[dead link]
- ^"Hypertext Transfer Protocol version 2". March 2015. Archived from the original on April 25, 2015. Retrieved April 25, 2015.
- ^"9.1.1. Connection Reuse". RFC7540. May 2015. Archived from the original on June 23, 2015. Retrieved July 11, 2017.
- ^Khare, R; Lawrence, S. "Upgrading to TLS Within HTTP/1.1". IETF. Network Working Group. Archived from the original on October 8, 2015. Retrieved October 16, 2015.
- ^ abcdNottingham, M.; Fielding, R. (April 2012), internal error code 210. "RFC 6585 – Additional HTTP Status Codes". Request for Comments. Internet Engineering Task Force. Archived from the original on May 4, 2012. Retrieved May 1, 2012.
- ^Bray, T. (February 2016). "An HTTP Status Code to Report Legal Obstacles". ietf.org. Archived from the original on March 4, 2016. Retrieved March 7, 2015.
- ^"Server Error Codes". CSGNetwork.com. Archived from the original on October 8, 2015. Retrieved October 16, 2015.
- ^mrGott. "HTTP Status Codes To Handle Errors In Your API". mrGott. Archived from the original on September 30, 2015. Retrieved October 16, 2015.
- ^Fisher, Tim. "500 Internal Server Error". Lifewire. Archived from the original on February 23, 2017. Retrieved February 22, 2017.
- ^"HTTP Error 501 Not implemented". Check Up Down. Archived from the original on May 12, 2017. Retrieved February 22, 2017.
- ^Fisher, Tim. "502 Bad Gateway". Lifewire. Archived from the original on February 23, 2017. Retrieved February 22, 2017.
- ^alex. "What is the correct HTTP status code to send when a site is down for maintenance?". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
- ^"HTTP Error 504 Gateway timeout". Check Up Down. Archived from the original on September 20, 2015. Retrieved October 16, 2015.
- ^"HTTP Error 505 – HTTP version not supported". Check Up Down. Archived from the original on September 24, 2015. Retrieved October 16, 2015.
- ^Holtman, internal error code 210, Koen; Mutz, Andrew H. (March 1998). Transparent Content Negotiation in HTTP. IETF. doi:10.17487/RFC2295. RFC2295. Retrieved October 24, 2009.
- ^Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. IETF. doi:10.17487/RFC2774. RFC2774. Retrieved October 24, 2009.
- ^"Enum HttpStatus". Spring Framework. org.springframework.http. Archived from the original on October 25, 2015. Retrieved October 16, 2015.
- ^"HTTP Status Codes and SEO: what you need to know". ContentKing. Retrieved August 9, 2019.
- ^"Screenshot of error page". Archived from the original(bmp) on May 11, 2013. Retrieved October 11, 2009.
- ^ ab"Using token-based authentication". ArcGIS Server SOAP SDK. Archived from the original on September 26, 2014. Retrieved September 8, internal error code 210, 2014.
- ^"HTTP Error Codes and Quick Fixes". Docs.cpanel.net. Archived from the original on November 23, 2015. Retrieved October 15, internal error code 210, 2015.
- ^"SSL Labs API v3 Documentation". github.com.
- ^"Platform Considerations HWM
HTTP response status codes
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:
- Informational responses (–)
- Successful responses (–)
- Redirection messages (–)
- Client error responses (–)
- Server error internal error code 210 (–)
The below status codes are defined by section 10 of RFC 2616. You can find an updated specification in Internal error code 210 7231.
Note: If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server's software.
This interim response indicates that the client should continue internal error code 210 request internal error code 210 ignore the response if the request is already finished.
This code is sent in response to an request header from the client and indicates the protocol the server is switching to.
This code indicates that the server has received and is processing the request, internal error code 210, but no response is available yet.
This status code is primarily intended to be used with the header, letting the user agent start preloading resources while the server prepares a response.
The request succeeded. The result meaning of "success" depends on the HTTP method:
- : The resource has been fetched and transmitted in the message body.
- : The representation headers are included in the response without any message body.
- or : The resource describing the result of the action is transmitted in the message body.
- : The message body contains the request message as received by the server.
The request succeeded, and a new resource was created as a result. This is typically the response sent after requests, internal error code 210, or some requests.
The request has been received but not yet acted upon. It is noncommittal, internal error code 210, since there is no way in Internal error code 210 to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.
This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from internal error code 210 local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the response is preferred to this status.
There is no content to send for this request, but the headers may be useful. internal error code 210 The user agent may update its cached headers for this resource with the new ones, internal error code 210.
Tells the user agent to reset the document which sent this request.
This response code is used when the header is sent from the client to request only part of a resource.
Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
Used inside a response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
- (HTTP Delta encoding)
The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
The request has more than one possible internal error code 210. The user agent or user should choose one of them. (There is no standardized way of choosing one of the responses, internal error code 210, but HTML links to the possibilities are recommended so the user can pick.)
The URL of the requested resource has been changed permanently. The new URL is given in the response.
internal error code 210 This response code means that the URI of requested resource has been changed temporarily, internal error code 210. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.
This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.
The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the HTTP response code, with the exception that the user agent must not change the Internal error code 210 method used: if a was used in the first request, a must be used in the second request.
This means that the resource is now permanently internal error code 210 at another URI, specified by the HTTP Response header. This has the same semantics as the HTTP response code, with the exception that the user agent must not change the HTTP method used: if a was used in the first request, a must be used in the second request.
Client error responses
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, internal error code 210, invalid request message framing, or deceptive request routing).
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
This response code is internal error code 210 for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
Internal error code 210 client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlikethe client's identity is known to the server.
The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.
The request method is known by the server but is not supported by the target resource. For example, internal error code 210, an API may not allow calling to remove a resource.
This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content that conforms to the criteria given by the user agent.
This is internal error code 210 to but authentication is needed to be done by a proxy.
This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. internal error code 210 This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.
This response is sent when a request conflicts with the current state of the server.
This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links internal error code 210 the resource. The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code. internal error code 210
Server rejected the request because the header field is not defined and the server requires it.
The client has indicated preconditions in its headers which the server does not meet.
Request entity is larger than limits defined by server. The server might close the connection or return an header field.
The URI requested by the client is longer than the server is willing to interpret.
The media format of the requested data is not supported by the server, so the server is rejecting the request.
The range specified by the header field in the request cannot be fulfilled. It's possible that the range is outside the size of the target URI's data.
This response code means the expectation indicated by the request header field cannot be met by the server.
The server refuses the attempt to brew coffee with a teapot.
The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
The request internal error code 210 well-formed but was unable to be followed due to semantic errors.
The resource that is being accessed is locked.
The request failed due internal error code 210 failure of a previous request.
Indicates that the server is unwilling to risk processing a request that internal error code 210 be replayed.
The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an header in a 426 response to indicate the required protocol(s).
internal error code 210 The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client s a resource's state, modifies it and s it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
The user has sent too many requests in a given amount of time ("rate limiting").
The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.
The user agent requested a resource that cannot legally be provided, such as a web page censored by a government.
Server error responses
The server has encountered a situation it does not know how to handle.
The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are and .
This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
The server is not ready aida64 fpu error handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
This error response is given when the server is acting as a gateway and cannot get a response in time.
The HTTP version used in the request is not supported by the server.
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
The server detected an infinite loop while processing the request.
Further extensions to the request are required for the server to fulfill it.
Indicates that the client needs to authenticate to gain network access.
BCD tables only load in the browser