Expand description
The response cache: JSON reads kept by ETag, so a repeated one is answered from a 304.
Structs§
- Cached
Response - A response the cache holds for a URL: the validator HEY sent with it, and the body it validates.
- File
Cache - Keeps cached responses on disk, the same layout the Go SDK uses:
etags.jsonmaps keys to validators andresponses/<key>.bodyholds the bodies. Anything that goes wrong on disk is treated as a miss. - InMemory
Cache - Keeps cached responses for the life of the process.
Traits§
- Response
Cache - Stores JSON responses by
ETagso a repeated read can be answered from a 304.
Functions§
- cache_
key - The key a URL is cached under. The credentials are folded in so one person’s cached reads are never answered to another.