Comments on: Should I Remove ETags From My Headers? http://www.cloudfour.com/should-i-remove-etags-from-my-headers/ Expert Web and Mobile Design, Development and Strategy Thu, 02 Feb 2012 22:58:07 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Drew http://www.cloudfour.com/should-i-remove-etags-from-my-headers/comment-page-1/#comment-14956 Drew Sun, 27 Jun 2010 12:47:19 +0000 http://www.cloudfour.com/?p=110#comment-14956 If I remove Etags does this mean I will remove any last modified headers that the search engines use? If I remove Etags does this mean I will remove any last modified headers that the search engines use?

]]> By: AskApache http://www.cloudfour.com/should-i-remove-etags-from-my-headers/comment-page-1/#comment-2870 AskApache Wed, 10 Dec 2008 02:35:36 +0000 http://www.cloudfour.com/?p=110#comment-2870 <blockquote>Since <strong>our strategy is to provide a far futures cache expiration date</strong>, I am perfectly comfortable removing the ETags.</blockquote> Bingo! All that validation is impressive, works wonderfully, and does make sure visitors have the latest versions... But that is more than alot of overkill for most websites. Unless you are a proxying/caching server or have some other unique freshness requirements, you should only choose 1 method of cache validation (etags, last-modified, md5-digest, etc..) and of course setting future expires headers (even if only for 24 hours) means your visitors and server will have 24-hours of connectionless exchange without wasting CPU, bandwidth, etc..

Since our strategy is to provide a far futures cache expiration date, I am perfectly comfortable removing the ETags.

Bingo! All that validation is impressive, works wonderfully, and does make sure visitors have the latest versions… But that is more than alot of overkill for most websites. Unless you are a proxying/caching server or have some other unique freshness requirements, you should only choose 1 method of cache validation (etags, last-modified, md5-digest, etc..) and of course setting future expires headers (even if only for 24 hours) means your visitors and server will have 24-hours of connectionless exchange without wasting CPU, bandwidth, etc..

]]>