A Fastify plugin to facilitate working with cache headers
Switch branches/tags
Nothing to show
Clone or download
Latest commit dae341f Nov 28, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
test Update deps, minor fixes Nov 18, 2018
.editorconfig Initial commit Sep 24, 2017
.gitignore update ignore Nov 18, 2018
.travis.yml Update deps, minor fixes Nov 18, 2018
LICENSE Update LICENSE Nov 27, 2018
Readme.md Update for fastify v2 Nov 27, 2018
package.json 4.0.0 Nov 28, 2018
plugin.js Update for fastify v2 Nov 27, 2018

Readme.md

fastify-caching

Greenkeeper badge Build Status

fastify-caching is a plugin for the Fastify framework that provides mechanisms for manipulating HTTP cache headers according to RFC 2616 §14.9.

Supports Fastify versions ^2.0.0.

This plugin fully supports Fastify's encapsulation. Therefore, routes that should have differing cache settings should be registered within different contexts.

In addition to providing header manipulation, the plugin also decorates the server instance with an object that can be used for caching items. Note: the default cache should not be used in a "production" environment. It is an LRU, in-memory cache that is capped at 100,000 items. It is highly recommended that a full featured cache object be supplied, e.g. abstract-cache-redis.

Example

This example shows using the plugin to disable client side caching of all routes.

const http = require('http')
const fastify = require('fastify')
const fastifyCaching = require('fastify-caching')

fastify.register(
  fastifyCaching,
  {privacy: fastifyCaching.privacy.NOCACHE},
  (err) => { if (err) throw err }
)

fastify.get('/', (req, reply) => {
  reply.send({hello: 'world'})
})

fastify.listen(3000, (err) => {
  if (err) throw err

  http.get('http://127.0.0.1:3000/', (res) => {
    console.log(res.headers['cache-control'])
  })
})

This example shows how to register the plugin such that it only provides a server-local cache. It will not set any cache control headers on responses. It also shows how to retain a reference to the cache object so that it can be re-used.

const redis = require('ioredis')({host: '127.0.0.1'})
const abcache = require('abstract-cache')({
  useAwait: false,
  driver: {
    name: 'abstract-cache-redis', // must be installed via `npm install`
    options: {client: redis}
  }
})

const fastify = require('fastify')()
fastify
  .register(require('fastify-redis'), {client: redis})
  .register(require('fastify-caching'), {cache: abcache})

fastify.get('/', (req, reply) => {
  fastify.cache.set('hello', {hello: 'world'}, 10000, (err) => {
    if (err) return reply.send(err)
    reply.send({hello: 'world'})
  })
})

fastify.listen(3000, (err) => {
  if (err) throw err
})

API

Options

fastify-caching accepts the options object:

{
  privacy: 'value',
  expiresIn: 300,
  cache: {get, set},
  cacheSegment: 'segment-name'
}
  • privacy (Default: undefined): can be set to any string that is valid for a cache-response-directive as defined by RFC 2616.
  • expiresIn (Default: undefined): a value, in seconds, for the max-age the resource may be cached. When this is set, and privacy is not set to no-cache, then ', max-age=<value>' will be appended to the cache-control header.
  • cache (Default: abstract-cache.memclient): an abstract-cache protocol compliant cache object. Note: the plugin requires a cache instance to properly support the ETag mechanism. Therefore, if a falsy value is supplied the default will be used.
  • cacheSegment (Default: 'fastify-caching'): segment identifier to use when communicating with the cache.

reply.etag(string, number)

This method allows setting of the etag header. It accepts any arbitrary string. Be sure to supply a string that is valid for HTTP headers.

If a tag string is not supplied then uid-safe will be used to generate a tag. This operation will be performed synchronously. It is recommended to always supply a value to this method to avoid this operation.

All incoming requests to paths affected by this plugin will be inspected for the if-none-match header. If the header is present, the value will be used to lookup the tag within the cache associated with this plugin. If the tag is found, then the response will be ended with a 304 status code sent to the client.

Tags will be cached according to the second parameter. If the second parameter is supplied, and it is an integer, then it will be used as the time to cache the etag for generating 304 responses. The time must be specified in milliseconds. The default lifetime, when the parameter is not specified, is 3600000.

reply.expires(date)

This method allows setting of the expires header. It accepts a regular Date object, or a string that is a valid date string according to RFC 2616 §14.21.

License

MIT License