W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

New "200 OK" status codes, PATCH & PROPFIND

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Mon, 06 Aug 2007 18:30:28 +0200
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1186417828.4273.98.camel@henriknordstrom.net>
Regarding the new proposed "209 Content Returned" status code.

I think recent discussions show that there is actually a need for two
new status codes.

209 Content Retuned
to be used when the entity has been modified. If the resource varies
then the response MUST contain a Vary header telling which request
headers the variance is based on just as for a GET. If any of those
headers is not present in the request due to special method requirements
then "Vary: *" must be used. A cache may update it's cache with the
returned entity, and any old matching responses MUST be invalidated.
This response status is identical to 200 OK in all regards except that
it's defined to always return the current requested entity and MUST NOT
be used for returning method specific status responses.

210 Information returned
to be used when auxillary information about the requested entity or
resource is returned. This response do not invalidate any cached
entities for the URI. The response may contain a Content-Location
indicating an URI where the same information can be retreived using GET
and optionally an Content-ETag header providing the current ETag for the
same.

Example use case for "209 Content Returned" is PATCH.

Example use case for "210 Information Returned" is PROPFIND

Regards
Henrik

Received on Monday, 6 August 2007 16:30:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:15 GMT