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

Re: New "200 OK" status codes, PATCH & PROPFIND

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 06 Aug 2007 19:54:14 +0200
Message-ID: <46B76046.6000604@gmx.de>
To: Henrik Nordstrom <henrik@henriknordstrom.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>

Henrik Nordstrom wrote:
> ...
> 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 "210 Information Returned" is PROPFIND

The problem with 210 (instead of 207) is that you can't deploy it. 
Clients expect 207. So either we'd need to expand the semantics to 207, 
or clients would need to be able to signal they understand 210.

It seems that you're trying to mirror the GET-Location header 
functionality into status codes and existing headers, with which I 

But wouldn't we also need some mechanism for the validity time, see 
"max-age" in 

Best regards, Julian
Received on Monday, 6 August 2007 17:54:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:43 UTC