Re: Filters as views (ISSUE-45)

Hi Maik,

> This should only be used if you want to point to a concrete representation when directly returning an entity response following some kind of content negotiation.

The spec seems to agree with you:

>> For a response to a GET or HEAD request, [Content-Location] is an indication
>>       that the effective request URI refers to a resource that is
>>       subject to content negotiation and the Content-Location
>>       field-value is a more specific identifier for the selected
>>       representation.
>> 

—https://tools.ietf.org/html/rfc7231#section-3.1.4.2

That said, why can a page not be a content-negotiated version,
if the server has determined the client would not like long pages?
A representation can only present part of a resource;
in this case, the part just gets an identifier.

Best,

Ruben

Received on Thursday, 11 February 2016 18:49:30 UTC