Cookies

Cookies store your account login, cart, language and settings. The browser sends them to the site with every request in the headers.

Changing your IP does not reset cookies. If you open two accounts in one browser profile through different proxies, the site will still see the same cookies and link the accounts.

That is why separate accounts use separate profiles, in a regular browser or in an antidetect browser, where each profile has its own cookies and its own proxy.

For data collection, cookies are sometimes needed: some sites do not show regional prices without them or redirect you to a language selection page.

Cookie attributes that affect your work

A site sets a cookie with the Set-Cookie header, and its attributes decide where and how long it lives.

• Domain and Path: which hosts and sections receive the cookie.
• Expires or Max-Age: the lifetime. Without them it is a session cookie that disappears when the browser closes.
• Secure: sent only over HTTPS.
• HttpOnly: not available to page scripts.
• SameSite: whether the cookie goes along with requests from other sites.

Cookies and IP rotation in scripts

In Python requests, a Session object keeps cookies between requests, while separate calls to requests.get do not. If you work with a logged-in session through port 823, every request leaves from a new IP with the same cookies. To the site this looks like one visitor jumping between addresses, and many sites end such a session.

For work that needs a login, use a sticky session on a port from the 10000-20000 range: the IP stays the same for the holding time you set, from 1 to 120 minutes. A new IP per request suits collecting public pages where no session is needed. If a site keeps the country, language or currency in a cookie, keep the same country in the username until the session ends, or the page may switch between regional versions.

Cookies are only part of the picture

Deleting cookies does not make a browser new. Sites also keep data in localStorage and IndexedDB, and a browser fingerprint does not depend on cookies at all. To keep real accounts apart, a separate profile with its own storage and its own proxy works more reliably than clearing cookies by hand.