- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 09 Jan 2014 16:35:18 +0100
- To: Henry Story <henry.story@bblfish.net>, Mark Nottingham <mnot@mnot.net>
- CC: Tim Berners-Lee <timbl@w3.org>, TAG List <www-tag@w3.org>, Arnaud LeHors <lehors@us.ibm.com>, Eric Prud'hommeaux <eric@w3.org>, Yves Lafon <ylafon@w3.org>, Philippe Le Hégaret <plh@w3.org>, Peter Linss <peter.linss@hp.com>, "Appelquist Daniel (UK)" <Daniel.Appelquist@telefonica.com>
On 2014-01-09 11:18, Henry Story wrote: > ... > ... > Btw. the http-bis spec for 303 seems a bit out of date here: > > [ http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-25#page-57 [ > This status code is applicable to any HTTP method. It is primarily > used to allow the output of a POST action to redirect the user agent > to a selected resource, since doing so provides the information > corresponding to the POST response in a form that can be separately > identified, bookmarked, and cached independent of the original > request. > ]] > ... It's the latest and greatest, and now very close to publication as RFC. FWIW, it goes on saying: "A 303 response to a GET request indicates that the origin server does not have a representation of the target resource that can be transferred by the server over HTTP. However, the Location field value refers to a resource that is descriptive of the target resource, such that making a retrieval request on that other resource might result in a representation that is useful to recipients without implying that it represents the original target resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful description are outside the scope of HTTP." -- <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-25.html#rfc.section.6.4.4.p.3> > ... Best regards, Julian
Received on Thursday, 9 January 2014 15:35:52 UTC