Re: A new HTTP response code say 209

* Henry S. Thompson <> [2014-01-09 11:57+0000]
> Henry Story writes:
> > It is a bad idea to put semantics into media types. Media types are
> > there to help interpret the representation coming back from the
> > resource, not for describing the resource itself ( since after all
> > the same resource could have a number of different representation in
> > different formats, as we do in RDF land regularly )
> > ...
> > What is wanted is something that does what 303 does, but returns the content immediately. 
> Right -- to short-circuit this, in the TAG f2f this morning, I offered
> the following paraphrase for the 2xx proposal:
>   A 2xx response code signals all and only the short-circuiting of a
>   303 response, with the content of what a GET to the Location header
>   of the 303 would have had, and a Content-location header giving what
>   would have been the Location of the 303.
> So no new 'semantics', in the sense that whatever you believe 303
> means wrt what the relation between what you originally asked for, and
> what you _eventually_ get, holds for 2xx between what you originally
> asks for and what you get _immediately_.


There's an argument that 303 says "here's something related" instead
of the desired "here's information about a non-information-resource".
A shortcut for 303 doesn't improve that situation, but it does make
the 303 dance much more efficient, which is important regardless of
how you think about 303s. I'd be content with this outcome. If we
eventually discover some debilitating ambiguity in competing uses of
303, we'll have to deal with that regardless of how 2xx is defined.

> ht
> -- 
>        Henry S. Thompson, School of Informatics, University of Edinburgh
>       10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
>                 Fax: (44) 131 650-4587, e-mail:
>                        URL:
>  [mail from me _always_ has a .sig like this -- mail without it is forged spam]


office: +1.617.599.3509
mobile: +

Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.

Received on Thursday, 9 January 2014 12:24:21 UTC