Python Requests Proxy Setup: HTTP, SOCKS5 and Connection Reuse

Build the client in six steps

1. 1

   Install the client in an isolated environment

   Create a project environment and install Requests there rather than modifying a shared system Python. Include the optional SOCKS dependencies if you plan to test SOCKS5. Record the resolved package versions in your application’s dependency workflow. A successful installation only confirms client readiness; it does not validate account balance, region inventory or proxy credentials. Keep the test script small enough that another teammate can reproduce it with their own authorized connection details.

   python -m pip install "requests[socks]"

2. 2

   Make one authenticated HTTP-proxy request

   The proxy mapping keys select the destination scheme. An HTTPS target can therefore use an HTTP proxy URL: the key remains https while the proxy URL describes the gateway protocol. Copy the host and port from the console, preserve the complete generated username and enter the password interactively. Encode username and password as URL components so reserved characters do not change the address. Proxy authentication belongs in the proxy URL here; the request auth parameter would authenticate to the destination instead.

   from getpass import getpassfrom urllib.parse import quoteimport requests host = input("Proxy host from your console: ").strip()port = int(input("Proxy port from your console: "))username = input("Full generated proxy username: ")password = getpass("Proxy password: ")target = input("HTTPS test URL you control: ").strip()if not target.startswith("https://"):    raise ValueError("Use an HTTPS test target") userinfo = f"{quote(username, safe='')}:{quote(password, safe='')}"proxy_url = f"http://{userinfo}@{host}:{port}"proxies = {"http": proxy_url, "https": proxy_url} with requests.Session() as client:    try:        with client.get(target, proxies=proxies, timeout=(5, 20)) as response:            print("status:", response.status_code)            print("header_seconds:", response.elapsed.total_seconds())            response.raise_for_status()    except requests.exceptions.RequestException as error:        print("request_failed:", type(error).__name__)        # Do not print authenticated URLs or complete exception messages.

3. 3

   Choose SOCKS5 DNS deliberately

   For the SOCKS comparison, use the SOCKS-enabled host and port from the selected access. socks5 resolves the destination name on the client; socks5h delegates that lookup to the proxy. Pick the behavior required by the test and record it. A proxy-side lookup does not alone prove country targeting, and a DNS difference can change which destination server responds. Repeat the same owned test with the selected mode, rather than changing credentials, region and target simultaneously. Requests SOCKS documentation explains this distinction.

   # Use the host and port enabled for SOCKS5 in your console.proxy_url = f"socks5h://{userinfo}@{host}:{port}"proxies = {"http": proxy_url, "https": proxy_url}

4. 4

   Set separate connect and read timeouts

   The example timeout=(5, 20) gives connect and read limits in seconds. These numbers are starting points for a controlled test, not a universal KAIROXO setting. The read limit concerns waiting for incoming data; the tuple is not a guaranteed total job deadline. Give the surrounding task its own overall budget, cancellation policy and maximum attempts. Note which failure class occurred before changing limits, because increasing a timeout cannot repair a wrong password or an expired endpoint.

5. 5

   Reuse a Session without assuming a fixed exit

   A Session can retain cookies and reuse eligible connections. Keep it within a context manager, finish or close responses and reuse it for the intended logical task. In the example, the default response download completes before the next request. Connection reuse is a client behavior; it does not guarantee the proxy keeps the same exit IP. Verify exit continuity separately and choose supported session settings. Keep independent user flows in separate Sessions so cookie state does not silently cross tasks.

   # Use the same proxies mapping for this controlled test.with requests.Session() as client:    for index in range(2):        try:            with client.get(target, proxies=proxies, timeout=(5, 20)) as response:                print("check:", index + 1, "status:", response.status_code)                response.raise_for_status()        except requests.exceptions.RequestException as error:            print("request_failed:", type(error).__name__)            break

6. 6

   Verify the result before adding concurrency

   Check the destination’s observed connecting address, expected page or API fields, response status and run timestamps. The printed elapsed value covers response-header timing rather than a complete workload benchmark. Compare at least two controlled requests and keep the protocol, region and target constant. If the result differs from curl, inspect per-request proxies, local environment routing, DNS choice and certificates. Do not solve a failing baseline by immediately adding workers or rotating through more endpoints.