django-cookie-samesite has a browser version guesser, because different browsers interpret samesite differently.
The best solution I've heard of is setting two cookies with two different names, one the old way and one the google way. Then check for both where checking needs done, one of them being a fallback. On Sun, 23 Aug 2020 at 03:41, אורי <[email protected]> wrote: > > > > On Sat, Aug 22, 2020 at 10:07 PM Adam Johnson <[email protected]> wrote: >> >> (The workaround is in this comment: >> https://github.com/django/django/pull/11894#issuecomment-577681440 , and if >> you want, a package: https://github.com/jotes/django-cookies-samesite ) > > > Thank you. I was not aware of this package and middleware. > > אורי. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CABD5YeGTtzHQMrsB%3Dc%3DHBeymNxWFJc1En9vqj%3DF1HEtO5P0odA%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CACQ%3DrrdpXMcQUmHVF9hQgXtD-1pADQMO5WoyySBw3OB-p5Oqeg%40mail.gmail.com.
