Alright, this is due to the pain that godaddy gives me by implementing their own caching in a managed wordpress hosting. I have build a docker image from a docker file using the below command. I looked it up and as it turns out, their flush caching facility is not avai.
The list is just examples of different techniques, it's not for direct insertion. Until you do so, your browser will keep the old cached version, and won't refresh it with a normal refresh (f5). I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works.
It was intended as a privacy measure: 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. 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 refresh (ctrl+f5) in your browser.
Edited jul 9, 2015 at 8:48 donnelle.