It's generated at the end of the request and could be another source of unintended. I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works. If your class or action didn't have nocache when it was rendered in your browser and you want to check it's working, remember that after compiling the changes you need to do a hard.
“He Was Never Supposed To Say This”—Mark Zuckerberg’s Private Audio
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.
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.
