Improvements and fixes to HttpRobotRulesParser when following redirects #1103
Conversation
This file contains 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
- remove unsafe check for absolute URLs on redirects (location header) - resolve relative redirects using the redirect source as base URL - cache robot rules for all /robots.txt (if on default location) in a chain of redirects Signed-off-by: Sebastian Nagel <sebastian@commoncrawl.org>
|
Thanks @sebastian-nagel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
httpis not necessarily a valid and resolvable URL. For safety, always resolve the redirect location using java.net.URL(URL context, String spec)/robots.txt(if on default location) in a chain of redirectsNote: this PR is a result of implementing the RFC 9309 redirect rules to Nutch, see NUTCH-2990 and apache/nutch#779. I deliberately took the implementation in StormCrawler (#1058/#1074) as a starting point.