Link header parser and builder
Parse RFC 8288 Link headers into a table, or build one for pagination.
Runs in your browser. Your input is not uploaded.
Loading the tool…
What it does, how to use it, and questions
What it does
RFC 8288 Link headers carry typed links such as pagination: <…>; rel="next". APIs including GitHub use them instead of embedding URLs in JSON.
Parse a header into a table, or build one from URI and rel pairs.
How to use it
- Paste a
Linkheader value (with or without theLink:name). - Read URI, rel and other parameters.
- Or fill the builder and copy the header.
Things to watch for
- Commas separate links; quoted parameter values may contain commas.
- Only a practical subset of the grammar is parsed.
Questions
- What does rel=next mean?
- The URI of the next page of results.
- Can I paste multiple Link lines?
- Paste them as one header value joined with commas, as on the wire.
- Is anything fetched?
- No. Only the header text is parsed.
- Which parameters are shown?
- Every
key=valueafter the URI, includingrel,typeandtitle.