Closed ebidel closed 9 years ago
Yes, please! Support for X-Associated-Content will be deprecated.
I knew you'd stalk this repo!
Question, is there priority in the Link
header, or that's completely deprecated? Also is the as=
final?
Yes, there is. It's an optional field but you should specify it where possible to give the UA and any intermediaries the context about type and priority of the resource:
p.s. current as
is as "final" as any living spec can be :-)
An priority level is gone?
Guessing you're thinking "pr", which is defined in Resource Hints spec?
The pr
attribute is defined for speculative resource fetches: prefetch, prerender, preconnect. Preload, on the other hand, is a declarative fetch (the user agent must fetch it), so pr
is a noop.
Got it. Thanks for clarifying @igrigorik. Hard to keep all these specs sorted.
Added support for the spec'd header. The X-Associated-Content
is also supported for now.
https://github.com/GoogleChrome/http2push-gae/blob/master/http2push.py
The
Link rel="preload"
is the new standard header as described in http://w3c.github.io/preload/. It would be good to preemptively support this. TheX-Associated-Content
is an old SPDY header.https://www.chromestatus.com/features/5757468554559488