Algorithm for caching requests. This assumes a requests Response object.

Store the data in the cache.

Return a cached response if it exists in the cache, otherwise return False.

Load a cached response, or return None if it's not available.

On a 304 we will get a new set of headers that we want to update our cached value with, assuming we have one. This should only ever b

Safely write the data to the given path.

Plain random http data generator:

If the local cache has the given URL ``update_cached_response()`` will: 1. Load the body from the cache. 2. Update the store

Normalize the URL to create a safe key for the cache

Build a response by making a request or using the cache. This will end up calling send and returning a potentially cached re

Helper for clearing all the keys in a database. Use with caution!

Redis uses connection pooling, no need to close the connection.

Return the body as file-like object.

Parses a URI using the regex given in Appendix B of RFC 3986. (scheme, authority, path, query, fragment) = parse_uri(uri)

Verify our vary headers match and construct a real urllib3 HTTPResponse object.

Update the response headers with any new headers. NOTE: This SHOULD always include some Warning header to signify that the resp

Return a valid 1xx warning header value describing the cache adjustments. The response is provided too allow warnings like 1

A request with no hints as to whether it should be cached. Yet, we might still choose to cache it via a heuristic.

Send a request. Use the request information to see if it exists in the cache and cache the response if we need to and can.