I'm not sure if this is something file_entity even has control over, or if supplemental modules are needed.
I am working on a site hosted on the Acquia Managed Cloud. The hosting architecture includes a Varnish cache.
When I replace a public file (e.g. a PDF file) in an existing File Entity with a file of the same name, the old file remains cached in Varnish until the cache expires. Is there a way to trigger invalidation of the Varnish cache entry when a file is replaced?