W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

VERSION-CONTROL on an existing resource

From: Greg Stein <gstein@lyra.org>
Date: Wed, 15 Nov 2000 17:03:19 -0800
To: ietf-dav-versioning@w3.org
Message-ID: <20001115170319.G5983@lyra.org>
Section 9.1.1 shows the use of a VERSION-CONTROL on an existing resource.
However, it responds with a 201 (Created). I'm thinking that it should be a
200 (OK) or a 204 (No Content) since it is not creating the Request-URI.

RFC 2616, 10.2.2 states that the created resource should be returned in a
Location: header (presuming it is different from the Request-URI). As I read
it, it may even mandate a Location: header for the 201 (Created) response.

I think it might be a bit whacky for VERSION-CONTROL to return the location
of the version history, so I'd recommend changing the response (for an
existing, versionable) resource to one of:

1) 200 (OK) with a body that specifies the URIs of the initial version and
   the version history.

2) 204 (No Content)

The first is certainly more informative for smart clients.


Greg Stein, http://www.lyra.org/
Received on Wednesday, 15 November 2000 20:01:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:45 UTC