51940 2011-01-05 11:43:52 -0800 implement Link: header 2023-01-25 05:02:19 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) PC OS X 10.5 UNCONFIRMED https://bugs.webkit.org/show_bug.cgi?id=194539 P2 Normal --- 102936 51941 57842 20018 0 gavinp webkit-unassigned abarth ap front.end.developing gavinp jerome mathias me miket mike nickshanks oldest_to_newest 329692 0 gavinp 2011-01-05 11:43:52 -0800 RFC 5988 re-introduces the Link: header, last seen in RFC 2068 (and not RFC 2616!). The Link header has lots of uses; one less-confusing such use is to use it for rel=prefetch, and rel=subresource allowing server side indication of important resources in advance of a document parse. Implement the link header. 330926 1 ap 2011-01-07 12:27:04 -0800 I'm wondering what the difference between link=prefetch and link=subresource is. I couldn't find the latter documented anywhere. Is this the same as prefetch, but delaying load event? 330928 2 abarth 2011-01-07 12:32:55 -0800 > I'm wondering what the difference between link=prefetch and link=subresource is. I couldn't find the latter documented anywhere. I believe prefetch is a low priority load (so it waits until all the other resources for the page are loaded before clogging up the network) whereas subresource is a high priority load that tries to load the resource in time before its needed by the same page. 333844 3 gavinp 2011-01-13 11:45:05 -0800 To be clear about my first comment, I think the initial implementation of the Link header should shy away from rel types that mutate or affect data; so let's stick with rel=prefetch, rel=subresource, rel=dns-prefetch and possibly rel=icon. 404343 4 mathias 2011-05-16 00:41:49 -0700 Test cases: http://greenbytes.de/tech/tc/httplink/ 1050813 5 front.end.developing 2014-11-24 00:26:48 -0800 What is the state of this bug? We have implemented Link header for mobile and I was disappoint why nobody implement it well.