W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2011

[Bug 14704] appcache: allow a manifest to be identified by something other than its URL

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 Nov 2011 16:48:23 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RNSMx-0001AK-H3@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14704

--- Comment #4 from Karl Dubost <karl+w3c@la-grange.net> 2011-11-07 16:48:22 UTC ---
Anne, I know what is URL fingerprinting. In my previous job, we were using it
for some specific big sites. There are many ways do do that. One of the way to
do that is to use a timestamp. 

http://example.org/blabla?yyyymmddhhmmss


This answer doesn't make sense in the context of your previous comments:
"No, because as far as the server is concerned the resource exists
permanently."

URL Fingerprinting is specifically used for busting the browser cache in a way
which is random. Basically we do not know in advance when it will change. We do
that usually when hosting CSS files on a CDN or icons for profiles pictures in 
a social network for example, where you usually want the photo live forever
(Long caching information - Expires in the order of months) and at the same
time be able to have the browser to update it when there is a new image. 

The proposal for a separate identifier is basically recreating a HTTP 302
mechanism.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 7 November 2011 16:48:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 November 2011 16:48:25 GMT