ETag & Cache-Control Headers (II)

Continuing the discussion from ETag & Cache-Control Headers:

I do not want to deploy to S3. Currently I’ve written a reverse proxy in Go which adds the necessary headers I want and use the hugo server itself. I was looking for best practices and wanted to see if there is any flaws in my approach. But the thread was closed.

Caddy Server supports Hugo and allows to create a new posts as well. Caddy should support those headers. It might be hard to setup/flush cache headers for drafts especially.