Cookie
Login succeeds, but a refresh signs the user out. Help me check whether the session cookie is set and sent back with requests.
Set-Cookie to store a session identifier. When the browser later visits a matching address, it sends a Cookie request header so the server can find the session. A cookie is only part of the request round trip, not a complete authentication system, authorization decision, or database; sensitive sessions also need properties such as Secure, HttpOnly, and SameSite.Set-Cookie: session=•••;
HttpOnly; Securesession HttpOnly ✓GET /profile
Cookie: session=•••The response asks the browser to store it: The server sends Set-Cookie in a response, and the browser decides whether to store it from its name, scope, and security attributes.
Later requests send it when conditions match: For a matching address, the browser puts sendable cookies in the Cookie request header. An HttpOnly cookie cannot be read by page script but can still be sent with a request.
You can say this to an AI Agent
“Check whether the login response sets a secure session cookie and whether the protected request after refresh sends it automatically. Do not print the full cookie value; use Network and Storage to verify the session survives refresh, while identity and authorization remain server-side.
Select page elements for precise AI edits
Click a button, text, or card, note the change, then copy its exact location to AI.
Open Selector Pro website↗