New issue
Advanced search Search tips

Issue 449620 link

Starred by 17 users

Issue metadata

Status: Fixed
Closed: Sep 2015
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Test: ----
Launch-UI: ----
Rollout-Type: ----

Blocked on:
issue 450682

Sign in to add a comment

OWP Launch: Resource Hints - preconnect

Project Member Reported by, Jan 16 2015

Issue description

Change description:
Adds support for <link rel="preconnect" href="..."> as a hint that the browser should predictively open a connection to the supplied server/protocol for resources that will be needed later in the loading process.

Changes to API surface:
Adds "preconnect" as a method to the link element and HTTP header as defined in the spec.

Public standards discussion:

Support in other browsers:
Internet Explorer: no
Firefox: no
Safari: no

Blockedon: chromium:450682
Project Member

Comment 2 by, Jul 29 2015

The following revision refers to this bug:

r199657 | | 2015-07-29T12:26:54.678982Z

Changed paths:

Turn on <link rel=preconnect> support by default

Intent to ship thread:

BUG= 449620 

Review URL:
Labels: -M-42 M-46
Status: Fixed
I believe that this is enabled by default in M46. The blocked on issue isn't closed yet but seems stale with CLs landed so I'm going to assume that everything is fine. Let me know if anything is missing.

I tried using preconnect on my website using HTTP response header and also as part of markup, but I am not sure whether its working as expected or not.
I tried using chrome://dns method on browser to check if its changing the subresource-preconnects or not but its not impacting it for that domain.
I tried like this :
link :; rel=preconnect;

How should I verify its working correctly?
Still waiting for the answer.Can someone please help out here.

Sign in to add a comment