A pool manager is an abstraction for a collection of ConnectionPools.
If you need to make requests to multiple hosts, then you can use a
PoolManager, which takes care of maintaining your pools
so you don’t have to.
The API of a PoolManager object is similar to that of a
ConnectionPool, so they can be passed around interchangeably.
The PoolManager uses a Least Recently Used (LRU) policy for discarding old
pools. That is, if you set the PoolManager num_pools to 10, then after
making requests to 11 or more different hosts, the least recently used pools
will be cleaned up eventually.
Cleanup of stale pools does not happen immediately but can be forced when used as a context manager.
You can read more about the implementation and the various adjustable variables
within RecentlyUsedContainer.
- class urllib3.poolmanager.PoolManager(num_pools: int = 10, headers: Mapping[str, str] | None = None, **connection_pool_kw: Any)[source]¶
Allows for arbitrary requests while transparently keeping track of necessary connection pools for you.
- Parameters:
num_pools – Number of connection pools to cache before discarding the least recently used pool.
headers – Headers to include with all requests, unless other headers are given explicitly.
**connection_pool_kw – Additional parameters are used to create fresh
urllib3.connectionpool.ConnectionPoolinstances.Example:
import urllib3 http = urllib3.PoolManager(num_pools=2) resp1 = http.request("GET", "https://google.com/") resp2 = http.request("GET", "https://google.com/mail") resp3 = http.request("GET", "https://yahoo.com/") print(len(http.pools)) # 2
- clear() None[source]¶
Empty our store of pools and direct them all to close.
This will not affect in-flight connections, but they will not be re-used after completion.
- connection_from_context(request_context: dict[str, Any]) HTTPConnectionPool[source]¶
Get a
urllib3.connectionpool.ConnectionPoolbased on the request context.
request_contextmust at least contain theschemekey and its value must be a key inkey_fn_by_schemeinstance variable.
- connection_from_host(host: str | None, port: int | None = None, scheme: str | None = 'http', pool_kwargs: dict[str, Any] | None = None) HTTPConnectionPool[source]¶
Get a
urllib3.connectionpool.ConnectionPoolbased on the host, port, and scheme.If
portisn’t given, it will be derived from theschemeusingurllib3.connectionpool.port_by_scheme. Ifpool_kwargsis provided, it is merged with the instance’sconnection_pool_kwvariable and used to create the new connection pool, if one is needed.
- connection_from_pool_key(pool_key: PoolKey, request_context: dict[str, Any]) HTTPConnectionPool[source]¶
Get a
urllib3.connectionpool.ConnectionPoolbased on the provided pool key.
pool_keyshould be a namedtuple that only contains immutable objects. At a minimum it must have thescheme,host, andportfields.
- connection_from_url(url: str, pool_kwargs: dict[str, Any] | None = None) HTTPConnectionPool[source]¶
Similar to
urllib3.connectionpool.connection_from_url().If
pool_kwargsis not provided and a new pool needs to be constructed,self.connection_pool_kwis used to initialize theurllib3.connectionpool.ConnectionPool. Ifpool_kwargsis provided, it is used instead. Note that if a new pool does not need to be created for the request, the providedpool_kwargsare not used.
- request(method: str, url: str, body: bytes | IO[Any] | Iterable[bytes] | str | None = None, fields: Sequence[Tuple[str, str | bytes | Tuple[str, str | bytes] | Tuple[str, str | bytes, str]] | RequestField] | Mapping[str, str | bytes | Tuple[str, str | bytes] | Tuple[str, str | bytes, str]] | None = None, headers: Mapping[str, str] | None = None, json: Any | None = None, **urlopen_kw: Any) BaseHTTPResponse¶
Make a request using
urlopen()with the appropriate encoding offieldsbased on themethodused.This is a convenience method that requires the least amount of manual effort. It can be used in most situations, while still having the option to drop down to more specific methods when necessary, such as
request_encode_url(),request_encode_body(), or even the lowest levelurlopen().
- request_encode_body(method: str, url: str, fields: Sequence[Tuple[str, str | bytes | Tuple[str, str | bytes] | Tuple[str, str | bytes, str]] | RequestField] | Mapping[str, str | bytes | Tuple[str, str | bytes] | Tuple[str, str | bytes, str]] | None = None, headers: Mapping[str, str] | None = None, encode_multipart: bool = True, multipart_boundary: str | None = None, **urlopen_kw: str) BaseHTTPResponse¶
Make a request using
urlopen()with thefieldsencoded in the body. This is useful for request methods like POST, PUT, PATCH, etc.When
encode_multipart=True(default), thenurllib3.encode_multipart_formdata()is used to encode the payload with the appropriate content type. Otherwiseurllib.parse.urlencode()is used with the ‘application/x-www-form-urlencoded’ content type.Multipart encoding must be used when posting files, and it’s reasonably safe to use it in other times too. However, it may break request signing, such as with OAuth.
Supports an optional
fieldsparameter of key/value strings AND key/filetuple. A filetuple is a (filename, data, MIME type) tuple where the MIME type is optional. For example:fields = { 'foo': 'bar', 'fakefile': ('foofile.txt', 'contents of foofile'), 'realfile': ('barfile.txt', open('realfile').read()), 'typedfile': ('bazfile.bin', open('bazfile').read(), 'image/jpeg'), 'nonamefile': 'contents of nonamefile field', }When uploading a file, providing a filename (the first parameter of the tuple) is optional but recommended to best mimic behavior of browsers.
Note that if
headersare supplied, the ‘Content-Type’ header will be overwritten because it depends on the dynamic random boundary string which is used to compose the body of the request. The random boundary string can be explicitly set with themultipart_boundaryparameter.
- request_encode_url(method: str, url: str, fields: Sequence[Tuple[str, str | bytes]] | Mapping[str, str | bytes] | None = None, headers: Mapping[str, str] | None = None, **urlopen_kw: str) BaseHTTPResponse¶
Make a request using
urlopen()with thefieldsencoded in the url. This is useful for request methods like GET, HEAD, DELETE, etc.
- urlopen(method: str, url: str, redirect: bool = True, **kw: Any) BaseHTTPResponse[source]¶
Same as
urllib3.HTTPConnectionPool.urlopen()with custom cross-host redirect logic and only sends the request-uri portion of theurl.The given
urlparameter must be absolute, such that an appropriateurllib3.connectionpool.ConnectionPoolcan be chosen for it.
ProxyManager is an HTTP proxy-aware subclass of PoolManager.
It produces a single
HTTPConnectionPool instance for all HTTP
connections and individual per-server:port
HTTPSConnectionPool instances for tunnelled
HTTPS connections.
Example using proxy authentication:
>>> headers = urllib3.make_headers(proxy_basic_auth='myusername:mypassword')
>>> proxy = urllib3.ProxyManager('http://localhost:3128', proxy_headers=headers)
>>> r = proxy.request('GET', 'http://example.com/')
>>> r.status
200
- class urllib3.poolmanager.ProxyManager(proxy_url: str, num_pools: int = 10, headers: Mapping[str, str] | None = None, proxy_headers: Mapping[str, str] | None = None, proxy_ssl_context: ssl.SSLContext | None = None, use_forwarding_for_https: bool = False, proxy_assert_hostname: None | str | Literal[False] = None, proxy_assert_fingerprint: str | None = None, **connection_pool_kw: Any)[source]¶
Behaves just like
PoolManager, but sends all requests through the defined proxy, using the CONNECT method for HTTPS URLs.
- Parameters:
proxy_url – The URL of the proxy to be used.
proxy_headers – A dictionary containing headers that will be sent to the proxy. In case of HTTP they are being sent with each request, while in the HTTPS/CONNECT case they are sent only once. Could be used for proxy authentication.
proxy_ssl_context – The proxy SSL context is used to establish the TLS connection to the proxy when using HTTPS proxies.
use_forwarding_for_https – (Defaults to False) If set to True will forward requests to the HTTPS proxy to be made on behalf of the client instead of creating a TLS tunnel via the CONNECT method. Enabling this flag means that request and response headers and content will be visible from the HTTPS proxy whereas tunneling keeps request and response headers and content private. IP address, target hostname, SNI, and port are always visible to an HTTPS proxy even when this flag is disabled.
proxy_assert_hostname – The hostname of the certificate to verify against.
proxy_assert_fingerprint – The fingerprint of the certificate to verify against.
Example:
import urllib3 proxy = urllib3.ProxyManager("https://localhost:3128/") resp1 = proxy.request("GET", "https://google.com/") resp2 = proxy.request("GET", "https://httpbin.org/") print(len(proxy.pools)) # 1 resp3 = proxy.request("GET", "https://httpbin.org/") resp4 = proxy.request("GET", "https://twitter.com/") print(len(proxy.pools)) # 3