Currently NGINX automatically adds ETag and Last-Modified HTTP response headers for RRDP content served from files shared via Gluster. According to the article if the ETag is based on inode as with Apache this can cause different ETags on different cluster nodes.
On the other hand this might be non-issue, see this thread which points to NGINX source code to show it generates ETags (in 2015) based on last modified time and content length.
See Advanced bits: revalidation with cluster mode in mind.
Currently NGINX automatically adds ETag and Last-Modified HTTP response headers for RRDP content served from files shared via Gluster. According to the article if the ETag is based on inode as with Apache this can cause different ETags on different cluster nodes.
On the other hand this might be non-issue, see this thread which points to NGINX source code to show it generates ETags (in 2015) based on last modified time and content length.