Cache performs two gets on misses

We observe two cache.get() calls whenever we miss. The first attempt is made in CacheController.cached_request(). We see the "No cache entry available" in logs. However, we immediately see another cache.get() call after this. This seems to be because CacheController.conditional_headers() makes another call to self.cache.get().
This doesn't appear to be ideal, but I'm not sure what change to propose. I see some other usage of self.cache.get in the Controller as well. Since we don't rely on etag/last-modified headers, we may just use a custom Controller that has a condition_headers that simply returns {}, but raising here to see if there's any shared appreciation for trying to limit the number of get calls to make to the cache, or ideas for how otherwise to improve that.

Start by tracing CacheController.cached_request() and conditional_headers(), then inspect the other self.cache.get usages mentioned in the issue. Reproduce a cache miss and review existing tests or logging around these entry points; done should be defined as an agreed behavior for avoiding an unnecessary second get without breaking conditional-header handling.