You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As many browsers are rejecting the set-cookie header when SAMESITE is set to none, it would be good if a new attribute "PARTITIONED" is created. Unless, the authentication under this set-up will be impossible in a near future. As far as I see, only Firefox is still supporting set-cookie headers without this parameter.
Would it be possible to add this in the next major release?... as well as #584 . It would be extremely helpful.
Hello,
As many browsers are rejecting the set-cookie header when SAMESITE is set to none, it would be good if a new attribute "PARTITIONED" is created. Unless, the authentication under this set-up will be impossible in a near future. As far as I see, only Firefox is still supporting set-cookie headers without this parameter.
Would it be possible to add this in the next major release?... as well as #584 . It would be extremely helpful.
https://developers.google.com/privacy-sandbox/3pcd/chips
I am sorry, I am new to Django, so I cannot send a PR (for now). But I am willing to help in any sort of way that I can.
Thanks!
The text was updated successfully, but these errors were encountered: