Skip to main content
All CollectionsDashboardSOAX rotation
Session control for ISP proxies
Session control for ISP proxies
Kate avatar
Written by Kate
Updated over a week ago

The sticky session allows you to keep the same IP address with a specified session length (up to 24 hours) to run multiple requests and be able to change them when needed.

Also can use rotation settings in the dashboard. More info here.

Setting a sticky sessions connection

SOAX offers ISP proxy access through a single endpoint:

Sticky sessions work with the parameters described below:

  • package_id - package id can be found on the left top corner of your package card

  • country - country code to target United States location : us

  • sessionid - a random string to create a session in order to keep the same proxy for more than one request. If this parameter is not indicated (along with sessionlength), you will get new IP on every request you make. Example: rand123456

  • sessionlength - must be used with sessionid. Specifies the sticky session time in seconds – from 0 seconds up to 86400 sec (24 hours). If you don’t indicate sessionlength, a session will last 180 sec. Example: 90

To build sticky sessions, you need to add the parameters described above along with package-id and login (package_key): package-{package_id}-country-us-sessionid-{session_id}-sessionlength-{time_in_sec}:{package_key}

Use the Session ID only if you want a sticky session. Otherwise, just ignore that part to receive a rotating proxy with a specified Session length.

How sticky sessions work

  1. To force an IP change, just modify the sessionid

  2. Sticky sessions work only at port 5000 with endpoint

  3. You can start as many parallel connections using sessions as you want. To do that, just use a different random string sessionid.

  4. If you keep sending requests to the same sessionid, you can maintain the same IP for any amount of time within the set sessionlength.

  5. If an assigned to the session node IP becomes unavailable, the proxy server will return the error “502 — Node is not available” and the new IP will be assigned in 60 seconds if the IP didn’t return.

  6. The session automatically expires in 60 seconds of inactivity. After that, a new IP will be assigned to this session’s ID. To keep this IP longer, send a tiny keep-alive request every 30 seconds to prevent this session from becoming idle for over a minute.

  7. While IP is assigned to a specified sessionid it can not be assigned to another sessionid. Therefore, IPs in parallel active sessions cannot overlap.

  8. If you do not indicate sessionid and sessionlength you will get new IP on every request you make.

  9. sessionlength – must be used with sessionid otherwise, you will get an error from the proxy server.

Examples of using Sticky sessions

United States proxy with new IP on each request package-{package_id}-country-us:{login}

United States proxy with sticky sessions (using session ID) and default session length in 180 sec package-{package_id}-country-us-sessionid-{session_id}:{login}

United States proxy with sticky sessions (using session ID) and custom session length package-{package_id}-country-us-sessionid-{session_id}-sessionlength-{time_in_sec}:{login}

An example represents a list of credentials that establish different sessions in different countries with different sessions length (seconds).

[](<>) package-64412-country-us-sessionid-rand123456-sessionlength-90:PFh4Nm42Boe6hcJ0 [](<>) package-64412-country-uk-sessionid-tsa122-sessionlength-180:PFh4Nm42Boe6hcJ0 [](<>) package-64412-country-br-sessionid-rwaf123122-sessionlength-86400:PFh4Nm42Boe6hcJ0

To connect to sessions in the 3-rd party tools, you need to use the next credentials without <> symbols :

Login: package-<your package id>-country-<code>-sessionid-<session_id>-sessionlength-<time_in_sec> Pass: <your package login>
Domain: Port: 5000

Did this answer your question?