Revealing and arranging image delivery issues

If you have a modern website or mobile application, there is no doubt that you are managing a lot of media resources, especially images. But the delivery of these images can be a challenge. You may not know if there are broken images on your website, or if URLs indicate users on non-existent images, resulting in HTTP status errors. Worse still, search engines like Google may have indexed the URLs of images that have been deleted or changed, resulting in even more errors when users try to access them.

So how do you discover and identify these errors when you do not have clear visibility on your system and analytics tools like Google Analytics can not help you find them? A good way is to use an image management solution that offers image delivery error reports. When you are looking for a solution to help solve this problem, you will want to make sure that it offers a centralized management console from which you can quickly and easily view detailed error reports.

                            Any problem involving the correct construction of image URLs … can be                                     identified, debugged and repaired before users notice it.

An error report should list all resource delivery errors for the current (default) date, as well as the number of errors by the type of error encountered. Another useful feature is the graphic capabilities, which can indicate the frequency of each type of error over a given period of time. Search capabilities are also useful, which allows you to recover the total number of errors for a specific date.

Among the types of errors you can find:

• 400 Incorrect query: The server can not process the query because of something that is perceived as a request error. The cause could be malformed query syntax or invalid image transformation parameters.
• 401 Unauthorized: Authentication is required and has failed or was not provided. For example, the URL must be signed when using add-ons or for some transformations in Strict Transformations mode, or the image type has been restricted in the security settings of your account.
• 404 not found: The requested resource could not be found, which means that the public identifier is invalid.
• 408 request period: the server has expired pending the request. This could be the result of a network error or a slow client.
• Tariff 420 limited: there may be too many simultaneous requests for images, or the quota difficult for additional use for your account has been exceeded.
• 200 images returned in error: a default image placeholder was delivered when the requested image was not found.

When viewing an error report, you should be able to select one of these error categories, then see the list of errors encountered in this category and the details associated with this error, such as the reason for the error, the URL Of the request The image and the reference website (which asks for the resource).

The information contained in the error reports should be useful to indicate the problems associated with the delivery of the image and displayed in near real time. In addition to the usefulness of the report on identifying and resolving issues related to the delivery of resources on an ongoing basis, an error report can help you when you implement an image management solution, and when you launch Your site or your application in production or update it. Any problem involving the correct construction of image URLs, or in case of accidental breakage of image deliveries, can be identified, debugged and corrected before users notice it.

With an error reporting feature, you will be able to get a lot of useful information about your delivery of images and videos and analyze the problems related to the broadcast of your media. The report allows you to quickly locate problems, debug and analyze problems, and then repair them.