Someone mentioned to me that it's actually using the browser cache. This means you don't even need to have a cache store set!
@websebdev Yes! It uses etags (see en.wikipedia.org/wiki/HTTP_ETag) and it’s pretty cool how they work. One of thing I‘ve done in the past is include the git commit hash in the etag generation so clients would see the updated page when the code had changed
@websebdev Yes this is http caching(using etags), But it doesn’t skip controller query(needs that to calculate staleness), it just skips view rendering since browser can use locally cached version.
@websebdev Yes this will not return any body in response so browser can serve from cache and the request hence feels faster. The slow query will still execute so it wont be a lot of savings besides speeding network call since there is no data sent