Re: NEW ISSUE: Drop Content-Location

On 29 Nov 2006, at 14:05, Henrik Nordstrom wrote:
> ons 2006-11-29 klockan 13:41 -0800 skrev Roy T. Fielding:
>>     The value of Content-Location also defines the base URI for the
>>     entity.
>> s/also defines/does not define/;
>> Such a change would not effect current practice and would still allow
>> Content-Location to be useful for all of the other reasons it exists
>> (none of which are broken by IIS or MSIE because they don't author).
> Partly agreed as it's unlikely the header will ever get supported by
> clients in the current state of things, but please note it's also in
> RFC2396->RFC2110.
> There is no doubt that servers sending bad Content-Location is broken,
> and this in large due to clients not supporting it so server admins
> hasn't noticed they are sending bad Content-Location headers.

Could that be solved my creating a ERR method, so that clients could  
send feedback to servers at the resource they found wanting?

ERR /page0 HTTP...

Your Content-Location is broken see spec xyz

> It's worth noting that in many cases servers sending bad
> Content-Location headers is also sending bad Location headers, often
> seen if you drop the last / on a directory request etc...

> Regards
> Henrik

Received on Wednesday, 29 November 2006 22:19:09 UTC