Something fishy about cookies managment ...

[jrouaix]

Hello,

I started using your tool long time ago and just updated to v17 today ... there is something really weird.

• I use auth cookies in some scenarios.
• When I load 1 only user from goose, everything goes fine, my website auth works well, I changed nothing recently
• Then I load multiple users and some scenarios fails because the authentication does not auth them ...
• Then I switch from auth cookie managed by the reqwest client of goose side, to manually crafted from the scenario auth bearer token headers .... and I have no more problems with loads of parallel users.

So I really think something is broken in users isolation, without having any more clue ...

Does that click on your side ? Should I dig deeper ?

[jeremyandrews]

Reviewing the Changelog, nothing jumps out at me as causing this regression. The only related changed is #557 , so perhaps you can start by reverting that change and see if it solves your problem? Any further investigation would be greatly appreciated.

[alecsmrekar]

I am noticing the same issue. It started popping up after upgrading from Goose 0.17.0 to 0.17.2. I am running a loadtest with 20 users, and one of those users performs two transactions:

• log into a site (runs with set_on_start)
• create a piece of content -> this fails due to a 403, inspecting the response, it turned out that the admin sessions wasn't there anymore