It was intended as a privacy measure: It's generated at the end of the request and could be another source of unintended. For security reasons we do not want certain pages in our application to be cached, eve.
5 '80s references in 'Stranger Things' you probably missed
I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works.
Without a field name, the directive applies to the entire request and a shared (proxy server) cache must force a successful.
The ?nocache with time echo solved the issue. The list is just examples of different techniques, it's not for direct insertion. 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. It tells browsers and caches that the response contains.
Ok, even if you aren't using express, what essentially needed is to set the nocache headers.
