A caching middleware that follows HTTP caching rules, thanks to http-cache-semantics. By default, it uses cacache as the backend cache manager.
Likely you won't! At least not directly. Unless you are looking to implement a custom backend cache manager or client middleware you'll probably want to pull in one of the existing client implementations instead. See the Provided Client Implementations section below.
1.67.1
With cargo add installed :
cargo add http-cache
The following features are available. By default manager-cacache
and cacache-async-std
are enabled.
manager-cacache
(default): enable cacache, a high-performance disk cache, backend manager.cacache-async-std
(default): enable async-std runtime support for cacache.cacache-tokio
(disabled): enable tokio runtime support for cacache.manager-moka
(disabled): enable moka, a high-performance in-memory cache, backend manager.with-http-types
(disabled): enable http-types type conversion supportLicensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.