Sending and receiving cookies
How cookies are sent
Section titled “How cookies are sent”For HTTP, GraphQL, SSE, WebSocket, and Socket.IO handshakes, Kurlo checks the cookie jar before sending:
- Domain and path must match the request URL.
- Secure cookies are only sent over secure schemes.
- Expired cookies are ignored.
- Host-only cookies stay scoped to their original host.
- Manual
Cookieheaders remain visible in the request preview and are not hidden by the jar.
gRPC does not use the browser-style cookie jar path.
Reading cookies from responses
Section titled “Reading cookies from responses”When a response includes Set-Cookie, Kurlo stores it in the active workspace jar. The jar is encrypted alongside the rest of the request store.
Cookies are refreshed after normal sends and after Collection Runner runs.
Was this page helpful?