How are relative URLs resolved in the Link header?

Target and anchor URIs are resolved using the RFC 3986 §5.2 algorithm against the specified Base URL or the previous page URL during simulated multi-page crawls.

What happens if a response contains multiple rel="next" entries?

The parser flags duplicate rel="next" declarations as potential errors and follows the first encountered relation per RFC 8288 rules.

How are non-ASCII characters handled in link parameters?

The parser decodes internationalized parameters using RFC 8187 encoding rules (such as title*) and validates percent-encoding on target IRIs.

Can this tool detect infinite loops in pagination headers?

Yes, the crawler preview tracks a visited-set of absolute URLs across response steps to identify cycles and limit execution to the configured max depth.

What validation is performed on preload and prefetch link hints?

The parser verifies whether preload and prefetch relations include required 'as' attributes and flags invalid destination values or deprecated attributes like rev.

Elysia Tools

Navigation

Network

HTTP Link Header RFC 8288 Parser and Pagination Crawler Preview

Parse RFC 8288 Link headers with the spec appendix-B algorithm, resolve relative URI-references against a base URL, classify rel types against the IANA registry, validate preload/prefetch hints, and simulate how a rel="next" pagination crawler walks your responses — including cycle detection.

Details

What this tool helps you do

The parser implements RFC 8288 Appendix B literally: comma-separated link-values, parameters as token or quoted-string with backslash escapes, RFC 8187 title* decoding, star-param override, first-rel-wins, and lowercased registered relation types. Targets and anchors are resolved with the RFC 3986 §5.2 algorithm (URL(), never the payload body base). Extra checks: unquoted values containing whitespace, IRIs that need percent-encoding, extension rel types that must be absolute URIs, deprecated rev, preload/prefetch without as, invalid as destinations, and duplicate rel="next" per response. Paste one response per line to watch a crawler follow rel="next" from the base URL — each line is resolved against the previous page, with visited-set cycle detection and a depth cap.

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Samples

Examples that match this tool

Continue with connected tools and hubs

Base URL: http://127.0.0.1:8080/search/code?q=addClass&page=1 Max crawl depth: 10 Link headers: </search/code?q=addClass&page=15>; rel="next", </search/code?q=addClass&page=34>; rel="last", </search/code?q=addClass&page=1>; rel="first", </search/code?q=addClass&page=14>; rel="prev"

HTTP Link Header RFC 8288 Parser and Pagination Crawler Preview

What this tool helps you do

Run this tool

Examples that match this tool

Continue with connected tools and hubs

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Verifying GitHub-Style Pagination Headers

2. Sequential Crawl and Asset Preload Validation

FAQ

Nginx Log Parser Samples

Markdown Link Extractor Samples

Web Image Processing Python Samples

Web Image Processing Rust Samples

NB-IoT LTE-M Cat-M1 CoAP LwM2M Cellular IoT Packet Analyzer

Webhook Debugger & Relay

DNSSEC Chain & RDAP Trust Auditor

Cron Expression Visualizer