Added ability to set the maximum redirects #503
Merged
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.
So I am building a web scraper and I noticed sometimes it will follow a long set of redirects, probably from a scam website or something. But I looked at the documentation and the maximum redirects that HttpWebRequest and HttpClientHandler will follow is 50 by default. I think this is too much so I added the ability to adjust the maximum number of redirects that will be followed. This is so I can save on bandwidth and compute power.
When the redirect limit is hit,
HtmlWeb.StatusCode
will be a 3xx status code. If the resource is reached before the redirect limit, then it will be a 2xx status code.HttpWebRequest.MaximumAutomaticRedirections Property
HttpClientHandler.MaxAutomaticRedirections Property