AmpliFund uses HTTP response status codes for some of our error messages.
|This interim response indicates that the client should continue the request or ignore the response if the request is already finished.
|This code indicates that the server has received and is processing the request, but no response is available yet.
|The server cannot or will not process the request due to something that is perceived to be a client error.
|The client must authenticate to get the requested response.
|The client does not have access rights to the content.
|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.
|Method Not Allowed
|The request method is known by the server but is not supported by the target resource. For example, an API may not allow calling
DELETE to remove a resource.
|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.
|This response is sent when a request conflicts with the current state of the server.
|Too Many Requests
|The user has sent too many requests in a given amount of time ("rate limiting").
|Internal Server Error
|The server has encountered a situation it does not know how to handle.
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 to handle the request. Common causes are a server that is down for maintenance or that is overloaded.
|This error response is given when the server is acting as a gateway and cannot get a response in time.