Our investigations have shown us that not all browsers respect the HTTP cache directives in a uniform manner. For security reasons we do not want certain pages in our application to be cached, eve. Are there any other good reasons to mark memory as non-cacheable? P.S. seems that marking memory as non-cacheable from user-space can be done through mmap () with MAP_NOCACHE flag, isn't it? UPD From wiki: Marking some memory ranges as non-cacheable can improve performance, by avoiding caching of memory regions that are rarely re-accessed. Use JS to append ?nocache (or better yet ?timestamp, where timestamp is the current Unix time, e.g. 1598155107) to the end of every linked URL (or &timestamp if the URL already contains a query string). This solution uses jQuery but you could adapt it to vanilla JS: no-store should not be necessary in normal situations, and in some cases can harm speed and usability. It was intended as a privacy measure: it tells browsers and caches that the response contains sensitive information that should never be written to a disk-based cache (or other non-volatile storage). How it works: Normally, even if a response is marked as no-cache by the server, a user agent. 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. Oracle recommends using the CACHE setting to enhance performance if you are using sequences in an Oracle Real Application Clusters environment. Using the CACHE and NOORDER options together results in the best performance for a sequence. CACHE option is used without the ORDER option, each instance. Here's the NoCache attribute proposed by mattytommo, simplified by using the information from Chris Moschini's answer: But I also read that this doesn't work in some versions of IE. Are there any set of meta tags that will turn off cache in all browsers? From fastapi official doc The --no-cache-dir option tells pip to not save the downloaded packages locally, as that is only if pip was going to be run again to install the same packages, but that's not the case when working with containers. Basically, there is no need to store whatever package cache you're installing locally since it is not required by docker containers. Ok, even if you aren't using express, what essentially needed is to set the nocache headers. I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works.