Proxy Rotation Across Requests, Connections, and Sessions
Check what a rotating proxy service actually rotates before adding Connection: close to every application request.
A second request through the same gateway can legitimately use the same public IP. Check which lifetime the service uses for its rotation:
| Rotation unit | What to compare |
|---|---|
| Request | The next application operation and its observed exit |
| Connection | Whether the client reused a compatible connection or opened another |
| Provider session | The documented sticky-session input and its lifetime |
Connection: close is not a universal gateway instruction. For HTTPS inside CONNECT, the website request header travels inside destination TLS. It does not tell the outer proxy which public IP to assign. HTTP/1.1 connection-specific semantics also cannot be carried unchanged into every HTTP version or transport.
If a documented per-connection service needs a fresh connection, use the client's supported lifecycle control and account for repeated TCP/TLS setup costs. If rotation follows a provider session, reconnecting may retain both that session and its exit.
Record the request identifier, endpoint, relevant session key and destination-observed source separately. Closing a connection establishes only that lifecycle event; verify the exit chosen for the next operation against the service's actual rotation contract.