[release/7.0] Support populating cache without serving from it. #47481
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.
Backport of #47392 to release/7.0
/cc @mitchdenny
Support populating cache without serving from it.
Description
At the moment if a developer sets
AllowCacheLookup
tofalse
butAllowCacheStorage
totrue
the output caching middlewhere will throw a null reference exception which is obviously not intended. The problem stems from the fact that the cache key that cache storage relies on is a side effect of looking up the cache. This change simply makes it so that the cache key is created even if justAllowCacheStorage
is enabled.This is a useful scenario because someone might want to implement a cache refresh mechanism which forces to repopulation of the cache without attempting to first fetch what might be considered stale data. The test case in this PR illustrates this scenario.
Fixes #46671
Customer Impact
{Justification}
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
We are just calling
CreateCacheKey
a second time. If the key is already created the method no-ops - so this just enables the scenario mentioned above.Verification
Packaging changes reviewed?
When servicing release/2.1