You might need a newer version of Requests. I just tried it with v2.5.1: from requests.packages.urllib3.util import Retry Seems to work. FYI: The latest version is v2.5.3, worth upgrading. Also if you have a reasonably recent version of urllib3 installed separately, this should also work: from urllib3.util import Retry Unfortunately we check the specific isinstance … Read more
I wrote an article about this. pasted it here: Requests’ secret: pool_connections and pool_maxsize Requests is one of the, if not the most well-known Python third-party library for Python programmers. With its simple API and high performance, people tend to use requests instead of urllib2 provided by standard library for HTTP requests. However, people who … Read more
In urllib3 POST is not allowed as a retried method by default (since it can cause multiple inserts). You can force it though: Retry(total=3, allowed_methods=frozenset([‘GET’, ‘POST’])) See https://urllib3.readthedocs.io/en/latest/reference/urllib3.util.html#urllib3.util.retry.Retry
I would use a retry decorator. There are other ones out there, but this one works pretty well. Here’s how you can use it: @retry(urllib2.URLError, tries=4, delay=3, backoff=2) def urlopen_with_retry(): return urllib2.urlopen(“http://example.com”) This will retry the function if URLError is raised. Check the link above for documentation on the parameters, but basically it will retry … Read more
There can be multiple possible solutions to this problem. There are a multitude of answers on StackOverflow for any of these, so I will try to combine them all to save you the hassle of searching for them. In my search I have uncovered the following layers to this: First, try logging For many problems, … Read more
The reason why the error message mentioned OpenSSL 1.1.1+ and LibreSSL 2.8.3 is that urllib3 v2.0 ( version you’ve installed) requires OpenSSL 1.1.1+ to work properly, as it relies on some new features of OpenSSL 1.1.1. The issue is that the version of the ‘ssl’ module that is currently installed in your environment is compiled … Read more
Requests uses Keep-Alive by default. Resetting dropped connection, from my understanding, means a connection that should be alive was dropped somehow. Possible reasons are: Server doesn’t support Keep-Alive. There’s no data transfer in established connections for a while, so server drops connections. See https://stackoverflow.com/a/25239947/2142577 for more details.
as a work around: pip install urllib3==1.25.11
This is actually an issue with urllib3, not with pyopenssl. Debian lately compiles OpenSSL without SSLv3 support, and urllib3 just assumed that support was there. The issue was fixed in commit b9b3b0102 which is part of the 1.10 release of urllib3. As you are using urllib3 as part of requests, which in turn is used … Read more
No data is being lost! The connection is being discarded after the request is completed (because the pool is full, as mentioned). This means that this particular connection is not going to be re-used in the future. Because a urllib3 PoolManager reuses connections, it will limit how many connections are retained per hos to avoid … Read more