Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was just looking at our site on and one of their recommendations for speeding up a website is:

ETag headers should generally not be used unless you have an explicit reason to need them

I was wondering what this means. Does it mean that static content you know will not be changing should not have them, or does it mean content you know will be changing regularly shouldn't have them, or does it mean that you shouldn't use them generally unless you have a specific need.

If it's the latter, when is the right time to use them?

share|improve this question
up vote 9 down vote accepted

The main argument I have seen against them is that files that are common to many servers will have to be grabbed over and over again by the client. Better is to include a version string in the name of the file itself.

So for example, if you round robin load balance your web servers each server will generate its own ETag causing the client to grab it multiple times.

You can read more on the yahoo high performance website blog. The summary of this is that you can make it work but you have spend the time to configure it right.

share|improve this answer
That link just about answers my questions, thanks! – Django Reinhardt Oct 27 '10 at 10:08
tldr for the blog article: The webservers include the inode number in the ETag, which makes it unique to the machine. – user123444555621 Aug 30 '14 at 12:33
A bit late now, but this is a useful (if old) article from Yahoo too:… – Django Reinhardt Mar 10 at 12:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.