- From: Ted Hardie <hardie@qualcomm.com>
- Date: Mon, 19 Dec 2005 15:06:28 -0800
- To: Julian Reschke <julian.reschke@gmx.de>, Jim Whitehead <ejw@soe.ucsc.edu>
- Cc: Cullen Jennings <fluffy@cisco.com>, WebDav <w3c-dist-auth@w3.org>
At 11:50 PM +0100 12/19/05, Julian Reschke wrote: >Jim Whitehead wrote: >>I'd like clarification as well. >> >>It's fine for WebDAV to place additional requirements on base HTTP servers. I don't see anything in the definition of PUT or of the Etag header that would prevent Etag being returned by PUT. > >That's not the issue here. > >The question here is whether an ETag returned upon PUT is for the entity the client sent (1), or for the entity the server would send upon a subsequent GET (2). I have personally always assumed that an ETag returned on a PUT is for the entity the client sent , and that if what the client would get at a subsequent GET was different, the ETag changed. It's not clear to me how a subsequent range request would work interoperably if this were not the case, as it seems to require that the client understand what transformation the server is going to perform (that is, the client would have to somehow know what the bits would be after its PUT). It certainly seems easier to me to code a conditional with this assumption. Just my personal opinion, regards, Ted Hardie
Received on Monday, 19 December 2005 23:06:42 UTC