[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 bugzilla-daemon at webkit.org
Fri Sep 22 06:42:36 PDT 2023


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

--- Comment #75 from ed <edinsweden at gmail.com> ---
(In reply to ed from comment #74)
> (In reply to Karl Dubost from comment #72)
> > ed, what is you configuration
> > * OS version
> > * Device version
> > * Browser
> > * Server used
> > * Software etc.
> > 
> > Is there a public site which is usable for the problem you are experiencing.
> 
> I will try to replicate and ship that to render.com and also share the code
> on github. Will come back later today with some links.

I built a separate example reusing some code to try to reproduce, which I have been able to partially achieve. here's the working link https://safari-cookies-test.onrender.com -- clicking the link will set the cookie then redirect back to /.
Here's the repository with the code https://github.com/edimoldovan/safari-cookies-test

What I have found so far is that when Safari is connecting directly to the Go app, that is when the issue occurs. In the above url it works fine because I believe render uses a reverse proxy of some sort between the app and Safari.

The cases where it doesn't work:
- localhost, where there is no proxy running or 
- my actual production, where I accidentally forgot to set up Nginx or Caddy but the Go app still works as it runs and serves content directly on :443

And here are the answers for the system related questions:

* OS version: Sonoma 14.0 (23A344)
* Device version: Apple M1 Pro
* Browser: Safari Version 17.0 (19616.1.27.211.1)
* Server used: Go
* Software etc. everything is implemented in Go's Standard Library mostly

On the same system above everything works as expected in Firefox Developer Edition 118.0b9 (64-bit) and Chrome Version 116.0.5845.187 (Official Build) (arm64).

What happens in Safari feels like cookies are not being set at all on localhost.

-- 
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/20230922/151c52b1/attachment.htm>


More information about the webkit-unassigned mailing list