Match a ``urllib3.response.HTTPResponse``.

An interface to see if request should cached or not.

Match a Request.

Small wrapper around a fp object which will tee everything read into a buffer, and when that file is closed it will execute a callback with t

If there is no Expires header already, fall back on Last-Modified using the heuristic from http://tools.ietf.org/html/rfc7234#section-4.2

Cache **all** requests for a defined time period.

Traditional FileCache: body is stored in memory, so not suitable for large downloads.

Cache the response by providing an expires 1 day in the future.

Memory-efficient FileCache: body is stored in a separate file, reducing peak memory usage.

In this variant, the body is not stored mixed in with the metadata, but is passed in (as a bytes-like object) in a separate call to ``set_bod

Test our use of ETags when the response is stale and the response has an ETag.

Test our equal priority caching with ETags Equal Priority Caching is a term I've defined to describe when ETags are cached orthgonally from T

Tests for ``FileCache``.

On 304s we still make a request using our connection pool, yet we do not call the parent adapter, which releases the connection back to t

Tests for ``SeparateBodyFileCache``

Shared implementation for both FileCache variants.