I've read a bit more about HTTP caching now. It seems that caching headers are very complex and clients are not guaranteed to obey them.

The only case in which caching would affect us for the April release is when two assets (e.g. images) are referred to twice on the same HTML page. A `no-cache` or `no-store` directive on such a resource seems to me like intentionally bad design and unlikely to happen.