W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

Re: Standardizing Firefox's Implementation of Link Fingerprints

From: Roy T. Fielding <fielding@gbiv.com>
Date: Tue, 10 Jul 2007 15:13:41 -0700
Message-Id: <3EE69C50-E077-4744-893B-C2207BA459A5@gbiv.com>
Cc: ietf-http-wg@w3.org
To: Edward Lee <edilee@mozilla.com>

On Jul 10, 2007, at 2:49 PM, Edward Lee wrote:
> On 7/2/07, Roy T. Fielding <fielding@gbiv.com> wrote:
>> Adding metadata to a URI that is orthogonal to its identifying  
>> purpose
>> duplicates the space of references and splits the power of the  
>> resulting
>> resources.
> Link Fingerprints are used to identify a particular version of a
> resource; if the Link Fingerprint does not match up, it's as if the
> resource was not found. In that sense, it strengthens the URI's
> ability to identify resources.

No, it does not.  A "resource" is not what is sent to the client in
response to a retrieval request.  Fragments are an extra level of
indirection that refers to a different resource defined by the
representation returned by the resource.  The only component in
the request chain that is even aware of the fragment is the UA.

This whole feature is completely unnecessary.  If you want the
resource to be named as a static representation, then use the hash
in its real identifier -- the URI path.  That way, both the server
and the client can verify that the representation fits the hash
prior to its delivery and the origin server can set the appropriate
metadata for cache-control, content-md5, etc.

Received on Tuesday, 10 July 2007 22:13:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:31 UTC