Wolfgang,

you are right, explicit setting of same-site=none is necessary now.

In previous versions of browsers, no explicit setting
of the same-site flag was exactly the same as explicit setting
(an implicit default of same-site=none)

Since some browsers switched to a default of "lax", explicit
setting became necessary.

Fixed now on bitbucket.

-gn

PS: it is not developer-friendly that the behavior is changed
on the fly.... On the client site, the disruptive behavior
change was intended, so changing the default value on the
server is probably not good - and is left unchanged.



_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Reply via email to