[Webkit-unassigned] [Bug 255524] REGRESSION (Safari 16.4): Safari sometimes doesn't send cookies for assets requests and javascript fetch requests

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=255524

guillaume.esquevin at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |guillaume.esquevin at gmail.co
                   |                            |m

--- Comment #78 from guillaume.esquevin at gmail.com ---
I've been affected by this bug since last march. It has driven me crazy as I thought at first that it was due to the security policy that my company IT had installed on our macs. (I still wonder to this day, could it be an external process wiping some session/cookie files for security purpose?)

I've no clue as to why and how to fix this bug, but I'll give you details that might be of use to reproduce/understand it.

I managed to circumvent the issue by using safari technology preview which did not log me out every few minutes. With the release of MacOS Sonoma I tried going back to safari and it worked for a few glorious week, but today, suddenly, the issue is back

I've developper tools activated, I toggle the disable cache often in the network tab.

My company makes me use Okta for sso on the websites I noticed the issue

I close and reopen safari frequently.

I lock my session whenever I leave my laptop.

I've disabled/uninstalled all the extensions I had.

I've disabled `prevent cross site tracking` in my settings to circumvent a login issue I had running our webapp on localhost

I encounter this issue on google.com and gitlab.com and okta.com where it'll ask me to connect multiple times a day.


I understand perfectly how hard it can be to track a bug you cannot reproduce and seem to not affect everyone, I can simply hope that one of the random facts I've listed here might spark the beginning of the understanding of what is going on.


I believe a key point is that I've never had the issue in private mode or in safari technology preview. Only in plain safari, which lead me to believe that something is messing with whatever is publicly accessible in safari.



Anyway, Thanks for all the hard work you put in this amazing browser and best of luck tracking this bug

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20231103/0c6003b6/attachment-0001.htm>