Skip to content

docs: raise max sticky session TTL from 240 to 1440 minutes #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
valentin-naboka wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: raise max sticky session TTL from 240 to 1440 minutes #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion kb/technical/what-are-sticky-sessions-and-how-do-they-work.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Sticky sessions (session persistence) maintain the same proxy IP for multiple re

1. Duration:
- Default TTL: 15 minutes
- Maximum TTL: 240 minutes (4 hours)
- Maximum TTL: 1440 minutes (24 hours)
- Customizable via `sessionttl` parameter
- Static TTL: expires at creation time + TTL, not extended by activity

Expand Down
4 changes: 2 additions & 2 deletions ...echnical/what-is-the-difference-between-sticky-sessions-and-tcp-connections.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ When a TCP connection closes, it does **not** mean your sticky session has expir

A sticky session is a logical mapping between your session ID and a specific proxy node (IP address). It is tracked server-side and persists independently of TCP connections.

- **Default TTL**: 15 minutes (customizable up to 240 minutes via `sessionttl`)
- **Default TTL**: 15 minutes (customizable up to 1440 minutes via `sessionttl`)
- **TTL is static**: Set at creation time, not extended by subsequent requests
- **Scope**: All requests sharing the same session ID, regardless of how many TCP connections they use
- **Lifetime**: Minutes to hours, controlled by `sessionttl` parameter.
Expand Down Expand Up @@ -55,7 +55,7 @@ Within a single sticky session, many TCP connections can open and close — your
|---|---|---|
| **What it is** | Network socket between client and proxy | Logical IP-to-session mapping |
| **Idle timeout** | 30 seconds | None (static TTL) |
| **Max lifetime** | As long as data flows | 240 minutes (`sessionttl-240`) |
| **Max lifetime** | As long as data flows | 1440 minutes (`sessionttl-1440`) |

<Info>
The 30-second idle timeout applies to the TCP connection, not the session TTL. If your TCP connection closes due to inactivity, simply open a new connection with the same session ID — you will get the same IP as long as the session TTL has not expired.
Expand Down
4 changes: 2 additions & 2 deletions residential/sticky-sessions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: "We support session persistence (AKA sticky sessions) with a custom
| Key | Value | TTL | Examples |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | --------------- |
| session | Any unique identifier of up to 255 characters (regardless of character encoding); Massive will make best efforts to route requests in the same session to the same egress node | Default: 15 minutes (customizable with `sessionttl`) | session42, 1234 |
| sessionttl | Customizable session TTL in minutes, up to 240 minutes | Default: 15 minutes | 30, 60, 120, 240 |
| sessionttl | Customizable session TTL in minutes, up to 1440 minutes | Default: 15 minutes | 30, 60, 240, 1440 |

You can inject a session identifier, like a unique representation of your app or active task, to specify that multiple requests should originate from a single egress node (if available):

Expand All @@ -20,7 +20,7 @@ curl -x https://network.joinmassive.com:65535 \

### Session TTL Behavior

* Session TTL defaults to 15 minutes but can be customized using the `sessionttl` parameter up to 240 minutes (4 hours).
* Session TTL defaults to 15 minutes but can be customized using the `sessionttl` parameter up to 1440 minutes (24 hours).
* **Important**: Sessions use static TTL - they expire at creation time + TTL and are not extended by subsequent requests.
* For example, to set the TTL to 30 minutes:

Expand Down