- 2.When using your server or storage as an origin to deliver images, the original copies of the images and files stay within your servers, and ImageKit.io does not control how long the files remain there. Imagekit.io maintains a copy of your original image within its internal caches and performs all the optimizations on this copy of the original.
- 3.The transformed and optimized copies of the images and files, when requested via a URL, are usually stored permanently. This not only improves the performance for repeat requests, but ensures the number of requests made to your origin server or storage is less. However, ImageKit.io might change this practice for a specific account or all accounts, if and when necessary.
This option allows caching based on the cache control headers being passed from your origin attached to ImageKit.io. For example, if your origin (server or storage) sends a cache-control header to cache a file for 1 hour, ImageKit.io applies the cache-control header across all its internal caches, generated transformations, and CDN. This ensures that the cache control set by you is obeyed at all times.
This feature can be applied for any URL endpoint in your ImageKit account.
Note: Origin-Based Cache Control is disabled by default. Reach out to ImageKit's support team to enable it for your account.
ImageKit.io caches a copy of every transformed and optimized image at the CDN. Additionally, ImageKit.io also maintains its internal caches, which are co-located with its processing engine across 6 global locations. In case any URL is missed by the CDN, internal caches deliver the resources without passing on the request to your server or storage. The same process is followed when you integrate ImageKit.io with a custom CDN.