-
Notifications
You must be signed in to change notification settings - Fork 168
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
Keep-alive is disabled when using SOCKS #716
Comments
Hi @HirbodBehnam, welcome to ureq! Thanks for reporting this. Must be something about the connection pooling that isn't happening under socks5. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello
I've discovered that if you use socks5 proxy when building the Agent,
ureq
will instantiate a new connection for each request. However, when not using proxy, it will simply keep the connection and use the keep alive feature. I've also checkedreqwest
and apparently, that library does not have an issue and keeps the proxied connection alive.I've written two small functions to test demonstrate it:
You can check it with wireshark to see that it instantiates a new connection for each request. Tested with reqwest 0.11.24 and ureq 2.9.4.
The text was updated successfully, but these errors were encountered: