- From: Yves Lafon <ylafon@w3.org>
- Date: Fri, 5 Sep 2014 05:51:59 -0400 (EDT)
- To: Julian Reschke <julian.reschke@gmx.de>
- cc: Sandro Hawke <sandro@w3.org>, "Roy T. Fielding" <fielding@gbiv.com>, Martin Thomson <martin.thomson@gmail.com>, Eric Prud'hommeaux <eric@w3.org>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On Fri, 5 Sep 2014, Julian Reschke wrote:
>> In LDP applications, these calls are more like RPC than like displaying
>> a web-page, so milliseconds might possibly count more than they do in
>> more common existing applications.
>> ...
>
> It that's the problem, have you considered to tweak 303 to actually return
> the representation of the "other" resource (using a new Prefer option?)?
>
> GET / HTTP/1.1
> Prefer: contents-of-related
>
> HTTP/1.1 303 SEE OTHER
> Location: /other
> Preference-Applied: contents-of-related
> ...
>
> (representation of /other)
From 7231:
<<
Except for responses to a HEAD request, the representation of a 303
response ought to contain a short hypertext note with a hyperlink to
the same URI reference provided in the Location header field.
>>
So tweaking 303 to return the content of Location: would be weird, even
with the introduction of a new conneg header.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Friday, 5 September 2014 09:52:04 UTC