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, 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!, minimize caching effects. Contribute to Feh/nocache development by creating an account on GitHub., Surfing the internet can, at times be frustrating because the latest version of the website fails to load and you may see an outdated page. Disable cache to solve this issue., 95 I don't find get the practical difference between Cache-Control:no-store and Cache-Control:no-cache. As far as I know, no-store means that no cache device is allowed to cache that response. In the other hand, no-cache means that no cache device is allowed to serve a cached response without validate it first with the source., HTTP is designed to cache as much as possible, so even if no Cache-Control is given, responses will get stored and reused if certain conditions are met. This is called heuristic caching..