Anthony Accioly on Nostr: Quick question for folks who understand HTTP caching on reverse proxies like Squid or ...

Quick question for folks who understand HTTP caching on reverse proxies like Squid or Cloudflare. If I have a GET REST endpoint responding with 200 OK and the following headers:

Cache-Control: public, max-age=3600  
ETag: "123-a"

The proxy should cache and serve the response without hitting the underlying server more than once for the first hour, then send a request with If-Match: "123-a" when the cache goes stale, right? Is there any reason why it wouldn’t?

#http #caching #etag #rest #tech