Capturing 404 and 500 pages

Several things could go wrong when we visit a webpage to capture it, which may hinder obtaining a successful screenshot. The most common are 404 and 500 HTTP errors. When such errors occur, we make three attempts to capture the webpage again before giving up. Depending on the nature of the error, it may or may not be charged to your account.

404 Error

That is a result of accessing a nonexistent webpage (broken/dead link) and is usually when a customer provides an old URL to a resource that is no longer on the destination web server, a malformed URL. An example is providing a nonexistent webpage like "https://www.amazon.com/some-random-gibberish-page" and a malformed URL like "https https://www.amazon.com".

Screenshot is charged

When our engine visits such a webpage, and the server returns a custom '404 error page', that screenshot will be charged to your account.

Screenshot is not charged

When we do not receive any response from that server, no charges are incurred for this on your account, and we usually indicate this with a 404 thumbnail on the screenshot listing page for that webpage on your dashboard. 

500 Error

That is usually when the destination web server fails to process the request due to internal errors hence, returns the error message or no message at all. An example is when a webpage is overwhelmed by too many requests, and the service gets slow or completely unavailable to respond to further incoming requests. 

Screenshot is charged

When our engine visits a webpage and eventually, a custom '500 error page' is returned by the server, that screenshot will be charged to your account.

Screenshot is not charged

When we do not receive any response from the server, no charges are incurred for this on your account. Unlike the 404 error, no thumbnail will be displayed for this.