Sticky-сесія
Проксі-сесія, що утримує один і той самий IP-адресу заданий проміжок часу замість ротації на кожен запит.
Sticky-сесія закріплює ваше з’єднання за одним IP на обраний вами строк - у нас це тридцять секунд, п’ятнадцять хвилин або година. Кожен запит протягом цього вікна виходить з того самого IP, через що трафік має вигляд єдиної користувацької сесії.
Сайти зі входом, кошиками покупок чи пагінацією залежать від безперервності сесії. Якщо IP змінюється посеред сесії, сайт може розлогінити вас, скинути кошик або почати віддавати порожні сторінки. Sticky-сесії це запобігають.
Sticky-сесії налаштовуються в параметрі імені користувача проксі. Більшість провайдерів використовують суфікс з ID сесії або тривалістю, що додається до імені користувача. Шлюз спрямовує всі запити з цим ID сесії через один IP, поки вікно не спливе.
Компроміс: довша sticky-сесія використовує один IP для більшої кількості запитів, що підвищує шанс, що IP позначать за підозрілу поведінку, якщо сайт відстежує частоту запитів на IP. Для агресивних цілей беріть вікно в тридцять секунд і піднімайте сесію заново між кроками задачі.
Після спливання sticky-сесії шлюз призначає новий IP автоматично. Не потрібно перепідключатися чи щось переналаштовувати - наступний запит просто отримує свіжий IP.
Holding one exit on purpose
A sticky session pins your traffic to a single exit address for a defined period. The provider records the association between your session identifier and the device that answered first, then routes everything carrying that identifier to the same place until the clock runs out.
The lifetime is a ceiling, not a guarantee. On residential exits the device belongs to somebody else, and when their connection drops the session ends early no matter what you asked for.
Sticky sessions exist because many tasks span several requests: a login and the redirect after it, a checkout, a search followed by a detail page. Rotating in the middle of those makes the site see two different visitors sharing one session cookie.
Three lifetimes and one identifier
You choose both the identifier and how long it holds. The identifier is any number you like:
Sticky syntax
login_c_US_s_42_ttl_30s half a minute
login_c_US_s_42_ttl_15m fifteen minutes
login_c_US_s_42_ttl_1h one hour, our maximum
# Different numbers mean different exits running in parallel:
login_c_US_s_1_ttl_15m ... login_c_US_s_200_ttl_15m- Pick the shortest lifetime that covers your task. Holding an exit longer than needed reduces the pool available to your other sessions.
- One hour is the ceiling because a residential device that stays online longer is the exception. Anything that must never change belongs on an ISP address.
- Use a different number per worker, profile or account. Two workers on one identifier share an exit and their behaviour merges.
- Handle the case where the session dies early. A retry that re-establishes the session is the difference between a robust job and a fragile one.
Misreadings of stickiness
Sticky is not static
It is a temporary lease on a rotating pool. Static addresses are a different product with a different price model.
The identifier is not a password
It only groups your own traffic. Anyone else using your login and the same number is you as far as the gateway is concerned.
Longer is not safer
A device that has been proxying for an hour is more likely to drop in the next minute than one that just came online.
It does not survive a client restart
The identifier does, the device may not. Expect a new address after a long pause.
Choosing a lifetime
Four options, counting the one where you ask for nothing. Pick the shortest that covers the task in front of you.
| What you append | How long it holds | Task it fits | What ends it early |
|---|---|---|---|
| nothing | no hold at all, a new exit per connection | listings, prices, search results | not applicable |
| _s_42_ttl_30s | half a minute | a login and the redirect that follows it | the device dropping offline |
| _s_42_ttl_15m | fifteen minutes | a checkout or a multi-step form | the device dropping offline |
| _s_42_ttl_1h | one hour, our ceiling | warming an account, long session work | the device dropping offline, most likely of the four |
The number after _s_ is yours to choose and it is what separates parallel sessions. Two workers sharing one number share one exit, and the site sees their behaviour as a single person doing two things at once.
Questions people actually type
What is a sticky session?
An instruction to the gateway to keep sending your traffic out through the same address for a set period, instead of picking a new exit on every connection.
How do I set one?
Append it to the username, not the host. login_c_US_s_42_ttl_15m holds one United States exit for fifteen minutes under session number 42. The password and the endpoint never change.
How long can a session last?
One hour with us. The ceiling is not a licensing limit, it is what residential devices actually do: they belong to people who close laptops and leave home networks, and an exit held for an hour is more likely to vanish in the next minute than one that just came online.
Is the lifetime guaranteed?
No, and treat any provider promising otherwise with suspicion. The lifetime is a ceiling. Write the retry that re-establishes the session, because that is the difference between a job that survives the night and one that does not.
Can I run many sticky sessions at once?
Yes, that is what the session number is for. Give each worker, browser profile or account its own number and they get separate exits in parallel. Reusing a number across workers merges their behaviour onto one address.
Sticky session or a dedicated address?
A sticky session is a temporary lease on a rotating pool, and it ends. If the address must never change, for an account you intend to keep, buy an ISP or datacenter address instead. Different product, different price model.
Пов'язані терміни
Дивись на практиці
Готовий використовувати sticky-сесія?
SotaProxy надає доступ до ротуючих резидентських, мобільних, дата-центр та ISP проксі. Без мінімальних платежів.
Почати