[ad_1]
It’s come to our notice that when setting the plugin to bypass certain types of pages such as is_archive, a no-store is set for the Cache-Control header in addition to no-cache and max-age=0, a setup that prevents the pages in question being stored in browsers’ back/forward cache.
I wonder if you see any drawbacks for the plugin to not use no-store in this case in the light of the web.dev piece linked to above?