Stop copying Cookie values between requests
Cookie-authenticated API testing often requires a developer to inspect Set-Cookie, copy a value, and update the next request by hand. A refreshed login or rotated session repeats the work, while a stale value can make the result misleading.
Header Relay now lets each Profile define fixed Cookies and the Cookie names it should track. A registered Set-Cookie value is captured from the target origin and used on later matching requests.
One final Cookie header
Fixed and captured values are combined into one deterministic Cookie header. A fixed value wins when the same Profile also has a tracked value with that name. Different names from multiple matching Profiles can be combined; the same name across Profiles is reported as a conflict instead of being resolved silently.
URL Probe shows the matching Profiles and the final Cookie header before a request is sent. Values are also available in the manager and Popup, with individual and Profile-wide controls for clearing tracked values.
Chrome's cookie store stays separate
Header Relay does not read or modify Chrome's cookie store and does not request the cookies permission. When at least one managed value applies, it replaces the outgoing Cookie header for that request. When no managed value applies, it leaves Chrome's original Cookie header unchanged.
Tracked values live only for the current browser session. They are cleared after browser or extension restart, Profile disablement, relevant configuration changes, permission revocation, or an explicit clear action.
What the Cookie workflow adds
Fixed Cookie
Set a name and value that should always be sent by an enabled Profile.
Tracked Cookie
Register a Cookie name and update its session value from matching Set-Cookie responses.
Inspectable result
Review current values and the final Cookie header in the manager, Popup, and URL Probe.
Boundaries that remain explicit
- Only enabled Profiles, configured Target Origins, and non-excluded paths are eligible.
- Cookie attributes do not recreate browser send rules; Target Origins and Excluded Paths define scope.
- Cookie values and raw Set-Cookie strings are never written to audit logs or analytics.
- Invalid legacy Cookie header settings are preserved as migration issues for manual review.