We are planning to deploy an edge cache change on June 24th, which will affect customers who are using no-cache and no-store directives of the Cache-Control header. We currently ignore those directives and cache the response with a default TTL. We will start honoring the mentioned directives, which means that responses sending no-store or no-cache will become uncacheable, decreasing the cache HIT ratio, which could impact site performance. If you use those directives but don’t expect those requests to be uncacheable, please modify the code sending these directives in the Cache-Control header.
These changes won’t affect customers who are using no-store or no-cache in combination with other directives that make the response uncacheable, such as max-age=0 or private.
Existing limitations for Cache-Control still apply, as mentioned in our docs.
If you have any questions related to this upcoming change, please open a support ticket and we will be happy to assist.