It means that the requested resource is locked. According to W3 HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19. have a peek here
This presents many security issues; e.g., an attacking intermediary may be inserting cookies into the original domain's name space, may be observing cookies or HTTP authentication credentials sent from the user It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed If everything doesn't work out ok, the server will send back a 417 Expectation Failed. http://www.restapitutorial.com/httpstatuscodes.html
HTTP 508 Loop Detected The server encountered an infinite loop while attempting to serve the requested resource. The response representation SHOULD contain a link to a resource that allows the user to submit credentials (e.g. HTTP 502 Bad Gateway This occurs when the server is acting as a proxy or gateway, and receives an invalid response from the upstream server. Wikipedia The server does not meet one of the preconditions that the requester put on the request. 413 Request Entity Too Large The server is refusing to process a request because
The client SHOULD NOT repeat the request without modifications. A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses. Stack Overflow. Http Code 403 Ultimate Guide to Web Hosting Check out our Ultimate Guide to Web Hosting.
Wikipedia Standard response for successful HTTP requests. The client MAY repeat the request with a suitable Authorization header field (section 14.8). HTTP 505 HTTP Version Not Supported This error means that the server does not support the HTTP protocol version used in the request. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
a web browser or other HTTP client). Http Code 302 For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions. Methods can potentially take a long period of time to process, especially methods that support the Depth header. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use
The server MAY close the connection to prevent the client from continuing the request. https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-http-error-codes Internet Engineering Task Force. Http Error Wordpress 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. Http Response Example The actual response will depend on the request method used.
This status is intended for use when intercepting proxies used to control access to the network — that is "Captive Portals" used to require login or Terms of Service agreement before http://bookmarq.net/http-error/http-error-codes.php For this reason, 302 should only be used on URLs that accept POST data (web forms) if the server can actually accept the submitted data at the original URL, and use HTTP 408 Request Timeout This error happens when the server times out while waiting for the request. That's a protocol. Http 422
There are many situations that could cause a web server to respond to a request with a particular error code--we will cover common potential causes and solutions. If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity Check This Out The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.
Since HTTP/1.1 304 Not Modified If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this Http 404 Wikipedia Further extensions to the request are required for the server to fulfill it. 511 Network Authentication Required The 511 status code indicates that the client needs to authenticate to gain HTTP 496 No Cert (Nginx) Not part of the standard.
Servers will often provide additional information about what specifically went wrong with the request. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. HTTP 426 Upgrade Required The client should switch to a different protocol, as specified in the upgrade header. Http 502 This error code is specific to IIS 6.0. 500.18 URL authorization store cannot be opened.
There are no required headers for this class of status code. To put that in more technical language, the specification describes the 506 error with: Transparent content negotiation for the request results in a circular reference. This error code is specific to IIS 6.0. 403 Forbidden. 403.1 Execute access forbidden. this contact form This work by RestApiTutorial.com is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. HTTP 424 Failed Dependency Used with WebDav. Error code for user not authorized to perform the operation or the resource is unavailable for some reason (e.g. Community Tutorials Questions Projects Tags Newsletter RSS Distros & One-Click Apps Terms, Privacy, & Copyright Security Report a Bug Get Paid to Write Almost there!
HTTP 511 Network Authentication Required The 511 error is returned when the client needs to authenticate to gain network access. Wikipedia The origin server requires the request to be conditional. The entity format is specified by the media type given in the Content-Type header field. The browser should then serve the saved version of the resource, since it hasn't changed.
Hypertext Transfer Protocol – HTTP/1.0. The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed HTTP Status Codes This page is created from HTTP status code information found at ietf.org and Wikipedia.
HTTP Requests and Responses HTTP stands for "HyperText Transfer Protocol." What's a Protocol? Wikipedia The server successfully processed the request, but is not returning any content. A "web page" was thought of as an actual "page." A site was a collection of documents. Article has been viewed 200K times.
This response is only cacheable if indicated by a Cache-Control or Expires header field. The response body SHOULD include enough information for the user to recognize the source of the conflict. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead. HTTP 494 Request Header Too Large (Nginx) Not part of the standard, but was used by Nginx.
JSEND) are not used and nothing is in the body (e.g. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. See section 8.2.3 for detailed discussion of the use and handling of this status code. Domain validation errors, missing data, etc.