On 4 Dec 2025, at 3:31 pm, Paul Hoadley <[email protected]> wrote:
> Is this a feature, or am I doing something to cause this in my apps? Session > IDs are in cookies. I see in the new tab that the wosid cookie is not being sent on the first request, so WebObjects assigns it a new session and sends back a new wosid. This cookie replaces wosid in the original tab as well, which invalidates the navigation. So to that extent, it's all working as designed. Same behaviour no matter what SameSite is set to, or what domainForIDCookies() returns. Is this just... a feature of browsers? -- Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/
