Configurable inmediate redirection #433
Open
Conversation
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
WebURLs and WebCrawler now supports for individual URLs to be followed right away even if they were already visited. They will not be scheduled, but processed.
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.
WebURLs and WebCrawler now supports for individual URLs to be followed right away even if they were already visited. They will not be scheduled, but processed.
I needed to implement this because I found a site that used a common URL for redirections and based content on it's internal session or something I could't figure out.
Even if I managed to schedule visited URLs again, after scheduling all'em showed the same content: the one referenced in the last "previous page" visited. After allowing the crawler to visit sites inmediatly, the problem was solved.
Since this can generate non-desired infinite redirection loop, there's a maximum automatic redirection depth that can be configured on WebURLs: maxInmediateRedirects.
By default, this vehaviour is disabled. The creator of the WebURL is responsible of enabling it on a per-URL basis