We're excited to announce an improvement to the ignoreOriginCacheControl configuration option, giving you even more control over cache behavior customization!

Previously, when this option was set to false, it mainly prevented the deletion of the cache control received from your origin. However, it would still be overridden by the rules applied based on your results.

Now, setting this option to false treats the cache-control header from your origin as an additional cache rule. The system first calculates the cache-control from your stellate-config and then compares it to the cache-control header received from your origin. If your cache-control permits a shared cache, we consider the s-maxage, max-age, and stale-while-revalidate directives and choose the lowest value to optimize caching.

Furthermore, when non-cacheable directives like private, no-store, or no-cache are encountered, we will set the max-age to 0 and treat it as a cache pass.

Rest assured, if you have an undefined or truthy setting, there will be no changes.

This enhancement allows you to overwrite the cache-control header correctly, providing greater flexibility in customizing cache behavior. We hope you find this update helpful!