Hi everyone, I have a question regarding the new "Async stale-while-revalidate" feature released today.
My setup uses a custom Cache Rule where I set Edge TTL to "Ignore cache-control header" (assigning a custom TTL).
Meanwhile, my origin server responds with very restrictive headers: Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate.
I know that normally the Cache Rule successfully overrides the origin headers and handles SWR directly on the edge. However, the changelog for the new Async SWR specifically mentions: "To use this feature, make sure your origin includes the stale-while-revalidate directive in the Cache-Control header."
My question is:
Will the new asynchronous background revalidation (which triggers exactly at expiry rather than waiting for a visitor) work automatically based on my Cache Rule settings alone? Or does the background process strictly require the stale-while-revalidate directive to be present in the actual origin's Cache-Control response to trigger properly?
Thanks in advance for the clarification!