HTTP response freshness testing
Table of Contents
- Getting Started
- Known Issues
- Node.js 8 or higher is required.
npm i -s fresh
const fresh = default;
Check freshness of the response using request and response headers.
When the response is still "fresh" in the client's cache
false is returned to indicate that the client
cache is now stale and the full response should be sent.
When a client sends the
Cache-Control: no-cache request header to
indicate an end-to-end reload request, this module will return
to make handling these requests transparent.
This module is designed to only follow the HTTP specifications, not to work-around all kinda of client bugs (especially since this module typically does not receive enough information to understand what the client actually is).
There is a known issue that in certain versions of Safari, Safari will incorrectly make a request that allows this module to validate freshness of the resource even when Safari does not have a representation of the resource in the cache. The module jumanji can be used in an Express application to work-around this issue and also provides links to further reading on this Safari bug.
;;freshreqHeaders, resHeaders;// => false;;freshreqHeaders, resHeaders;// => true
Using with Node.js http server
npm run benchmarks
See the CHANGELOG.md file for details
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE file for details