docs(cache): add example usage for cache.varies
#2241
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
β Type of change
π Description
The
cache.varies
option forrouteRules
needs to be better documented to help understand the cache behavior and discarded headers, especially related to multi-tenant implementations.The explanation is not currently obvious when reading through the docs; however, was better explained in nuxt/nuxt#26102 (comment) by @pi0. This PR surfaces the explanation and provides docs visitors a keyword of "tenant" they can search for as a hint. (It took me 3 days to figure out why my
host
headers were returninglocalhost
π )I also created a corresponding PR for the Nuxt docs: nuxt/nuxt#26197
π Checklist