I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works. The list is just examples of different techniques, it's not for direct insertion. When i am trying to rebuild it with the same command, it's using the build.
(SO) Accessing the OAKS Supplier Module
It's generated at the end of the request and could be another source of unintended.
Ok, even if you aren't using express, what essentially needed is to set the nocache headers.
For security reasons we do not want certain pages in our application to be cached, eve. 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. Beware of etag even if you are using nocache, the etag header isn't removed, because it works in a different way.
