Protocol and sticky sessions for Residential Proxies (Legacy)

​

Choosing a Protocol: HTTP or HTTPS

http://<YOUR_USERNAME>:<YOUR_PASSWORD>@superproxy.zenrows.com:1337

https://<YOUR_USERNAME>:<YOUR_PASSWORD>@superproxy.zenrows.com:1338

​

Example: Using Both Ports

proxy_username = "YOUR_USERNAME"
proxy_password = "YOUR_PASSWORD"
proxy_domain = "superproxy.zenrows.com"

proxies = {
    "http": f"http://{proxy_username}:{proxy_password}@{proxy_domain}:1337",
    "https": f"https://{proxy_username}:{proxy_password}@{proxy_domain}:1338",
}

import requests
response = requests.get("https://www.scrapingcourse.com/ecommerce/", proxies=proxies)
print(response.status_code)

​

Why Use Sticky TTL?

• Maintain the same IP for a set period, from 30 seconds up to 1 day.
• Ensure session consistency for workflows that require login or multi-step navigation.
• Reduce the risk of bans or captchas by mimicking real user behavior.

​

How to Enable Sticky Sessions

​

Example: 30-Second Sticky Session

http://<YOUR_USERNAME>:<YOUR_PASSWORD>_ttl-30s_session-1cLiFzDgsq36@superproxy.zenrows.com:1337

• ttl-30s ensures the IP will be retained for 30 seconds.
• session-1cLiFzDgsq36 is a random session identifier that you can generate yourself. You can use any combination of letters and numbers, similar in length and style to the example. This allows Zenrows to allocate the same IP for multiple requests as long as you use the same session ID.

​

Available Sticky TTL Values

• 30 seconds: ttl-30s
• 1 minute: ttl-1m
• 30 minutes: ttl-30m
• 1 hour: ttl-1h
• 1 day: ttl-1d

​

Best Practices

• Use sticky sessions for login-required flows, shopping carts, or any scenario where the same IP is needed across requests.
• Choose the shortest TTL that meets your needs to maximize IP pool rotation and avoid detection.
• Always generate a unique session ID for each session to prevent conflicts.
• Match the port to the protocol you’re connecting with (1337 for HTTP, 1338 for HTTPS), unless your client tunnels both through the HTTP port.

​

Troubleshooting

• If you observe frequent IP changes, double-check your TTL and session ID format.
• Some websites may require longer TTLs for certain workflows; experiment with different values to find the best fit.
• If your connection fails on port 1338, confirm your client supports connecting directly to an HTTPS proxy endpoint, then fall back to port 1337.