4 ms·

Serious question: is properly handling the "Not Modified " status code really considered caching or is there a better name? Maybe client-side caching? HTTP cach

Serious question: is properly handling the "Not Modified " status code really considered caching or is there a better name? Maybe client-side caching? HTTP caching in my mind is associated with something like varnish.

artifaxx 12y ago
Caching is simply keeping a response that hasn't changed so you don't have to recompute it. There can be many levels of cache. Varnish is one useful type of cache, but there are many others too.
wolf550e 12y ago
Conditional GET and not re-downloading the same content are important aspects of caching. They save bandwidth and remove the download part of latency. For small resources, serving the content again instead of 304 will not matter.
garfij 12y ago
Yes, that along with dealing with Last-Modified, If-Not-Modified, ETag, and other similar HTTP Headers is what is meant by HTTP Caching. From what I can tell Varnish uses these same concepts to do what they do (caching HTTP reverse proxy). See * https://tools.ietf.org/html/rfc7234#section-1 https://tools.ietf.org/html/rfc7234#section-1 * http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html * https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching_FAQ https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching_FA...