I was considering moving my static files to multiple origin servers, however I noticed NGINX computes different Etags for identically deployed files on the different servers, which will then mess with downstream caching layers thinking files keep changing which have not.
What I wanted to happen was for the Etag to be dependent on the served file itself, e.g. using a MD5 or other hash of the content (and naturally for NGINX to locally cache that for performance).
Is this possible with the provided static file serving, or is it expected that I solve this in another way? e.g. write my own "file server" app/script that does compute and cache the hash, or ensure all the filesystem meta data (whatever it uses) is always identical somehow?
Using Apache or similar instead is an option.