Technical
Caching Process

Technical Caching Process

On the first request to the asset (cache-miss event), depending on the config, SpeedSize™️ Edge CDN responds with either a 302 redirect to the original asset, or generates a temporary real-time asset.

On the first requests to transformations, depending on the config, SpeedSize™️ Edge CDN responds with one of the supported formats and/or bigger resolutions from the list of available files, if any, or a 302 redirect to the original asset, or generates a temporary real-time asset.

SpeedSize™️ updates the cache upon the progress of processing with a max-age step of 600 seconds (10 minutes). Once all the possible processing for the requested transformation is done, the response is cached with the biggest supported value of max-age of 31536000 seconds (1 year).

Requests are cached based on the supported formats and the required asset resolution evaluated from the Accept, User-Agent and Client-Hints request headers.

If SpeedSize™️’s infrastructure can’t reach the origin, SpeedSize™️’s Edge CDN will respond with a 302 redirect to the original asset with the max-age value growing with each consequent failed attempt.

Global Content Delivery Network

We deliver content to end users with lower latency. Amazon CloudFront uses a global network
of 400+ Points of Presence in 90+ cities across 47 countries to ensure the fastest delivery possible.

Map

Have any questions?

Contact us here

For quick answers, please visit our FAQ page