Thanks Devon!
So just to clarify our request flow is:
Client > CDN > Go Reverse Proxy > Origin
Our Go Reverse Proxy has historically been responsible for adding caching
headers (e.g. Cache-Control and Surrogate-Control) when the origins have
failed to do so (as a way to ensure things are cache
Hello,
I'm using Go's standard library reverse proxy and I'm trying to figure out
if the standard library HTTP web server (e.g. http.ListenAndServe)
implements the relevant conditional request handling logic for
ETag/Last-Modified headers.
I did some Googling and noticed the HTTP file system r