Docs.cpanel.net. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server. 1992 This is a historic document and is not accurate anymore. Bad request 400 The request had bad syntax or was inherently impossible to be satisfied. An example scenario where a 401 Unauthorized error would be returned is if a user tries to access a resource that is protected by HTTP authentication, as in this Nginx tutorial. http://orgias.org/http-status/http-error-codes-301.html
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. Response body content may or may not be present. 202 Accepted The request has been accepted for processing, but the processing has not been completed. Stack Overflow. Create a wire coil Is turning off engines before landing "Normal"? https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Most common code used to indicate success. 201 Created The request has been fulfilled and resulted in a new resource being created. These status codes are applicable to any request method. This response MUST NOT use the multipart/byteranges content- type.
In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. 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. This response code probably is most famous one due to its frequency to occur in web. 405 Method Not Allowed The request method is known by the server but has been disabled and cannot be used. Http Code 302 A code of 498 indicates an expired or otherwise invalid token. 499 Token Required (Esri) Returned by ArcGIS for Server.
Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request. Http Response Example there is no facility for status returns from asynchronous operations such as this. Retrieved 16 October 2015. ^ "RFC7235 on code 401". https://en.wikipedia.org/wiki/List_of_HTTP_status_codes org.springframework.http.
All Rights Reserved. Http Code 403 IETF. 2014. Therefore, this same URI should be used by the client in future requests. 303 See Other Server sent this response to directing client to get requested resource to another URI with an GET request. 304 Not Modified This is used for caching purposes. Method 303 Method:
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 request entity is larger than the server is willing or able to process. HTTP 400 was changed in RFC 7231 to mean "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, invalid request message framing, or deceptive request routing)." I'm not saying 400 is correct usage in this case but it could be correct with the new definition of 400. –javajavajavajavajava Jun 21 at 18:16 @javajavajavajavajava: still, duplicate data is not a 'client error' in my mind, but that's in the eye of the beholder of course. –Wrikken Jul 16 at 23:45 add a comment| up vote 25 down vote Personally I go with the WebDAV extension 422 Unprocessable Entity. Http Status Code 400 If known, the length of the delay MAY be indicated in a Retry-After header. Http Status Codes Cheat Sheet 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. 504 Gateway Timeout This error response is given when the server is acting as a gateway and cannot get a response in time. 505 HTTP Version Not Supported The HTTP version used in the request is not supported by the server. 506 Variant Also Negotiates The server has an internal configuration error: transparent content negotiation for the request results in a circular reference. 507 Variant Also Negotiates 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. 511 Network Authentication Required The 511 status code indicates that the client needs to authenticate to gain network access.
If the servers can communicate on other ports, make sure that the firewall is allowing the traffic between them If your web application is configured to listen on a socket, ensure that the socket exists in the correct location and that it has the proper permissions 503 Service Unavailable The 503 status code, or Service Unavailable error, means that the server is overloaded or under maintenance. this content 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 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. 5xx Server Error The server failed to fulfill an apparently valid 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. Retrieved 16 October 2015. ^ "RFC7231 on code 400". The protocol SHOULD be switched only when it is advantageous to do so. Http 422
Cloudflare. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI. Is there a common practice when sending status codes? weblink CSGNetwork.com.
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 message-body; POST an entity describing or containing the result of the action; TRACE an entity containing the request message as received by the end server. 10.2.2 201 Created The request has been fulfilled and resulted in a new resource being created. Http 409 Retrieved January 8, 2015. ^ "401". In this application a manager user can create companies and has to give them a code.
Content developers should be aware that there might be clients that implement such a fixed limitation. 10.3.1 300 Multiple Choices The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location. httpstatus. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. Http 404 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.
For the moment it is for discussion only. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client. 10.3.4 303 See Other The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. Network Working Group. check over here someone's opinion on "what HTTP status codes mean"; note that the page essentialy says "this is what Apache means with 403, this is what IIS means with 403", and nowhere does it reference the official RFC.
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). The response MUST include the following header fields: Date, unless its omission is required by section 14.18.1 If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly. Why are they separated rest objects? Wikipedia The server successfully processed the request, but is returning information that may be from another source.
The new URI is not a substitute reference for the originally requested resource. Not Modified 304 If the client has done a conditional GET and access is allowed, but the document has not been modified since the date and time specified in If-Modified-Since field, the server responds with a 304 status code and does not send the document body to the client. The client SHOULD NOT repeat the request without modifications. Note: Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead.