Skip to content
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

[Feature Request] Update User-Agent String (web_agent_string) to avoid tripping online WAFs #95

Open
TAbdiukov opened this issue Aug 8, 2024 · 2 comments

Comments

@TAbdiukov
Copy link

Update User-Agent String (web_agent_string) to avoid tripping online WAFs, resulting in more websites being accessible

@ScholliYT
Copy link
Owner

What exactly do you mean by "update"?
Increase the version numbers of the Browsers mentioned in the default string?

@TAbdiukov
Copy link
Author

TAbdiukov commented Aug 9, 2024

Thanks for your swift response!

The way I do it is: I download the latest Google Chrome browser, and then use one of many online services to get User-Agent String.

At the time of writing this comment, it is Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36

Chrome 60 (whose User-Agent string is used) came out in 2017, so I believe it may trip trip WAFs or silent captcha (e.g., Google reCaptcha v3). But user-agent isn't the only thing that can trip them (bad IP addresses also can, and probably Github Actions IP addresses are already blacklisted at places). But browsers update often, and there's no need to update User-Agent string every time the browser updates, but it's a good practice to do it maybe once at least half a decade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants