Redis backend bypasses cache for resources lacking Vary headers

[cefn]

There's an issue with the ordering and truthy logic of !buffer at https://github.com/gitterHQ/request-http-cache/blob/master/lib/redis-backend.js#L19 in the Redis backend.

The result is that an empty string stored as a Vary header can never be retrieved, and given no Vary header coming back from the backend, the resource is then interpreted as having no cache, even when a cache is in fact stored in Redis at the proper location.

The empty-string has special meaning for request-http-cache - that there were no Vary headers when the resource was originally cached. Unfortunately that means that any resources not serving a Vary header can never be successfully retrieved from cache.

[lalkhum]

@suprememoocow Will this be approved in the near future or is this completely stopped from maintenance? Can you let us know please?