I found that Chrome responds better to Cache-Control: no-cache (100% conditional requests afterwards). "no-store" sometimes loaded from cache without even attempting a conditional request. Firefox responds better to "no-store" but still sometimes loads from cache if you reload immediately afterwords. What a mess!, The NOCACHE option specifies that the blocks retrieved for the table are placed at the least recently used end of the LRU list in the buffer cache when a FULL table scan is performed. This will cause the blocks read with a full table scan to be immediately flushed from the buffer cache., Middleware to disable client-side caching. Contribute to helmetjs/nocache development by creating an account on GitHub., The .nocache.js file contains JavaScript code that resolves the Deferred Binding configurations (such as browser detection, for instance) and then uses a lookup table generated by the GWT Compiler to locate one of the .cache.html files to use., Cache directive "no-cache" An explaination of the HTTP Cache-Control header The Cache-Control header is used to specify directives for caching mechanisms in both HTTP requests and responses. A typical header looks like this Cache-Control: public, max-age=10 public Indicates that the response may be cached by any cache. private, Alright, this is due to the pain that godaddy gives me by implementing their own caching in a MANAGED WORDPRESS hosting. I looked it up and as it turns out, their flush caching facility is not avai.