domain parameter in cookie.value()

Feature RequestImprovement
I’ve run into an issue with cookie.value():
My setup involves a login endpoint that sets a co-auth cookie, but the response actually sets cookies across multiple domains (the auth service uses subdomains).
| Domain | Cookie |
|---|---|
foo.example.com |
co-auth= |
bar.example.com |
co-auth= |
example.com |
co-auth=eyJhbG... ← the one I actually need |
This means my cookie jar ends up with several entries named co-auth. Some with actual values, some empty (expired/deleted ones from the subdomains).
cookie.value(name='co-auth') seems to grab the first match, which in my case is one of the empty ones. The actual token I need lives under a specific domain, but there’s no way to tell Yaak which one to pick.
I think that domain parameter would solve that problem, f.e. cookie.value(name=‘co-auth’, domain=‘example.com’)
Thanks for considering it :D
great app btw!
https://github.com/mountain-loop/yaak/pull/452