The list is just examples of different techniques, it's not for direct insertion They both are meant to prevent the client from caching the response It was intended as a privacy measure
For security reasons we do not want certain pages in our application to be cached, eve. App.set the first is disabling it using express builtin app.set('etag', false) Without a field name, the directive applies to the entire request and a shared (proxy server) cache must force a successful revalidation with the origin web server before satisfying the request
The rest of the response may be supplied from. Basically, there is no need to store whatever package cache you're installing locally since it is not required by docker containers. Ok, even if you aren't using express, what essentially needed is to set the nocache headers I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works.
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
