But what I would like to do is to apply ?nocache=1 to every URL related to the site (including the assets like style.css) so that I get the non cached version of the files.
regex - Adding ?nocache=1 to every url (including the assets like ...
@Anshul No, must-revalidate and no-cache have different meaning for fresh responses: If a cached response is fresh (i.e, the response hasn't expired), must-revalidate will make the proxy serve it right away without revalidating with the server, whereas with no-cache the proxy must revalidate the cached response regardless of freshness. Source: "HTTP - The Definitive Guide", pages 182-183.
To ensure that your build is completely rebuilt, including checking the base image for updates, use the following options when building: --no-cache - This will force rebuilding of layers already available --pull - This will trigger a pull of the base image referenced using FROM ensuring you got the latest version. The full command will therefore look like this: docker build --pull --no-cache ...
Our investigations have shown us that not all browsers respect the HTTP cache directives in a uniform manner. For security reasons we do not want certain pages in our application to be cached, eve...
Beware of ETag Even if you are using nocache, the ETag header isn't removed, because it works in a different way. It's generated at the end of the request and could be another source of unintended caching. In order to handle it you have two choices. app.set The first is disabling it using express builtin app.set('etag', false); method. on-headers The second is removing the header just before ...