- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Fri, 11 Apr 2014 09:43:39 +0100
- To: Yves Lafon <ylafon@w3.org>
- Cc: www-tag@w3.org
Yves, I found it hard to think of other good reasons for using HTTP 209 except for saving a round-trip. The “don’t change the URL bar” is a bit of a reach. If you can think of one, let me know. I actually think the 303+200 definition is unhelpful for the general case. It sort of works for rel=describedby, but only when the originally requested resource is a non-information resource. But if you’re requesting an information resource and wanting to get its description, or its provenance, or a related package, then the original response could have been a 200. The real distinguishing feature is the inclusion of a Link with a relevant relation, followed by a request on that related resource. I’m happy to change the recommendation re Location/Content-Location. Jeni ------------------------------------------------------ From: Yves Lafon ylafon@w3.org Reply: Yves Lafon ylafon@w3.org Date: 10 April 2014 at 23:29:57 To: Jeni Tennison jeni@jenitennison.com Cc: www-tag@w3.org www-tag@w3.org Subject: Re: draft HTTP 209 draft spec review > On Sat, 5 Apr 2014, Jeni Tennison wrote: > > > TAG members, > > > > As discussed during our face-to-face this last week, I have put together > > a draft review of the draft spec for the HTTP 209 status code, at: > > > > https://github.com/w3ctag/spec-reviews/blob/master/2014/04/http-209.md > > > > I?d appreciate a second pair of eyes before we officially forward this > > on to Eric Prudhommeaux as a consensual TAG review. > > I would also be happy if the primary goal stated by the document was not > "saving one round trip", especially if we decide to use 209 for other > "related" use cases, as we discussed during the f2f. > > Thinking about it, 303+200 should be > 209, with a Location: equal to Content-Location: > > That leaves open definition of 209 where Location: is different from > Content-Location: and lead to a more generic definition of 209 which would > 303 + a body which about what was requested, but not the result of > dereferencing the URL present in Location: > > > -- > Baroula que barouleras, au tiéu toujou t'entourneras. > > ~~Yves > > > > -- Jeni Tennison http://www.jenitennison.com/
Received on Friday, 11 April 2014 08:44:04 UTC