IP Sessions Explained: TCP, Website Login and Proxy Exits
This English page was updated; the Chinese version may not contain these revisions yet. Compare the Chinese page.
“IP session” is not one universal protocol setting. In a proxy workflow, people often use the same phrase for three different things: a TCP connection, a website login session and the proxy provider's exit-IP policy. Keeping them separate prevents a common mistake: assuming that a stable IP automatically keeps a website login alive, or that one open socket guarantees the next request will use the same exit.
Three layers that should not share one name
1. The TCP connection
A TCP connection is a transport path between a pair of sockets. It starts with a handshake and eventually closes or fails. An application can open more than one connection during a single task, and a browser may reuse or replace connections without asking the user. Connection lifetime is therefore not a reliable definition of how long a proxy exit or website login will last. The transport definition comes from RFC 9293.
2. The website session
HTTP requests are stateless by themselves, but a website can associate later requests with a login or shopping session using cookies or another application mechanism. Keeping the same proxy IP does not preserve an expired cookie, and changing an IP does not by itself prove that the website signed you out. Inspect the site's own response, cookie state and account rules separately from the proxy route. See MDN's HTTP overview and cookie guide.
3. The proxy exit policy
A proxy session is an operational label for how a provider assigns or retains an exit IP across requests. A static residential ISP product uses an assigned endpoint for the selected lease; a rotating residential route is intended for workflows that can accept a different exit. Some products may offer a sticky option, but its duration and reset behavior must be checked on the currently selected endpoint. Do not infer a universal rotation interval from this article or an old screenshot.
Choose the route from the task
- One assigned endpoint: consider static residential ISP when a multi-step workflow needs the same exit. The current price, region, protocol and lease term come from the product quote, not from a historical article.
- Independent requests: consider rotating residential when each request can be evaluated separately and you record which exit was observed.
- Several steps but no permanent IP requirement: check whether the current product offers a suitable sticky behavior, then test the actual window. A website login can still expire for reasons unrelated to IP rotation.
Neither “static” nor “rotating” is a guarantee of acceptance by a target website. Respect the destination's rules and compare the observed result with the job you are trying to complete.
Verify one route before a real workload
- Record the current endpoint host, port, protocol and authentication method from your Proxy302 product interface. Never paste a password or full proxy URL into a public ticket.
- Make one direct IP-check request and one proxied request to the same permitted IP-check service. Follow the cURL proxy guide for HTTP, SOCKS5 and DNS-mode examples with placeholders.
- For a multi-step test, record the exit IP at each step together with the time, client, destination response and website login state. Repeating a request with the same IP does not prove that every later request will keep it.
- If a step fails, separate connection refusal, proxy authentication such as HTTP 407, and a destination's own 401 or 403. The connection troubleshooting guide gives the first safe check for each case.
Frequently asked questions
Does one TCP connection mean one website session?
No. TCP carries data; the website decides how to recognize an application session. A login may continue across new connections or end while a connection is still open.
Will a static IP keep me logged in?
Not by itself. Cookies, account policy, device state and the website's own security checks also matter. Test the full permitted workflow rather than the IP alone.
How long will Proxy302 keep the same exit IP?
That depends on the selected product and current endpoint configuration. A static IP's lease and any sticky or rotating behavior must be read from the product interface and checked with repeated requests; this article does not promise a fixed interval.
References: RFC 9293 (TCP), MDN HTTP overview, and MDN cookies. Product availability and connection details must be checked in the current Proxy302 workspace.