Feat: Randomize User-agent #258
Closed
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
|
The semantics aren't wrong but these requests are going to gotor and not the actual request to Tor. These changes would be better placed with |
|
If you want help moving this over to |
|
Any update on this? If not, I'm going to close it soon. |
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.
Issue DedSecInside/gotor#44
Changes Proposed
Explanation of Changes
-r or --randomizeoptions for randomize user-agent. If we set this argument, all of requests have randomized user-agent headers.Screenshots of new feature/change
Ps. I didn't checked it much, but It may works for all features.