When using our service, it's important to understand how to manage sessions effectively. This guide will walk you through three key parameters that control how long a node stays connected to a session. These parameters are optional and can be adjusted to suit your needs.
A node is a unique connection point that gives you an IP address to browse the internet securely and anonymously.
1. Session duration (sessionlength)
The sessionlength parameter determines how long a session lasts. Once the time expires, the session will automatically end, and the node will be rotated.
Default value: 360 seconds (6 minutes)
You can increase this value for longer tasks. For example, setting sessionlength=3600 will keep the session active for 1 hour.
Important note:
If you want a new IP address on each request, you should either set sessionlength=0 or remove the session_id from the URL. This ensures the node is rotated after every request, providing you with a fresh IP every time.
Use case:
Need to keep the same IP address while completing tasks like logging into a website? Set a custom sessionlength to maintain consistency for as long as needed.
2. Binding time to live (bindttl)
The bindttl parameter controls how long a node remains connected to the session, even if an error occurs.
Default behavior: Without setting
bindttl, the node will remain connected for the fullsessionlength, even if there are errors.Custom setting: You can set
bindttlto a specific number of seconds. For example,bindttl=1200means the node will stay connected for 1200 seconds after the last successful request. If an error happens after this time, the node will be released.
Use case:
If it's more important to stay connected to the same node (like when you're logged into an account), you can tolerate errors and avoid switching nodes unnecessarily.
3. Idle time to live (idlettl)
The idlettl parameter defines how long a node stays connected when there is no activity.
Default values:
900 seconds (15 minutes) for mobile and Wi-Fi connections
86400 seconds (24 hours) for ISP and data center connections
Use case:
If you need to pause activity but want to continue with the same node when you return, set a custom idlettl ensures the node stays connected during periods of inactivity.
Bringing it all together
These parameters give you full control over session management. For example, if you start a session with sessionlength=3600 (1 hour), bindttl=1200 (20 minutes), and idlettl=900 (15 minutes), you can maintain a stable session even during errors or inactivity.
curl -k -x "http://package-11111-sessionid-1-sessionlength-3600-bindttl-1200-idlettl-900-country-ca-isp-sasktel:[email protected]:5000" -L http://checker.soax.com/api/ipinfo
If you have any questions, don't hesitate to contact our support via live chat. We'll be sure to help!