Merge pull request #2 from jkyberneees/support-multiple-expire-patterns

Support multiple expire patterns

Author: jkyberneees

README.md

@@ -94,6 +94,12 @@ service.patch('/numbers', (req, res) => {
 })
 ```
 
+#### Invalidating multiple patterns
+Sometimes is required to expire cache entries using multiple patterns, that is also possible using the `,` separator:
+```js
+res.setHeader('x-cache-expire', '*/pattern1,*/pattern2')
+```
+
 ### Custom cache keys
 Cache keys are generated using: `req.method + req.url`, however, for indexing/segmenting requirements it makes sense to allow cache keys extensions.  
 

index.js

@@ -50,9 +50,13 @@ const middleware = (opts) => async (req, res, next) => {
   onEnd(res, (payload) => {
     if (payload.headers[X_CACHE_EXPIRE]) {
       // support service level expiration
-      const keysPattern = payload.headers[X_CACHE_EXPIRE]
+      const keysPattern = payload.headers[X_CACHE_EXPIRE].replace(/\s/g, '')
+      const patterns = keysPattern.split(',')
       // delete keys on all cache tiers
-      opts.stores.forEach(cache => getKeys(cache, keysPattern).then(keys => mcache.del(keys)))
+      patterns.forEach(pattern =>
+        opts.stores.forEach(cache =>
+          getKeys(cache, pattern).then(keys =>
+            mcache.del(keys))))
     } else if (payload.headers[X_CACHE_TIMEOUT]) {
       // we need to cache response
       mcache.set(req.cacheKey, JSON.stringify(payload), {

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "http-cache-middleware",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "description": "HTTP Cache Middleware",
   "main": "index.js",
   "scripts": {