HTTP Response Codes
Every HTTP request sent to the server should generate a response code. There are literally dozens of possible response codes, but the tables below list the most common ones you're likely to encounter.
Response codes generally represent either success or failure of the requested action.
|200||OK||The request has succeeded. The information returned with the response is dependent on the method used in the request.|
|201||Created||The request has been fulfilled and resulted in a new resource being created.|
|204||No Content||The server has fulfilled the request but does not need to return an entity-body.|
|400||Bad Request||The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.|
|401||Unauthorized||The request requires user authentication.|
|403||Forbidden||The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.|
|404||Not Found||The server has not found anything matching the Request-URI.|
|409||Conflict||The request could not be completed due to a conflict with the current state of the resource.|
|500||Internal Server Error||The server encountered an unexpected condition which prevented it from fulfilling the request.|
|504||Gateway Timeout||The server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.|
|524||Timeout Error||This is a 100 sec timeout error. These errors are typically transient. If you continue to receive them on a regular basis or for a large period of time, contact our support team.|
For a comprehensive list of response codes, see the MDN Web Docs Page
Updated over 1 year ago