Cloudfront support for stale-while-revalidate

+1 this is a pretty standard feature on most cdns just not cloudfront, so need to know if I need to be looking at alternative providers.

+1. I would also very much like this feature, to be able to support Incremental Static Regeneration for our NextJS app. I can also imagine that this is really helpful for the AWS Amplify product since that also supports NextJS and I would therefor think they can use this functionality to support ISR on NextJS as well. tf-next (a zero config terraform module for hosting NextJS apps in AWS) also has GitHub issue related to this.

Overall, this functionality would be really helpful!

+1 I've been waiting for over 4 years for this to be supported. For my purposes, it's the feature that that cloudfront is missing that makes fastly a better option for many of my applications. Cloudfront team, please support this header!!

+1 this is a pretty standard feature...

+1 this is absolutely required to make it feasible to deploy your NextJS site on AWS behind CloudFront as opposed to on Vercel or Netlify or other competitors.

Hey, this really should be added as a feature. Has this been seen at any level of AWS yet?

Looks like CloudFront finally started supporting stale-while-revalidate=N some time in April 2023, without any announcement or documentation update. Testing shows that – at least in its current implementation as of Apr 2023 – they don't actually follow the RFC recommendation of not blocking during the revalidation: If, upon expiry of the object, the origin takes 2 seconds to respond with a 502, then the client will also have to wait for 2 seconds while CloudFront completes the origin request. Only after that period will CloudFront serve the stale object.