2 added link to similar question on security.stackexchange
source | link

Security tools sometimes report this ETag inode exposure when it is not there. Unless you have an ancient Apache version (1.3.27 or earlier), I'd recommend you challenge the infosec team to prove that it is real.
Tomcat 7 is a completely different product written in Java and does not calculate the ETags in a way that can expose sensitive server information. So, No.

See also this previous question.

Security tools sometimes report this ETag inode exposure when it is not there. Unless you have an ancient Apache version (1.3.27 or earlier), I'd recommend you challenge the infosec team to prove that it is real.
Tomcat 7 is a completely different product written in Java and does not calculate the ETags in a way that can expose sensitive server information. So, No

Security tools sometimes report this ETag inode exposure when it is not there. Unless you have an ancient Apache version (1.3.27 or earlier), I'd recommend you challenge the infosec team to prove that it is real.
Tomcat 7 is a completely different product written in Java and does not calculate the ETags in a way that can expose sensitive server information. So, No.

See also this previous question.

1
source | link

Security tools sometimes report this ETag inode exposure when it is not there. Unless you have an ancient Apache version (1.3.27 or earlier), I'd recommend you challenge the infosec team to prove that it is real.
Tomcat 7 is a completely different product written in Java and does not calculate the ETags in a way that can expose sensitive server information. So, No