I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works. It tells browsers and caches that the response contains. It was intended as a privacy measure:
What Salice Rose's Daring OnlyFans Photos Reveal About The Creator
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's generated at the end of the request and could be another source of unintended.
The ?nocache with time echo solved the issue. Beware of etag even if you are using nocache, the etag header isn't removed, because it works in a different way. For security reasons we do not want certain pages in our application to be cached, eve. Ok, even if you aren't using express, what essentially needed is to set the nocache headers.
