Not Modified is changing the cache-control headers

Not at my desk until later to add some more code. However, the 3rd time the server is not hit. It’s taken from browser cache of previous call (expected since the cache-headers are set private).

The server code in this case doesn’t short circuit. The same results (response object) would be passed to the HttpResult constructor each time with the same LastModified date being set as well.

Am I even understanding correctly how the 304 reply works? My understanding is that the first call should have stored in cache the result set. The second call, which returns the 304, is also empty - but should then automatically fetch results from the cache for usage? Or is this something we have to manually do?