Action/Framework Work Platform Error Code Error Name Description
Action/Framework Work Platform Error Code Error Name Description
HTTP Web 100 Continue Information responses
The client SHOULD continue with its request.The initial part of a request has been received and has not yet been rejected by the server.If the request has already been completed, ignore this response.The server MUST send a final response after the request has been completed.
HTTP Web 101 Switching Protocols Information responses
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.
HTTP Web 102 Processing Information responses
This code indicates that the server has received and is processing the request, but no response is available yet.
HTTP Web 103 Early Hints Information responses
This status code is primarily intended to be used with the Link header to allow the user agent to start preloading resources while the server is still preparing a response.
HTTP Web 200 OK Successful responses
The request has succeeded. The meaning of success varies depending on the HTTP method:
GET: The resource has been fetched and is transmitted in the message body.
HEAD: The entity headers are in the message body.
PUT or POST: The resource describing the result of the action is transmitted in the message body.
TRACE: The message body contains the request message as received by the server
HTTP Web 201 Created Successful responses
The request is complete, and a new resource is created .
HTTP Web 202 Accepted Successful responses
The request is accepted for processing, but the processing is not complete.
HTTP Web 203 Non-Authoritative Information Successful responses
The returned metainformation in the entity-header is not the definitive set as available from the origin server but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).
HTTP Web 204 No Content Successful responses
The server successfully processed the request and is not returning any content.
HTTP Web 205 Reset Content Successful responses
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
HTTP Web 206 Partial Content Successful responses
This response code is used because of range header sent by the client to separate download into multiple streams.
HTTP Web 207 Multi-Status Successful responses
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.
HTTP Web 208 Already Reported Successful responses
The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
HTTP Web 226 IM Used Successful responses
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
HTTP Web 300 Multiple Choice Redirection messages
The request has more than one possible response. The user-agent or user should choose one of them. There is no standardized way of choosing one of the responses.
HTTP Web 301 Moved Permanently Redirection messages
This response code means that the URI of the requested resource has been changed permanently. Probably, the new URI would be given in the response.
HTTP Web 302 Found Redirection messages
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
HTTP Web 303 See Other Redirection messages
The Response To The Request Can Be Found Under A Different Uri And Should Be Retrieved Using A Get Method On That Resource. This Method Exists Primarily To Allow The Output Of A Post-Activated Script To Redirect The User Agent To A Selected Resource. The New Uri Is Not A Substitute Reference For The Originally Requested Resource. The 303 Response Must Not Be Cached, But The Response To The Second (Redirected) Request Might Be Cacheable.
HTTP Web 304 Not Modified Redirection messages
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.
HTTP Web 303 See Other Redirection messages
The Response To The Request Can Be Found Under A Different Uri And Should Be Retrieved Using A Get Method On That Resource. This Method Exists Primarily To Allow The Output Of A Post-Activated Script To Redirect The User Agent To A Selected Resource. The New Uri Is Not A Substitute Reference For The Originally Requested Resource. The 303 Response Must Not Be Cached, But The Response To The Second (Redirected) Request Might Be Cacheable.
HTTP Web 304 Not Modified Redirection messages
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.
HTTP Web 305 Use Proxy Redirection messages
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 Firefoxand?Internet Explorer) Do Not Obey This Status Code.
HTTP Web 306 Unused Redirection messages
The 306 Status Code Was Used In A Previous Version Of The Specification, Is No Longer Used, And The Code Is Reserved.
HTTP Web 307 Temporary Redirect Redirection messages
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 302 Found Http Response Code, With The Exception That The User Agent Must Not Change The Http Method Used: If A Post Was Used In The First Request, A Post Must Be Used In The Second Request.
HTTP Web 308 Permanent Redirect Redirection messages
The Request And All Future Requests Should Be Repeated Using Another Uri. 307 And 308 Parallel The Behaviors Of 302 And 301, But Do Not Allow The Http Method To Change. So, For Example, Submitting A Form To A Permanently Redirected Resource May Continue Smoothly.
HTTP Web 400 Bad Request Client error responses
This response means that server could not understand the request due to invalid syntax.
HTTP Web 401 Unauthorized Client error responses
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
HTTP Web 402 Payment Required Client error responses
This response code is reserved for future use. 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.
HTTP Web 403 Forbidden Client error responses
The client does not have access rights to the content, i.e. they are unauthorized, so server is rejecting to give proper response. Unlike 401, the client's identity is known to the server.
HTTP Web 404 Not Found Client error responses
The server can not find 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 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurence on the web.
HTTP Web 405 Method Not Allowed Client error responses
The request method is known by the server but has been disabled and cannot be used. For example, an API may forbid DELETE-ing a resource. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code.
HTTP Web 406 Not Acceptable Client error responses
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
HTTP Web 407 Proxy Authentication Required Client error responses
This is similar to 401 but authentication is needed to be done by a proxy.
HTTP Web 408 Request Timeout Client error responses
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. 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.
HTTP Web 409 Conflict Client error responses
This response is sent when a request conflicts with the current state of the server.
HTTP Web 410 Gone Client error responses
This response would be sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to 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.
HTTP Web 411 Length Required Client error responses
Server rejected the request because the Content-Length header field is not defined and the server requires it.
HTTP Web 412 Precondition Failed Client error responses
The client has indicated preconditions in its headers which the server does not meet.
HTTP Web 413 Payload Too Large Client error responses
Request entity is larger than limits defined by server; the server might close the connection or return an Retry-After header field.
HTTP Web 414 URI Too Long Client error responses
The URI requested by the client is longer than the server is willing to interpret.
HTTP Web 415 Unsupported Media Type Client error responses
The media format of the requested data is not supported by the server, so the server is rejecting the request.
HTTP Web 416 Requested Range Not Satisfiable Client error responses
The range specified by the Range header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.
HTTP Web 417 Expectation Failed Client error responses
This response code means the expectation indicated by the Expect request header field can't be met by the server.
HTTP Web 418 I'm a teapot Client error responses
The server refuses the attempt to brew coffee with a teapot.
HTTP Web 421 Misdirected Request Client error responses
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.
HTTP Web 422 Unprocessable Entity Client error responses
The request was well-formed but was unable to be followed due to semantic errors.
HTTP Web 423 Locked Client error responses
The resource that is being accessed is locked.
HTTP Web 424 Failed Dependency Client error responses
The request failed due to failure of a previous request.
HTTP Web 425 Too Early Client error responses
Indicates that the server is unwilling to risk processing a request that might be replayed.
HTTP Web 426 Upgrade Required Client error responses
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 Upgrade header in a 426 response to indicate the required protocol(s).
HTTP Web 500 Internal Server Error Server error responses
The server has encountered a situation it doesn't know how to handle.
HTTP Web 501 Not Implemented Server error responses
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 GET and HEAD.
HTTP Web 502 Bad Gateway Server error responses
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.
HTTP Web 503 Service Unavailable Server error responses
The server is not ready to 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 responses should be used for temporary conditions and the Retry-After: 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.
HTTP Web 504 Gateway Timeout Server error responses
This error response is given when the server is acting as a gateway and cannot get a response in time.
HTTP Web 505 HTTP Version Not Supported Server error responses
The HTTP version used in the request is not supported by the server.
HTTP Web 506 Variant Also Negotiates Server error responses
The server has an internal configuration error: transparent content negotiation for the request results in a circular reference.
HTTP Web 507 Insufficient Storage Server error responses
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.
HTTP Web 508 Loop Detected Server error responses
The server detected an infinite loop while processing the request.
HTTP Web 510 Not Extended Server error responses
Further extensions to the request are required for the server to fulfill it.
HTTP Web 511 Network Authentication Required Server error responses
The 511 status code indicates that the client needs to authenticate to gain network access.