Common Errors
Common Error Code
Code | HttpCode | Message |
---|---|---|
Success | ||
200 | This is the standard “OK” status code for a successful HTTP request. The response that is returned is dependent on the request. | |
Client Errors | ||
400 | The server cannot understand and process a request due to a client error. | |
401 | This status code request occurs when authentication is required but has failed or not been provided | |
403 | Very similar to status code 401, a status code 403 happens when a valid request was sent, but the server refuses to accept it. This happens if a client/user requires the necessary permission or they may need an account to access the resource. Unlike a status code 401, authentication will not apply here. | |
404 | The most common status code the average user will see. A status code 404 occurs when the request is valid, but the resource cannot be found on the server. Even though these are grouped in the Client Errors “bucket,” they are often due to improper URL redirection. | |
429 | The HTTP 429 Too Many Requests client error response status code indicates the client has sent too many requests in a given amount of time. This mechanism of asking the client to slow down the rate of requests is commonly called "rate limiting" | |
Server Errors | ||
500 | Another one of the more commonly seen status codes by users, the 500 series codes are similar to the 400 series codes in that they are true error codes. The status code 500 happens when the server cannot fulfill a request due to an unexpected issue. Web developers typically have to comb through the server logs to determine where the exact issue is coming from. | |
502 | The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
Modified at 2025-04-26 03:14:49