From 9cda4e0db66391a5df5844ef3e3e409b1c6f6193 Mon Sep 17 00:00:00 2001 From: Kevin Whitley Date: Mon, 29 Aug 2016 12:28:35 -0500 Subject: [PATCH] README bump with contributors --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index 0999186..47c272b 100644 --- a/README.md +++ b/README.md @@ -125,3 +125,18 @@ The presence of this header flag will bypass the cache, ensuring you aren't look - `apicache` is currently an in-memory cache, built upon [memory-cache](https://github.com/ptarjan/node-cache). It may later be expanded to allow other cache-layers. - This should only be used for JSON responses (as from an API) - if for no other reason, because it will return the cached response as `application/json`. There's a reason it's called `apicache`. +## Contributors + +Special thanks to all those that use this library and report issues, but especially to the following active users that have helped add to the core functionality! + +- @rutgernation - JSONP support +- @Amhri - bugfix headers (with redis) +- @enricsangra - added x-apicache-force-fetch header +- @tskillian - custom appendKey path support +- @agolden - Content-Encoding preservation (for gzip, etc) +- @davidyang - express 4+ compatibility +- @gesposito - README update +- @Webcascade - bugfix in cache groups (during debug) +- @nmors - redis support + +