-
Notifications
You must be signed in to change notification settings - Fork 130
Description
Hi guys,
I've read the new third-party restrictions that are about to be implemented, all sounds great, all works on our end.
But, how do we continue developing and testing our frontend locally on http://localhost
when the cookie is SameSite=Secure
and the backend is fronted by a CDN? Will there be some sort of flag that would enable us to do cross-site requests for development after Chrome has fully phased out third-party cookies or will they be fully blocked?
Context:
The cookie we create is associated with our customdomain.com
and the frontend is communicating with AWS CloudFront where the custom domain is added as an alternate name. So the browser will just not send the cookie from localhost. Deploying a local backend is not really an option for us. And continuously deploying changes to pr-***.dev.customdomain.com
just to test a small change is not great either.
Any tips or pointers on how we can continue local development?
Edit: SameSite=Strict
is what I meant