W3C home > Mailing lists > Public > www-tag@w3.org > January 2011

Re: Understanding 'Content-Location' header in the IETF HTTPbis draft

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 05 Jan 2011 21:33:24 +0100
Message-ID: <4D24D594.7030206@gmx.de>
To: Bob Ferris <zazi@elbklang.net>
CC: www-tag@w3.org
On 05.01.2011 20:14, Bob Ferris wrote:
> ...
>> Again, there are no fragment IDs in HTTP requests. HTTP doesn't care.
>>
>> A 200 response to GET carries a representation of the requested
>> resource. Full stop. It may carry a C-L header as well, but that's not
>> what *that* particular paragraph is worried about.
>
> Yes, but this paragraph was about "Identifying the Resource Associated
> with a Representation", which can have a URI with a fragment id as well
> (from my understanding).

No no no. You can't send an HTTP request to an HTTP URI + fragment. You 
drop the fragment, receive a representation, and then process the 
fragment according to the media format. The origin server never sees the 
fragment id.

> ...

Best regards, Julian
Received on Wednesday, 5 January 2011 20:53:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:29 GMT