W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

Re: Summary of ETag related issues in RFC2518bis

From: Ted Hardie <hardie@qualcomm.com>
Date: Mon, 19 Dec 2005 15:20:02 -0800
Message-Id: <p0623090abfccf05e8730@[129.46.225.69]>
To: Yves Lafon <ylafon@w3.org>, Julian Reschke <julian.reschke@gmx.de>
Cc: Jim Whitehead <ejw@soe.ucsc.edu>, Cullen Jennings <fluffy@cisco.com>, WebDav <w3c-dist-auth@w3.org>

At 12:09 AM +0100 12/20/05, Yves Lafon wrote:
>
>
>My implementation returns the ETag that asubsequent GET would see, so option (2). Ans I am in the case where the PUT entity and the served entity will not be the same, as there are CVS actions done during the PUT, so possible keyword extensions, etc...

Are these property changes, or changes to the entity itself?  If to the entity, how does a get-range work?
			regards,
					Ted Hardie
Received on Monday, 19 December 2005 23:20:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:11 GMT