Thanks to buf481 suggestion in MGNLAVERS-97, supporting ETag configurable in advanced cache policies module would be an interesting topic which has been mentioned shortly here in our Cache improvements concept page.

It would be nice to have it configurable in the cache configuration. The ETag could be an option that could be enabled in the cache policy and directly linked to the records that is stored there (and hence flushed when new content is activated) or be a separate area of configurable caching (similar to the browser cache node) and generated from lastModifed+uuid.