Review saved cookie attributes with values withheld
Admin ·
A workshop site sets a session preference and a display preference. Read their source fields separately, then compare the client’s saved Cookie line.
Review the workshop cookies
Choose Load example and Analyze cookies. The recorded HTTPS response has a __Host-workshop entry with Secure, HttpOnly, SameSite=Lax and Path=/. The scope column reports host-only scope.
The display entry has an Expires date containing a comma. It stays on one row because it came from one Set-Cookie line. SameSite=None without Secure appears in Cookie findings.
RFC 6265, HTTP State Management MechanismIETF cookie specification draft and prefix rules
Compare the saved Cookie inventory
Look at the Saved Cookie inventory table. It lists display and session-mode from the request. The request field shows what names were sent and leaves the original attributes to the separate Set-Cookie table.
Try setting Recorded response transport to HTTP and analyzing again. The report notes that a Secure attribute on a saved HTTP response can face secure-origin storage rules.
RFC 6265, HTTP State Management MechanismIETF cookie specification draft and prefix rules
Save the redacted report
Choose Copy JSON report or Download JSON report. The report lists names and recognized attributes or scope details. It withholds the cookie values from both tables.
Paste each separate Set-Cookie header as its own line when checking another capture. Keep the original capture available for any checks that need exact cookie values or browser state.
Common questions
Why did a Set-Cookie name appear more than once?
The same name can be set with different scopes. Review each recorded line and its declared attributes.
Does a Secure flag guarantee that a browser stores the cookie?
Storage depends on the response origin, cookie restrictions and browser state. The analyzer reports the saved attributes.