Set-Cookie & Cookie Header Parser

Ek raw Set-Cookie ya Cookie header paste karein aur har attribute, expiry aur security warning aapke browser mein alag-alag dekhein.

Set-Cookie Parser poori tarah aapke browser mein chalta hai. Cookie headers, values aur unmein maujood koi bhi tokens aapke device par parse hote hain aur kabhi ArrayKit ko upload nahi hote.

HAR Viewer kholein

Set-Cookie Parser ke baare mein

Set-Cookie Parser ek raw Set-Cookie response header — ya unka ek poora dher — leta hai aur har cookie ko ek readable table mein todta hai: name, URL-decoded value, Domain, Path, ek friendly relative time ke saath Expires, Max-Age, aur Secure, HttpOnly, SameSite, Priority aur Partitioned flags. Yeh un galtiyon ko flag karta hai jo chupke se cookies ko todti hain, jaise Secure ke bina SameSite=None, ek pehle se expired date, ya ek __Host- prefix jo apne rules ka ullanghan karta hai, aur batata hai ki har cookie ek session hai ya ek persistent. Iske bajaye ek Cookie request header paste karein aur yeh bheje ja rahe har name aur value ko list karta hai. Sab kuch locally aapke browser mein parse hota hai, isliye jo headers aap inspect karte hain woh kabhi aapke device se bahar nahi jaate.

Features

Set-Cookie Parser kaise use karein

  1. Apne browser ke Network panel ya ek server response se ek Set-Cookie header copy karein
  2. Use box mein paste karein — agar kai hain to aur Set-Cookie lines add karein, ek per line
  3. Attributes, expiry aur kisi bhi highlighted warnings ke liye per-cookie table padhein
  4. Iske bajaye ek request ki Cookie: line inspect karne ke liye Cookie header mode par switch karein

Example

Input

Set-Cookie: track=1; Domain=.example.com; SameSite=None

Output

track = 1 | Domain=.example.com | SameSite=None | Session
⚠ SameSite=None requires the Secure attribute — browsers will reject this cookie.

Secure ke bina ek SameSite=None cookie ko aapke paste karte hi flag kar diya jaata hai.

Common errors aur troubleshooting

Aksar pooche jaane wale sawaal

Set-Cookie parser har cookie ke liye kya dikhata hai?
Har Set-Cookie header ke liye yeh name, URL-decoded value, aur jo bhi attribute use milta hai use list karta hai — Domain, Path, Expires (ek relative time ke saath), Max-Age, Secure, HttpOnly, SameSite, Priority aur Partitioned — plus jo bhi toota hua lage uske liye warnings.
SameSite=None ko Secure attribute ki zaroorat kyun hoti hai?
Modern browsers ek cross-site cookie (SameSite=None) ko sirf tab accept karte hain jab woh Secure bhi marked ho, taaki woh sirf HTTPS par travel kar sake. Agar Secure missing hai to browser cookie ko reject kar deta hai, aur parser us combination ko ek warning ke saath flag karta hai.
Ek cookie par Max-Age aur Expires mein kya farq hai?
Expires ek absolute date set karta hai; Max-Age cookie milne se seconds mein ek lifetime set karta hai. Jab dono maujood hon to Max-Age jeetta hai, isliye tool Max-Age ko current time ke against resolve karta hai aur note karta hai ki yeh Expires par precedence leta hai.
__Host- aur __Secure- cookie name prefixes ka kya matlab hai?
Ye security prefixes hain jinhe browsers enforce karte hain. Ek __Secure- cookie ko Secure set karna hoga; ek __Host- cookie ko Secure set karna, Domain omit karna, aur Path=/ use karna hoga. Parser in rules ko check karta hai aur warn karta hai jab ek cookie ka name aise guarantees ka vaada karta hai jo uske attributes nahi nibhaate.
Kya yeh tool ek Cookie request header bhi parse kar sakta hai?
Haan. Cookie header mode par switch karein aur ek Cookie: line (ya ek bare "a=1; b=2" string) paste karein taaki request jo bhejta hai us har cookie name aur value ki ek table mile, har ek URL-decoded aur copyable.
Yahan ek session cookie aur ek persistent cookie mein kya farq hai?
Bina Expires aur bina Max-Age wali ek cookie ek session cookie hai — jab browser band hota hai to yeh clear ho jaati hai. Ek Expires date ya Max-Age wali koi bhi cheez persistent hai. Parser har cookie ko Session ya Persistent label karta hai taaki aap ek nazar mein bata sakein.

Related tools

Saare ArrayKit tools