You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't look like there is currently a way to invalidate the in-memory cache if the client has requested the latest value. If the client needs the very latest value then there is no way to force the request down to the handler.
Perhaps if the client sets:
Cache-Control:max-age=0
or
Cache-Control:no-cache
then CachingInterceptor should skip TryGetValidCacheEntry. What do you think?
The text was updated successfully, but these errors were encountered:
Absolutely correct, although the no-cache and the max-age should take two different code paths. This stuff is kind of already implemented in a separate branch i ought to push back into master. Nag me tomorrow to make sure I do it :)
It doesn't look like there is currently a way to invalidate the in-memory cache if the client has requested the latest value. If the client needs the very latest value then there is no way to force the request down to the handler.
Perhaps if the client sets:
or
then
CachingInterceptor
should skipTryGetValidCacheEntry
. What do you think?The text was updated successfully, but these errors were encountered: