Resolve pagination links against a recorded response URL
Admin ·
Check a recorded next link when a client follows the wrong path. Start with the URL of the response that supplied the Link field and compare the original relative target with the resolved path.
Resolve the next page in the warehouse example
Load example and select Parse Link. Expect two Link fields and three entries. The relative next target ../pages/3 resolves to https://warehouse.example.test/api/pages/3 because the response address is https://warehouse.example.test/api/list/2.
The title Next, ready stays attached to the next link. The next row retains log,compact.css as a single target and identifies its preload relation and as=style parameter.
Clear Response URL and parse again. The relative targets stay visible. The report cannot resolve their full addresses without the recorded base.
Verify the target and anchor context independently
Load the example again. The third entry points to https://warehouse.example.test/items. Its anchor changes the context to the original response resource with the supplied fragment, displayed as #[withheld]. Both references resolve against the recorded response URL.
When you see a repeated rel parameter in one link value, review the first value. Later occurrences are ignored. Separate Link entries can each have their own relation values.
Check resource hints in the correct response block
If a capture begins with 103 Early Hints, check whether an expected Link field is in that block or the final response. This tool analyzes the selected final block by default. Paste just the 103 block to review its hints separately.
Export the JSON and check the source field number, target, relation and parameters. The report withholds credentials, query text and fragments in target and context addresses. Review destination and anchor text in the original when those values matter.
Common questions
Does a Link preload entry prove a resource loaded?
The field declares a hint. Check a browser network recording for the actual request and verify the selected type or fetch context.
Can several relations describe the same target?
Yes. Put the space-separated relation names in a single quoted rel parameter, such as rel="next alternate".