To ETag or not to ETag
|
04-06-2009, 02:20 AM
Post: #1
|
|||
|
|||
To ETag or not to ETag
(thread migrated from sourceforge forum - originally posted 6/25/2008)
This one's been bothering me for a while. ETags exist for a reason. It's part of the standard HTTP protocol ( http://www.w3.org/Protocols/rfc2616/rfc2...l#sec14.19 ) and is designed to help optimize cache utilization. Cacheing is generally good, so why is ETag bad? It can only mean that either: 1) the spec is broken 2) its implementation is broken Now, I have seem some discussion that says it's easy to break (server-side), so the same resource may have different ETag values which could lead to a cache miss, but what if you're a web guy who knows what he's doing and has consistent ETags? Why should my sites get penalized for using correctly-implemented W3C standards? |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
To ETag or not to ETag - pmeenan - 04-06-2009 02:20 AM
RE: To ETag or not to ETag - pmeenan - 04-06-2009, 02:21 AM
RE: To ETag or not to ETag - rchurchill - 10-06-2009, 10:59 AM
RE: To ETag or not to ETag - pmeenan - 10-06-2009, 11:25 PM
RE: To ETag or not to ETag - Naresh - 12-22-2009, 05:01 AM
RE: To ETag or not to ETag - pmeenan - 12-22-2009, 07:30 AM
|
User(s) browsing this thread: 1 Guest(s)