You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, for GET request caching the Cache-Control max-age setting also controls s-maxage. This seems counterproductive considering the plugin is purging shared caches for us...theoretically. I guess there could be shared caches beyond our CDN of choice (WP Engine Cloudflare in my case).
max-age=604800, s-maxage=604800, must-revalidate
Ideally, I'd like to tell it to never purge my CDN of choice...or on a very long timeline...but make the browser max-age very short. The option to do stale-while-revalidate or stale-while-error (though this isn't well supported) would also be slick.
Lots of ideas here. I think separating s-maxage and max-age would be good to start.
Thoughts?
The text was updated successfully, but these errors were encountered:
Hey, for GET request caching the Cache-Control max-age setting also controls
s-maxage
. This seems counterproductive considering the plugin is purging shared caches for us...theoretically. I guess there could be shared caches beyond our CDN of choice (WP Engine Cloudflare in my case).max-age=604800, s-maxage=604800, must-revalidate
Ideally, I'd like to tell it to never purge my CDN of choice...or on a very long timeline...but make the browser max-age very short. The option to do
stale-while-revalidate
orstale-while-error
(though this isn't well supported) would also be slick.Lots of ideas here. I think separating
s-maxage
andmax-age
would be good to start.Thoughts?
The text was updated successfully, but these errors were encountered: