Re: PUT vs strong ETags

Henrik Frystyk Nielsen wrote:
> Having a PUT response include an e-tag associated with the current
> entity is necessary in order to avoid the lost update problem (see [1]).
> I don't think this is a redefinition of the use of e-tags: section
> 10.2.2 states that
> "A 201 response MAY contain an ETag response header field indicating the
> current value of the entity tag for the requested variant just created,
> see section 14.19."

Good point, I wasn't aware of that part. But this is for creating 
resources (PUT -> 201), what about updating (PUT -> 200)???

> The use of the term "requested variant" is consistent with the use in
> section 14.19 and elsewhere in the spec. It refers to the resource
> identified by the request URI regardless of the method used.

Now that's certainly not obvious, and it would be nice if this would 
appear somewhere in the errata.

Best regards, Julian

Received on Wednesday, 30 November 2005 09:13:35 UTC