Re: See Other vs Contents of Related, was: 2NN Contents Of Related (303 Shortcut)


Also ó Content-Location is *not* a flag that conneg has happened; thatís only a use case for it.

One important point that I donít see being addressed here is that resource A is *claiming* that itís presenting a representation of resource B ó it isnít authoritative for that resource (even if theyíre on the same server). Thatís an important distinction, and itís precisely the one made by Content-Location.


On 5 Sep 2014, at 1:01 pm, Julian Reschke <> wrote:

> On 2014-09-05 11:51, Yves Lafon wrote:
>> 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.
> I believe you're reading too much into the "ought to".
> If the client clearly says "give me the representation of the 'other' resource", then the server ought to be able to do that. (pun intended)
> Best regards, Julian

Mark Nottingham

Received on Friday, 5 September 2014 10:36:24 UTC