[BUG-234978] Web Cookies are not persistent anymore on Windows

[sl-service-account]

What just happened?

When a webpage, displayed on Media on a prim, sets a cookie with PhP, that cookie is only retrieval-able on pages displayed on that same prim, and as long as the media is not unloaded.

A webpage on another prim can't retrieve that cookie anymore, as if it doesn't exist. And if the media is unloaded (by pressing the "stop all media" button or by taking the prim back in inventory or detaching it if it is a HUD), then loaded again (by pressing "play all media" button, or rezing the prim from inventory or attaching it) the cookie set up earlier does not exist anymore either.

What were you doing when it happened?

We have a system of HUDs and other displays throughout our regions that uses cookies as part of an identification system to link users to our backend. HUDs and other displays that only retrieve the user's cookies (and don't set them) have stopped working, as the cookies don't exist for the user anymore.

What were you expecting to happen instead?

Before the latest viewer update (and we're guessing, an update to Chromium), a cookie set up by one webpage on one prim, could be retrieved by another (or identical) webpage on a different prim. The cookie was cached and persistent. This problem only occurs on Windows. The Mac version of the viewer still behave as expected, and previous Windows viewers work as well. Please note that this affect the latest EDU viewer as well.

Other information

From our understanding, and this remains just a guess, in this latest version of the Chromium implementation, cookies are not cached anymore. They exists and are accessible as long as the dullahan process of that media, that set that cookie up in the first place, is running. So the cookie does not exist for the other processes, or later on when the original process has been terminated.

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-234978 | | Summary | Web Cookies are not persistent anymore on Windows | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Triaged | | Reporter | Snippy Yifu (snippy.yifu) | | Assignee | Callum Linden (callum.linden) | | Created at | 2024-01-12T16:08:46Z | | Updated at | 2024-01-12T18:40:00Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2024-01-12T12:40:00.850-0600', "Is there anything you'd like to add?": 'From our understanding, and this remains just a guess, in this latest version of the Chromium implementation, cookies are not cached anymore. They exists and are accessible as long as the dullahan process of that media, that set that cookie up in the first place, is running. So the cookie does not exist for the other processes, or later on when the original process has been terminated.', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'When a webpage, displayed on Media on a prim, sets a cookie with PhP, that cookie is only retrieval-able on pages displayed on that same prim, and as long as the media is not unloaded.\r\n\r\nA webpage on another prim can\'t retrieve that cookie anymore, as if it doesn\'t exist.\r\nAnd if the media is unloaded (by pressing the "stop all media" button or by taking the prim back in inventory or detaching it if it is a HUD), then loaded again (by pressing "play all media" button, or rezing the prim from inventory or attaching it) the cookie set up earlier does not exist anymore either.', 'What were you doing when it happened?': "We have a system of HUDs and other displays throughout our regions that uses cookies as part of an identification system to link users to our backend. HUDs and other displays that only retrieve the user's cookies (and don't set them) have stopped working, as the cookies don't exist for the user anymore.", 'What were you expecting to happen instead?': "Before the latest viewer update (and we're guessing, an update to Chromium), a cookie set up by one webpage on one prim, could be retrieved by another (or identical) webpage on a different prim. The cookie was cached and persistent.\r\nThis problem only occurs on Windows. The Mac version of the viewer still behave as expected, and previous Windows viewers work as well.\r\nPlease note that this affect the latest EDU viewer as well.", } ```

[sl-service-account]

Dan Linden commented at 2024-01-12T18:40:01Z

Thank you for the report, Snippy!