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. I noticed some caching issues with service calls when repeating the same service call (long polling). 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. If you omit both cache and nocache, then the database caches 20 sequence numbers by default. One solution is to pass a timestamp to ensure ie thinks it's a different.
The ?nocache with time echo solved the issue. I have read that to avoid caching in node.js, it is necessary to use: Spent days trying to get chromium based app to stop caching images. It tells browsers and caches that the response contains.
It was intended as a privacy measure: