Add bot detection bypass to prevent false bot flags#116
Open
Masonatorr wants to merge 1 commit intoForty-Bot:masterfrom
Open
Add bot detection bypass to prevent false bot flags#116Masonatorr wants to merge 1 commit intoForty-Bot:masterfrom
Masonatorr wants to merge 1 commit intoForty-Bot:masterfrom
Conversation
Adds custom header X-Not-A-Bot to bypass bot/scraper detection for legit requests originating from Chromium based browsers (specifically from browser extensions). This would prevent legitimate requests from receiving error 403 while still blocking most if not all scraper requests. Also update API docs to give more info on 403 errors and this new header. Signed-off-by: Mason Burns masonatortf@gmail.com
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
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.
Adds custom header X-Not-A-Bot to bypass bot/scraper detection for legit requests originating from Chromium based browsers (specifically from browser extensions). This would prevent legitimate requests from receiving error 403 while still blocking most if not all scraper requests. Also update API docs to give more info on 403 errors and this new header, talking about what exactly causes a 403 error to be returned and how it can be avoided. This should help people using the API for the first time who may have trouble with 403 errors due to Chrome/Chromium.
Signed-off-by: Mason Burns masonatortf@gmail.com