HTTP cache

Cache responses at the gateway so repeat requests never reach the app.


Type	`httpCache`
Category	Traffic

Fields

Field	Type	Required	Default	Description
`maxTtl`	number	no	—	Longest a response is kept, in seconds.
`maxStale`	number	no	—	How long a stale entry may still be served while it refreshes.
`memoryLimit`	text	no	—	Cap on the in-memory cache, e.g. 100MB. Example: `100MB`.
`cacheableStatusCodes`	list of numbers	no	—	Response codes worth caching. Empty uses Goma's defaults. Example: `200`.
`excludedResponseCodes`	list of text	no	—	Codes or ranges to keep out of the cache, e.g. 5xx. Example: `5xx`.
`includeQueryInKey`	true/false	no	—	Off means /page?a=1 and /page?a=2 share one cached response.
`queryParamsToCache`	list of text	no	—	Restrict the key to these parameters, so tracking parameters don't fragment the cache. Example: `page`.
`disableCacheStatusHeader`	true/false	no	—	By default Goma reports HIT/MISS on each response.
`cachePrivateResponses`	true/false	no	—	Off by default: a request carrying an Authorization header or a cookie skips the cache entirely, since one shared entry would be served to every caller. On, each caller gets their own entry.