Conversation
Mantisus
force-pushed
the
fix-relative-base
branch
from
September 30, 2026 16:27
b3ddddf to
d61677d
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
extract_linksandenqueue_linksin the HTTP-based crawlers now resolve a relative<base href>against the page URL and fall back to the page URL when the base is invalid. Previously, a relative base dropped every relative link on the page, and an invalid one made link extraction fail.PlaywrightCrawleralso falls back to the page URL when Chromium reports an invalid base asabout:blank, and ignores the whitespace around link URLs.Testing
✍️ Drafted by Claude Code