I'm adding the headers in a reusable middleware, otherwise you can set those. This is causing a problem to my login system (users not logged in can open old cached pages of logged in users). It was intended as a privacy measure:
I have build a docker image from a docker file using the below command. It tells browsers and caches that the response. Alright, this is due to the pain that godaddy gives me by implementing their own caching in a managed wordpress hosting.
When i am trying to rebuild it with the same command,. I looked it up and as it turns out, their flush. Ok, even if you aren't using express, what essentially needed is to set the nocache headers. 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.
The list is just examples of different techniques, it's not for direct insertion. By default, my browser caches webpages of my expressjs app.