A Proxy Caching plugin for Kong
A Proxy Caching plugin for Kong makes it fast and easy to configure caching of responses and serving of those cached responses in Redis. It caches responses bases on configurable response code and request headers with the request method.
This Kong plugin adds a non-standard X-Cache-Status header. There are several possible values for this header:
MISS: The resource was not found in cache, and the request was proxied upstream.HIT: The request was satisfied and served from cache.BYPASS: The request could not be satisfied from cache based on plugin settings.
Configure this plugin on a Service by making the following request:
$ curl -X POST http://kong:8001/services/debug-upstream/plugins \
--data "name=proxy-cache" \
--data "config.cache_ttl=300" \
--data "config.redis.host=127.0.0.1"- service: the id or name of the Service that this plugin configuration will target.
Here's a list of all the settings which can be used in this plugin:
Note: The required fields are in bold.
| Field | Default | Description |
|---|---|---|
| response_code | 200, 301, 302 | Upstream response status code considered cacheable |
| vary_headers | Relevant headers considered for the cache key | |
| vary_nginx_variables | Relevant nginx variables considered for the cache key | |
| cache_ttl | 300 | TTL, in seconds, of cache responses |
| cache_control | true | Respect the Cache-Control behaviors |
| redis.host | Host to use for Redis connection | |
| redis.port | 6379 | Port to use for Redis connection |
| redis.timeout | 2000 | Connection timeout to use for Redis connection |
| redis.password | Password to use for Redis connection | |
| redis.database | 0 | Database to use for Redis connection |
| redis.sentinel_master_name | Sentinel master name to use for Redis connection. Defining this value implies using Redis Sentinel | |
| redis.sentinel_role | Sentinel role to use for Redis connection | |
| redis.sentinel_addresses | Sentinel address to use for Redis connection | |
| redis.max_idle_timeout | 10000 | maximal idle timeout (in ms) for keep alive the Redis connection |
| redis.pool_size | 1000 | maximal pool size by Redis connection |
When the cache_control is enabled by settings, Kong will respect request and response Cache-Control headers as defined by RFC7234, with a few notes:
- The behavior of no-cache is simplified to exclude the entity from being cached entirely.
- Secondary key calculation via Vary is not yet supported.
$ luarocks install kong-plugin-proxy-cache$ sh -c "git clone https://github.com/globocom/kong-plugin-proxy-cache /tmp/kong-plugin-proxy-cache && cd /tmp/kong-plugin-proxy-cache && luarocks make *.rockspec"Please, read the contribute guide CONTRIBUTING.
kong-plugin-proxy-cache is MIT licensed.