How to Set Up Proxy in Python Requests: Session, Env, SOCKS5

Per-request configuration

import requests
proxy_url = "http://USERNAME:PASSWORD@HOST:PORT"
proxies = {"http": proxy_url, "https": proxy_url}
response = requests.get("https://TARGET.EXAMPLE", proxies=proxies, timeout=(5, 20))
response.raise_for_status()

This form keeps the setting local to one request. Use separate URLs only when the assigned HTTP and HTTPS endpoint settings differ.

Use a tuple timeout to separate connection setup from response reading. A short connect timeout catches unreachable endpoints; a reasonable read timeout gives the permitted target time to respond without allowing the process to hang indefinitely.

Session configuration

import requests
session = requests.Session()
session.proxies.update({"http": proxy_url, "https": proxy_url})
response = session.get("https://TARGET.EXAMPLE", timeout=(5, 20))
response.raise_for_status()

A Session is useful when several authorized requests should share proxy settings and connection state. Close it with a context manager in longer-running code.

A Session can also retain cookies and headers. That is useful only when the authorized workflow needs the same state. For independent samples, create separate Sessions and label each result instead of silently carrying state forward.

Environment variables

# Set these in the runtime environment, not in the repository
HTTP_PROXY=http://USERNAME:PASSWORD@HOST:PORT
HTTPS_PROXY=http://USERNAME:PASSWORD@HOST:PORT

Environment variables are convenient for tools that should inherit one setting, but they are broader than a per-request dictionary. Keep them out of committed configuration files and clear them when the task ends.

Environment variables are convenient in deployment systems, but inherited values can surprise tests and child processes. Log only whether a variable is present, never its full value, and remove it after the scoped task.

Before choosing, confirm whether this task needs a continuous review window or several independent samples.

Static residential addresses serve continuity. Dynamic residential addresses serve independent samples. Neither should be presented as an outcome guarantee.

For more detail, see the static residential proxy guide, the dynamic residential proxy guide, and current IPIPD pricing.

Use the official Requests proxy documentation to verify command and parameter behavior.

After the check: SOCKS5 and DNS behavior

python -m pip install "requests[socks]"
proxies = {
"http": "socks5h://USERNAME:PASSWORD@HOST:PORT",
"https": "socks5h://USERNAME:PASSWORD@HOST:PORT",
}

Use socks5 for local DNS resolution and socks5h when resolution should go through the proxy endpoint. Use only the protocol actually assigned to the account.

Installing requests[socks] adds the optional SOCKS transport dependency. It does not prove that the assigned endpoint supports SOCKS5; the scheme in code must match the protocol actually supplied for the account.

Timeouts, exceptions, and exit verification

import requests
try:
r = requests.get("https://IP-ECHO.EXAMPLE", proxies=proxies, timeout=(5, 20))
r.raise_for_status()
print(r.text)
except requests.exceptions.ProxyError:
print("Check endpoint protocol, host, port, and authentication")
except requests.exceptions.Timeout:
print("The connect or read timeout expired")
except requests.exceptions.RequestException as exc:
print(type(exc).name)

Do not print URLs or exception details that may contain secrets. Record the permitted response, status, time, endpoint label, and rollback action.

Use these examples only for authorized public-page checks and connection testing. Use the protocol and credentials assigned to the account. IPIPD product wording here is limited to static residential addresses and dynamic residential addresses; no access or platform outcome is promised.

Handle ProxyError, Timeout, and the broader RequestException separately so the operator knows whether to inspect endpoint fields, timing, or the target response. Keep exception output free of credentials and full proxy URLs.

Handoff Record for the Python Runtime

The Python handoff should preserve Python and Requests versions, dependency installation, configuration scope, timeout tuple, exception class, and Session shutdown method. The repository keeps dummy field values only; a protected runtime configuration assembles the authenticated URL.

The reviewer must identify whether the program uses a per-request proxies dictionary, Session.proxies, or inherited environment variables. Environment variables may affect child processes, while a Session may retain cookies and headers, so each needs a deliberate cleanup step.

Keep network configuration separate from business logic and test against one fixed authorized public target. Static residential addresses fit one continuous review condition; dynamic residential addresses fit separately labeled samples. Exception logs must not print the full proxy URL.

The final record should also name the exit verification endpoint, response status, timing, and rollback action. If protocol, secret source, target permission, or returned content cannot be confirmed, stop the program and close the Session instead of increasing concurrency or target scope.