minimize caching effects. Contribute to Feh/nocache development by creating an account on GitHub., This is an artifact of HTTP/1.0, as many implementations did not support the no-cache directive. max-stale. The max-stale directive is used by a client to indicate that they will accept stale HTTP responses up to a certain number of seconds. This differs from max-age, as max-stale begins once the max-age expires. Cache-Control: max-stale=, By adding Cache-Control: no-cache to the response along with Last-Modified and ETag — as shown below — the client will receive a 200 OK response if the requested resource has been updated, or will otherwise receive a 304 Not Modified response if the requested resource has not been updated. http. HTTP/1.1 200 OK Content-Type: text/html , 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 Indicates that the response is intended for a single user and must not be stored by a shared cache., Middleware to destroy caching. Latest version: 4.0.0, last published: 6 months ago. Start using nocache in your project by running `npm i nocache`. There are 409 other projects in the npm registry using nocache., `nocache` tries to minimize the effect an application has on the Linux file system cache. Use case: backup processes that should not interfere with the present state of the cache. Also this package provides the following utilities: * `cachedel`.