**Sticky IP sessions** allow you to maintain the same IP address across multiple requests, which is critical for workflows that require session continuity—such as logging in, cart management, or multi-step forms. This approach reduces the risk of triggering anti-bot defenses tied to sudden IP changes.
## **Understanding sticky IPs** **Sticky IPs** (also known as _session_ or _persistent proxies_) allow a single IP address to be used consistently over a period of time, preserving continuity across multiple HTTP or browser requests. **Use cases that require sticky sessions include:** - Multi-step form submissions - E-commerce add-to-cart + checkout flows - Logging into accounts and accessing personalized dashboards - Simulating user behavior or bot profiles - Social media automation that must mimic real users
## **Squid Proxies sticky IP behavior overview** | Proxy Type | Format | Stickiness | Rotation Style | Notes | |--------------------|---------------------------|----------------|-----------------------|--------------------------------------| | Datacenter Proxies | IP:PORT | Fully sticky | Manual | Persistent until you change it | | Residential Proxies| HOST:PORT (e.g., p102...) | Semi-sticky | Automatic (~10 mins) | IP is sticky for ~10 minutes per port|
## **Datacenter proxies – full control sticky sessions** Datacenter proxies from Squid Proxies are static by default. You are assigned a pool of IP:PORT endpoints, and each one is fully sticky as long as you continue using it. No automatic rotation occurs unless you change the IP manually. ```python proxies = { "http": "http://username:password@123.45.67.89:3128", "https": "http://username:password@123.45.67.89:3128" } ``` **Best Practices:** - Assign one static IP per session or user to avoid overlap - Use per-thread isolation if running concurrent tasks - Reuse the same IP throughout your session lifecycle This gives full control for long-running workflows or predictable client-server handshakes.
## **Residential proxies – 10-minute sticky rotation** Squid Proxies’ residential proxies automatically rotate every ~10 minutes. However, if you reuse the same host:port endpoint, you’ll get the same IP for the duration of the sticky session window (approx. 8–10 minutes). ```python proxies = { "http": "http://p102.squidproxies.com:8907", "https": "http://p102.squidproxies.com:8907" } ``` - If you persist this connection or socket, the IP will remain the same - After ~10 minutes, a new IP will be issued automatically
## **Implementing sticky sessions in code** ### **Using `requests.Session()` (Python)** ```python import requests session = requests.Session() session.proxies = { "http": "http://p102.squidproxies.com:8907", "https": "http://p102.squidproxies.com:8907" } session.headers.update({"User-Agent": "Mozilla/5.0"}) response = session.get("https://target.com/profile") ```
## **Browser automation with sticky IPs & sessions** ### **Selenium (Python)** ```python from selenium import webdriver options = webdriver.ChromeOptions() options.add_argument('--proxy-server=http://p102.squidproxies.com:8907') driver = webdriver.Chrome(options=options) driver.get("https://target.com/login") ``` To maintain session continuity, reuse the same browser context or instance for multiple actions.
## **Extending residential sticky sessions beyond 10 minute** You **cannot** force Squid Proxies residential IPs to persist beyond the rotation window, but you can: - Complete the workflow within the 10-minute window - Detect IP changes and handle re-login automatically - Store cookies and tokens client-side - Use watchdogs to monitor public IP and reinitialize session state
## **Proxy authentication recap** | Method | Usage | |------------------|----------------------------------------| | IP Whitelisting | Recommended; faster, no credentials | | Username/Password| Use when IP is dynamic or remote |
## **Thread-level sticky session handling** When scraping or automating at scale: - Assign one proxy + session object per thread or user - Never share proxy instances across concurrent users ```python from threading import Thread def run_task(proxy): session = requests.Session() session.proxies.update({"http": proxy, "https": proxy}) session.get("https://example.com") threads = [] for proxy in proxy_list: t = Thread(target=run_task, args=(proxy,)) t.start() threads.append(t) for t in threads: t.join() ```
## **Common sticky proxy issues** | Issue | Cause | Solution | |---------------------------|---------------------------------------------|-------------------------------------------| | IP changed mid-session | Exceeded 10-minute rotation window | Complete session faster or reinitiate | | Session dropped (residential)| Lost sticky window due to port reuse | Persist same host:port per session | | IP collision (datacenter) | Reusing same IP across users/threads | Use pool assignment and isolate properly | | DNS leaks | Client not routing traffic correctly | Enable DNS-over-HTTPS or proxy-aware DNS |
## **Verifying sticky session functionality** ```bash curl -x http://p102.squidproxies.com:8907 https://httpbin.org/ip ``` Use browser dev tools to inspect: - IP consistency - Cookie reuse - Login persistence - Headers and session continuity
## **Best practices for sticky proxy sessions** | Scenario | Proxy Type | Recommended Approach | |-----------------------------|--------------|-----------------------------------------------| | Login + dashboard workflows | Residential | Reuse same port for under 10 mins | | Long-running scraping tasks | Datacenter | Use static IP from assigned pool | | Parallel users or threads | Both | Assign 1 proxy per user/thread | | Mobile or local testing | Residential | Combine with geo-targeted pools | | Cookie-dependent automations| Both | Reuse sessions and persist cookies |
---
**More Guides:** - [Custom Headers & Fingerprinting](https://www.squidproxies.com/developer-docs/dev-advanced-guides/custom-headers-and-fingerprinting) - [Geo-Targeting: Pool IPs vs Headers](https://www.squidproxies.com/developer-docs/dev-advanced-guides/geo-targeting-pool-ips-vs-headers)