Interface: CachePluginStrategyInput

Properties

Property	Type	Description	Defined in
`clearRelatedCache?`	`boolean`	-	inputs.ts:55
`contentTypes?`	\| ( \| `string` \| `CacheContentTypeConfigInput`)[] \| `CacheContentTypeConfig`[]	-	inputs.ts:58
`debug?`	`boolean`	-	inputs.ts:48
`enableAdminCTBMiddleware?`	`boolean`	-	inputs.ts:51
`enableContentApiPurge?`	`boolean`	-	inputs.ts:53
`enableDocumentServiceMiddleware?`	`boolean`	-	inputs.ts:52
`enableEtag?`	`boolean`	-	inputs.ts:49
`enableXCacheHeaders?`	`boolean`	-	inputs.ts:50
`hitpass?`	`boolean` \| `CachePluginHitpass`	The default hitpass for every content type and route that does not set its own. The plugin ships one that bypasses the cache for any request carrying an authorization or cookie header. Note this is consumed during resolution and deliberately not carried on the resolved CachePluginStrategy: by the time resolution finishes, every route holds its own effective hitpass, so a copy on the strategy could only disagree with them.	inputs.ts:70
`keys?`	\| `CacheKeysConfig` \| `CacheKeysConfigInput`	-	inputs.ts:59
`keysPrefix?`	`string`	-	inputs.ts:57
`maxAge?`	`number` \| `Milliseconds`	-	inputs.ts:56
`resetOnStartup?`	`boolean`	-	inputs.ts:54