This article left me wanting, in terms of understanding why (or when) you'd want to have the server or proxy cache return a 304 (Not Modified) - I've been opera

This article left me wanting, in terms of understanding why (or when) you'd want to have the server or proxy cache return a 304 (Not Modified) - I've been operating under the understanding that "the best request is one that is never made". Given a complex web page with a large number of HTTP requests (especially now that bundling of assets is considered an anti-pattern with HTTP/2), that the latency introduced by all those repeated requests that end up returning a 304 are redundant if we can serve them directly from the client. Most caching tutorials seem to skip this area.