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

Get rid of requests library #3

Open
krizhanovsky opened this issue Oct 1, 2023 · 1 comment
Open

Get rid of requests library #3

krizhanovsky opened this issue Oct 1, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@krizhanovsky
Copy link
Contributor

krizhanovsky commented Oct 1, 2023

Since it's not trivial to get response status code from Selenium, at the moment we use requests to get the status. This increases requests rate and reveals the robotic nature of the bot. We need to do everything with Selenium only. To achieve this we can parse the page body and/or get (intercept) data from the socket layer.

@krizhanovsky krizhanovsky added the enhancement New feature or request label Oct 1, 2023
@krizhanovsky
Copy link
Contributor Author

One more thing I discovered in the current usage of requests is that it uses HTTP/1. It can not fetch any of the resources from our website, e.g.

WARNING:root:BROKEN LINK https://tempesta-tech.com/blog/ on https://tempesta-tech.com/ (can not connect)

and there is

28735.672417] [tempesta tls] Warning: [::ffff:31.221.30.162] ClientHello: cannot find matching ALPN for http/1.1

on Tempesta FW side.

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

No branches or pull requests

1 participant