Subresource server header header not working
Trying to use the subresource server hint but it doesn't seem to work.
In the screens below, you can see the master page with the headings "Link" and both resources will be retrieved later. And as you can see, the parser is the initiator instead of the headers received before any content was parsed. So the result is the same as before we used this header :(
Any ideas why?
full size: http://i.stack.imgur.com/2ey2K.png
full size: http://i.stack.imgur.com/fHXCM.png
source to share
-
This has been an open bug in the Chromium project since 2010:
The Link element Link has the equivalent of a response header. The form follows:
Link: <http://href.here/to/resource.html>;rel="prefetch"
we must maintain this header, in particular for prefetching rel, subresource and dns-prefetch types.
At the time of this writing, the issue has been updated 2 days ago, 2014-10-28.
More on the issue: https://code.google.com/p/chromium/issues/detail?id=58456 -
According to RFC 5988 Section 5 ,
The Link object's header field provides a facility for serializing one or more links in HTTP headers. It is semantically equivalent to an element
<LINK>
in HTML. -
The W3C page indicates that
The HTTP link header allows metadata to be passed without actually touching the resource in question
-
In a related Webkit bug, a 2011 comment indicates that handling the link header
just a matter of connecting an HTML element.
Based on these links, I would conclude that Chrome is handling this header as it <head>
will link
.
Since it doesn't break the page, I would not lose sleep over it ... in Chrome or Firefox . Internet Explorer, on the other hand, denies that they will add support - and I quote - "we have no plans to fix this limited use of the Link header we saw on web pages."
source to share