Thomas Broyer schrieb:
If I read RFC2616 correctly, nothing prevents the "latest entries
only" and "full" representations (or any representation of the same
resource) to share the same entity-tag, i.e. nothing prevents a server
to assign an entity-tag to a resource rather than its representations.
Maybe servers should use a weak etag in this case? But RFC2616 says in
section 13.3.3 that "Clients MAY issue simple (non-subrange) GET
requests with either weak validators or strong validators. Clients
MUST NOT use weak validators in other forms of request."
...
I think this is a misunderstanding of how HTTP/1.1 is supposed to work.
If a server returns the same ETag for different entities returned for
the same URL, this will cause breakage of caches. You may want to
re-read Section 13.6 of RFC2616
(<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.13.6>).
Best regards, Julian
