I don't really get why to use "no-store" even. You can use "no-cache" and it will have forced revalidation on each request returning 304 most of the time if your index.html was not changed.
It also applies to any static files that doesn't have a "hashed" names for various reasons.
I agree, no need to use no-store here as long as your server implements validation via etag or last-modified. Dev.to, for example, sets the following headers:
I don't really get why to use "no-store" even. You can use "no-cache" and it will have forced revalidation on each request returning 304 most of the time if your index.html was not changed.
It also applies to any static files that doesn't have a "hashed" names for various reasons.
I agree, no need to use
no-storehere as long as your server implements validation viaetagorlast-modified. Dev.to, for example, sets the following headers: