DevKits

Response · Response header

Link

Serialized <link> relationships as an HTTP header.

What is Link?

Encodes typed relationships to other resources in header form — most commonly `preload` for early resource hints, or `next` / `prev` for pagination.

Typical usage

Set for HTTP/2 server push (deprecated), preload hints, and REST API pagination.

Examples

Preload a font

Link: </fonts/x.woff2>; rel=preload; as=font; type=font/woff2; crossorigin

Pagination

Link: <?page=3>; rel="next", <?page=1>; rel="prev"

Specification

RFC 8288

Frequently asked questions

What is the Link HTTP header?

Encodes typed relationships to other resources in header form — most commonly `preload` for early resource hints, or `next` / `prev` for pagination.

Is Link a request or response header?

Link is a response header — the server sends it to the client. Set for HTTP/2 server push (deprecated), preload hints, and REST API pagination.

What does a Link header look like?

A typical Link header looks like: Link: </fonts/x.woff2>; rel=preload; as=font; type=font/woff2; crossorigin (Preload a font).

Related headers

Location

The redirect target (3xx) or newly created resource URL (201).

Retry-After

How long the client should wait before retrying.

Server

Identifies the server software.

Date

When the response was generated.

Allow

Which HTTP methods the target resource supports.

Work with this header

User-Agent Parser →See how servers read client hints.cURL Converter →Turn a curl command into fetch / code and back.URL Parser →Break a URL into scheme, host, path and query.