express-cache-response-directive

Middleware for ExpressJS that defines a cacheControl method to set Cache-Control headers.

This middleware doesn't define legacy Expires headers. For compatibility with old HTTP/1.0 agents combine it with express-legacy-expires.

Install

1$ npm install express-cache-response-directive

Usage

1var cacheResponseDirective = require('express-cache-response-directive');

1app.use(cacheResponseDirective());

1app.get('/', function(req, res, next) {
2	res.cacheControl({maxAge: 300});
3	// ...
4});

res.cacheControl([pattern], [options])

The method added by the middleware accepts an optional string pattern and an object of Cache-Control options. Both are optional but at least one of them should be specified.

See the HTTP/1.1 Standard's Cache-Control sections for information on the usage of Cache-Control directives.

Patterns

String patterns are defined for simple directives so you can simply write res.cacheControl("public"); instead of having to always write res.cacheControl({'public': true});. Patterns can be combined with options res.cacheControl("public", {mustRevalidate: true});.

"public"

1res.cacheControl("public");
2// Cache-Control: public

"private"

1res.cacheControl("private");
2// Cache-Control: private

"no-cache"

1res.cacheControl("no-cache");
2// Cache-Control: no-cache

"no-store"

1res.cacheControl("no-store");
2// Cache-Control: no-cache, no-store

Options

Each Cache-Control response directive defined in HTTP/1.1 has an option that can be defined.

• Options for directives that use a delta time accept a number as a value.
  • Time values may also be expressed as strings like "3 min", "1h", "5 days".
• Options that optionally accept field names accept true for the normal non-field directive and for the with field-name directive accept either a string or an array of strings for the field names.
• The remaining directives that don't have a value simply accept a truthy value.

The public, private, no-cache, and no-store directives are exclusive only one may be specified. With the exception that no-cache and no-store may be defined together.

public:

1res.cacheControl({'public': true});
2// Cache-Control: public

private:

1res.cacheControl({'private': true});
2// Cache-Control: private

1res.cacheControl({'private': "X-Private"});
2// Cache-Control: private="X-Private"

1res.cacheControl({'private': ["X-Private-1", "X-Private-2"]});
2// Cache-Control: private="X-Private-1, X-Private-2"

no-cache:

1res.cacheControl({'no-cache': true});
2res.cacheControl({noCache: true});
3// Cache-Control: no-cache

1res.cacheControl({noCache: "X-Uncached"});
2// Cache-Control: no-cache="X-Uncached"

1res.cacheControl({noCache: ["X-Uncached-1", "X-Uncached-2"]});
2// Cache-Control: no-cache="X-Uncached-1, X-Uncached-2"

no-store:

1res.cacheControl({'no-store': true});
2res.cacheControl({noStore: true});
3// Cache-Control: no-cache, no-store

• no-store also implies no-cache because some browsers have begun treating no-cache the same way they treat no-store.

max-age:

1res.cacheControl({'max-age': 300});
2res.cacheControl({maxAge: 300});
3res.cacheControl({maxAge: "5min"});
4// Cache-Control: public, max-age=300

• max-age implies public if none of private, no-cache, or no-store is defined, so you can define it alone.

s-maxage:

1res.cacheControl({'s-maxage': 300});
2res.cacheControl({sMaxage: 300});
3res.cacheControl({sMaxAge: 300});
4// Cache-Control: public, s-maxage=300

• s-maxage supports sMaxAge in addition to the standard camel-case conversion sMaxage due to the potential confusion of the max-age to maxAge conversion.

must-revalidate:

1res.cacheControl({'must-revalidate': true});
2res.cacheControl({mustRevalidate: true});
3// Cache-Control: must-revalidate

proxy-revalidate:

1res.cacheControl({'proxy-revalidate': true});
2res.cacheControl({proxyRevalidate: true});
3// Cache-Control: proxy-revalidate

no-transform:

1res.cacheControl({noTransform: true});
2res.cacheControl({'no-transform': true});
3// Cache-Control: no-transform

License

MIT