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 skip TryGetValidCacheEntry. What do you think?