HTTP headers | Link

For serialising one or more links in HTTP headers, the HTTP Link header-field is used. It allows the server to point an interested client to another resource containing metadata about the requested resource. It is semantically equivalent to the HTML <link> element. 
Syntax: 

Link: <uri-reference>; param1="value1" param2="value2"

Directive: This header accept a single directive as mentioned above and described below. The link header contains parameters, which are separated with ; and are equivalent to attributes of the <link> element. 

  • <uri-reference>: The URI reference, must be enclosed between < and >. 

Examples: 

  • This means that more information about the requested resource is available in the resource whose relative URI is https://www.geeksforgeeks.org/.
Link: <https://www.geeksforgeeks.org/>; rel="preconnect"
  • The URI must be enclosed between < and >. So, this is not a good way to write.
Link:https://www.geeksforgeeks.org/; rel="preconnect"

Specifying multiple links:  You can specify multiple links separated by commas. 

Example: 

Link: <https://example.one.com>; rel="preconnect", 
<https://example.two.com>; rel="preconnect", 
<https://example.three.com>; rel="preconnect"

Typical uses are: 

  • A map of different language, content-type and version-specific URIs
  • Licensing, such as Creative Commons
  • Information about how to edit the file
  • Policy information about appropriate use and/or distribution of the data

Supported Browsers: The browser supported by HTTP-header  link are unknown till now.
 

My Personal Notes arrow_drop_up


If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.

Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.


Article Tags :

Be the First to upvote.


Please write to us at contribute@geeksforgeeks.org to report any issue with the above content.