Caches the response, stripping any headers marked as "not-cacheable".
Allows the cache to calculate the freshness lifetime of the request using a heuristic.
Allows the cache to calculate the freshness lifetime of the request using a heuristic.
https://tools.ietf.org/html/rfc7234#section-4.2.2
Returns true if the selecting header fields nominated by the stored response match those presented by the new request.
Returns true if the selecting header fields nominated by the stored response match those presented by the new request. This method is broken out into the cache functionality as section 4.1 can do transformation of header fields in non-trivial ways that cannot be anticipated by this library in order to find a match. Given the vagaries of Vary and the overall complexities of fields such as User-Agent, the assumption is that the cache knows best.
the presented headers by the new request.
the header fields nominated by the stored response
true if the cache considers it a match, false otherwise.
https://tools.ietf.org/html/rfc7234#section-4.1
Generates a response for the HTTP response with the appropriate headers.
Invalidates the key.
Returns true if the cache knows what to do with this cache extension, false otherwise.
Returns true if the cache knows what to do with this cache extension, false otherwise.
Defines cacheable methods.
Defines cacheable methods.
Returns true if the response code is cacheable by default.
Returns true if the response code is cacheable by default.
Cache is not shared.
Cache is not shared.
Cache understands the response status code behavior for caching purposes.
Cache understands the response status code behavior for caching purposes.
Strips headers using a strip headers cache-control calculator.
Strips headers using a strip headers cache-control calculator.
Central HTTP cache. This keeps a cache of HTTP responses according to https://tools.ietf.org/html/rfc7234#section-2
The primary cache key consists of the request method and target URI. However, since HTTP caches in common use today are typically limited to caching responses to GET, many caches simply decline other methods and use only the URI as the primary cache key.