Sounds like a logistical first step to me. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Owen Leonard Sent: Monday, 7 February 2022 10:50 AM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: [Koha-devel] Bug 26019 and SameSite cookie attribute There has been some discussion on Bug 26019 about how to handle the changing ways browsers are handling the "SameSite" attribute in cookies: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26019 There doesn't seem to be a consensus on how to proceed, and I guess part of the question is whether there should be options for setting an attribute other than "Lax." I propose that a logical first step would be to explicitly set SameSite to "Lax" for the cookies we currently set without a SameSite attribute, since browsers have been assuming "Lax." I'd be happy to work on such a patch because I'm tired of seeing the warnings in the browser console while I'm trying to hunt down jQuery upgrade issues. Please weigh in! Thanks, Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/