-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following domain redirects #3
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that in cases where a redirect occurs for the domain, the current logic won't adjust to the new location. This results in a null JARM hash.
When running the alexa500 list here is an example of a failed resolution.
163.com redirects to www.163.com when visited. When its run again with the redirect URL:
Maybe we can have a follow redirect option that performs a pre-check to get the actual URL that should be scanned?
The text was updated successfully, but these errors were encountered: