The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, too large size, invalid request message framing, or deceptive request routing).
Use this when the access is tied to the application logic, such as insufficient rights to a resource
Use this when the client already has the most recent version of a resource. For example, when calling get-next-event, if there are no events within the timeout period, the server will return a 304 to indicate that there are no events.
The server successfully processed the request and is not returning any content.
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.
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.
This error code means that the URL is too long for the server to process
Generated using TypeDoc
Enum for http response status codes