HTTP Error Codes and REST APIs

HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:

1. Informational responses (100–199)
2. Successful responses (200–299)
3. Redirects (300–399)
4. Client errors (400–499)
5. Server errors (500–599)

If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server's software.

Ref: developer.mozilla.org

All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role. There are five classes defined by the standard:

1xx informational response – the request was received, continuing process
2xx successful – the request was successfully received, understood, and accepted
3xx redirection – further action needs to be taken in order to complete the request
4xx client error – the request contains bad syntax or cannot be fulfilled
5xx server error – the server failed to fulfil an apparently valid request

Ref: en.wikipedia.org

Some common error codes one must know:

401 Unauthorized
    Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

403 Forbidden
    The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server.

405 Method Not Allowed
    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.

415 Unsupported Media Type
    The media format of the requested data is not supported by the server, so the server is rejecting the request.

RESTful API Response Codes (used by Amazon Drive API)

The HTTP Status Codes used by the RESTful Amazon Drive API.

HTTP Status Code  ---  Description

200 OK  ---  Successful.

201 Created  ---  Created.
Status code '201' is important for REST APIs that are performing some action such as raising a ticket or logging something.

400 Bad Request  ---  Bad input parameter. Error message should indicate which one and why.

401 Unauthorized  ---  The client passed in the invalid Auth token. Client should refresh the token and then try again.

403 Forbidden  ---  * Customer doesn’t exist. * Application not registered. * Application try to access to properties not belong to an App. * Application try to trash/purge root node. * Application try to update contentProperties. * Operation is blocked (for third-party apps). * Customer account over quota.

404 Not Found  ---  Resource not found.

405 Method Not Allowed  ---  The resource doesn't support the specified HTTP verb.

409 Conflict  ---  Conflict.

411 Length Required  ---  The Content-Length header was not specified.

412 Precondition Failed  ---  Precondition failed.

429 Too Many Requests  ---  Too many request for rate limiting.

500 Internal Server Error  ---  Servers are not working as expected. The request is probably valid but needs to be requested again later.

503 Service Unavailable  ---  Service Unavailable.

Ref: developer.amazon.com (Dated: 24 Feb 2021)

Additional Notes

In Europe, the NotFound project, created by multiple European organizations including Missing Children Europe and Child Focus, encourages site operators to add a snippet of code to serve customized 404 error pages which provide data about missing children.

Ref: HTTP 404

Tags: Technology,Web Development,Web Scraping,