From ef56cccb28df78ebf72bd0c65aa1c0cf74d4afb4 Mon Sep 17 00:00:00 2001 From: Adam DeHaven Date: Mon, 11 Mar 2024 10:00:32 -0400 Subject: [PATCH] docs(nitro): improve cache.varies property documentation The cache.varies option needs to be better documented to help understand multi-tenant implementation and discarded headers. --- docs/1.guide/6.cache.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/1.guide/6.cache.md b/docs/1.guide/6.cache.md index 3f6ac86b9c..27b4edebf2 100644 --- a/docs/1.guide/6.cache.md +++ b/docs/1.guide/6.cache.md @@ -236,7 +236,7 @@ The `cachedEventHandler` and `cachedFunction` functions accept the following opt A function that returns a `boolean` to bypass the current cache without invalidating the existing entry. :: ::field{name="varies" type="string[]"} - An array of request headers to be considered for the cache, [learn more](https://github.com/unjs/nitro/issues/1031). + An array of request headers to be considered for the cache, [learn more](https://github.com/unjs/nitro/issues/1031). If utilizing in a multi-tenant environment, you may want to pass `['host', 'x-forwarded-host']` to ensure these headers are not discarded and that the cache is unique per tenant. :: ::