3.5.0

What's New?

maxAgeSeconds and Fresh Responses

The 3.5.0 release brings with it a small change to how responses are retrieved from caches that have age-based expiration enabled, i.e. those that use the maxAgeSeconds parameter.

Previously, a response in such a cache would be considered valid, even if the resource was added to the cache longer than maxAgeSeconds seconds ago.

As of 3.5.0, the Date header of the cached response will be checked prior to it being used. If the Date header is present, and if the value corresponds to an time in the past more than maxAgeSeconds, then the response will not be considered valid, and the fallback behavior (usually, retrieving a new response from the network) will be used. If the Date header is not present, or if the response is determined to be "fresh" based on its age, the cached response will be used to satisfy the request.

Documentation & README Fixes

This release also includes a number of documentation-related fixes.

PRs Since Previous Release

• Enhance the README.
• Fix link typo in README
• Explicitly check the Date: header of a cached response when maxAge is set
• Test fixes
• Update link in comment

Thanks

Thanks to @corburn and @DavidScales for their contributions!