A Cache Store is responsible for storing and retrieving cached responses.\nIt is also responsible for deciding which specific response to use based off of\na response's Vary header (if present). It is expected to be compliant with\nRFC-9111.
The MemoryCacheStore stores the responses in-memory.
Options
\nmaxSize - The maximum total size in bytes of all stored responses. Default 104857600 (100MB).maxCount - The maximum amount of responses to store. Default 1024.maxEntrySize - The maximum size in bytes that a response's body can be. If a response's body is greater than or equal to this, the response will not be cached. Default 5242880 (5MB).Returns the current total size in bytes of all stored responses.
" } ], "displayName": "Getters" }, { "textRaw": "Methods", "name": "methods", "type": "module", "methods": [ { "textRaw": "`MemoryCacheStore.isFull()`", "name": "isFull", "type": "method", "signatures": [ { "params": [] } ], "desc": "Returns a boolean indicating whether the cache has reached its maximum size or count.
" } ], "displayName": "Methods" }, { "textRaw": "Events", "name": "events", "type": "module", "modules": [ { "textRaw": "`'maxSizeExceeded'`", "name": "`'maxsizeexceeded'`", "type": "module", "desc": "Emitted when the cache exceeds its maximum size or count limits. The event payload contains size, maxSize, count, and maxCount properties.
The SqliteCacheStore stores the responses in a SQLite database.\nUnder the hood, it uses Node.js' node:sqlite api.\nThe SqliteCacheStore is only exposed if the node:sqlite api is present.
Options
\nlocation - The location of the SQLite database to use. Default :memory:.maxCount - The maximum number of entries to store in the database. Default Infinity.maxEntrySize - The maximum size in bytes that a response's body can be. If a response's body is greater than or equal to this, the response will not be cached. Default Infinity.The store must implement the following functions:
", "modules": [ { "textRaw": "Getter: `isFull`", "name": "getter:_`isfull`", "type": "module", "desc": "Optional. This tells the cache interceptor if the store is full or not. If this is true,\nthe cache interceptor will not attempt to cache the response.
", "displayName": "Getter: `isFull`" }, { "textRaw": "Function: `get`", "name": "function:_`get`", "type": "module", "desc": "Parameters:
\nDispatcher.RequestOptions - Incoming requestReturns: GetResult | Promise<GetResult | undefined> | undefined - If the request is cached, the cached response is returned. If the request's method is anything other than HEAD, the response is also returned.\nIf the request isn't cached, undefined is returned.
The get method may return a Promise for async cache stores (e.g. Redis-backed or remote stores). The cache interceptor handles both synchronous and asynchronous return values, including in revalidation paths (304 Not Modified handling and stale-while-revalidate background revalidation).
Response properties:
\nCacheValue - The cached response data.Readable | Iterable<Buffer> | undefined - The response's body. This can be an array of Buffer chunks (with a .values() method) or a Readable stream. Both formats are supported in all code paths, including 304 revalidation.Parameters:
\nDispatcher.RequestOptions - Incoming requestCacheValue - Response to storeReturns: Writable | undefined - If the store is full, return undefined. Otherwise, return a writable so that the cache interceptor can stream the body and trailers to the store.
This is an interface containing the majority of a response's data (minus the body).
", "modules": [ { "textRaw": "Property `statusCode`", "name": "property_`statuscode`", "type": "module", "desc": "number - The response's HTTP status code.
string - The response's HTTP status message.
Buffer[] - The response's headers.
Record<string, string | string[] | null> | undefined - The headers defined by the response's Vary header\nand their respective values for later comparison. Values are null when the\nheader specified in Vary was not present in the original request. These null\nvalues are automatically filtered out during revalidation so they are not sent\nas request headers.
For example, for a response like
\nVary: content-encoding, accepts\ncontent-encoding: utf8\naccepts: application/json\nThis would be
\n{\n 'content-encoding': 'utf8',\n accepts: 'application/json'\n}\nIf the original request did not include the accepts header:
{\n 'content-encoding': 'utf8',\n accepts: null\n}\nnumber - Time in millis that this value was cached.
number - Time in millis that this value is considered stale.
number - Time in millis that this value is to be deleted from the cache. This\nis either the same sa staleAt or the max-stale caching directive.
The store must not return a response after the time defined in this property.
", "displayName": "Property `deleteAt`" } ], "displayName": "`CacheValue`" }, { "textRaw": "`CacheStoreReadable`", "name": "`cachestorereadable`", "type": "module", "desc": "This extends Node's Readable\nand defines extra properties relevant to the cache interceptor.
The response's CacheStoreValue
This extends Node's Writable\nand defines extra properties relevant to the cache interceptor.
If the response has trailers, the cache interceptor will pass them to the cache\ninterceptor through this method.
", "displayName": "Setter: `rawTrailers`" } ], "displayName": "`CacheStoreWriteable`" } ], "displayName": "Cache Store" } ] }