17687 2012-07-04 08:33:33 +0000 appcache: When resources are downloaded from the server because of the manifest file, the referrer should be set accordingly 2014-09-19 17:52:26 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#downloading-or-updating-an-application-cache P3 normal Unsorted 1 contributor ian adrianba ap eoconnor eric franko ian james jonas jrossi michaeln mike Ms2ger myfacebook roc zcorpan contributor oldest_to_newest 69631 0 contributor 2012-07-04 08:33:33 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html Multipage: http://www.whatwg.org/C#downloading-or-updating-an-application-cache Complete: http://www.whatwg.org/c#downloading-or-updating-an-application-cache Comment: When resources are downloaded from the server because of the manifest file, the referrer should be set accordingly Posted from: 90.146.74.58 by simon.schatka@compuware.com User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11 71027 1 contributor 2012-07-18 17:56:42 +0000 This bug was cloned to create bug 18280 as part of operation convergence. 77120 2 ian 2012-10-25 20:03:06 +0000 IE and Gecko use the URL of the Document object of (one of) the resource(s) that referenced the manifest. Opera and Webkit use "". Neither really makes much sense, but I don't want to chose a third option without first checking that nobody minds. Otherwise I'll spec it so it's the document URL like IE and Gecko. Anyone have an opinion? Demo: http://www.hixie.ch/tests/adhoc/html/offline/005.html 78808 3 ian 2012-11-26 04:52:34 +0000 The problem with using the Document URL is that there might be multiple Documents causing the same cache to be updated at the same time. The problem with using the manifest URL (or indeed, "") is that if two Documents that both refer to the same cache are loaded at the same time, they might both request images from the network both before and after the cache update starts, and so we'd end up with some images from the Documents (it being before we know they're in the cache) and some from the manifest. The first problem is probably less bad, except what if the manifest is being updated unrelated to any particular document or other? :-/ 109231 4 ian 2014-07-23 21:07:05 +0000 I really don't think either the Document or "" is the right answer. Maybe the manifest? But then no browsers are conforming. 111089 5 ian 2014-09-05 18:07:07 +0000 I guess using the manifest doesn't stop the problem of the Referer changing half-way through a load. I'll go with the empty string, unless someone objects first. 111816 6 contributor 2014-09-19 17:52:26 +0000 Checked in as WHATWG revision r8791. Check-in comment: Make appcache requests have no referrer, since it's not clear what referrer to use. https://html5.org/tools/web-apps-tracker?from=8790&to=8791