Cookie “_session_id” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To know more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Cookies
kt/8362
Diff:
Diff:
Seeing same warning for
memorable_forget
. Probablysite-notification
cookie needs it too.Allura can run without https, in fact that's the default for a docker develoment instance. And then setting
secure
flag on the cookie means it doesn't work and you can't submit any form successfully. Could checkbeaker.session.secure
config and only do secure if that is secure. Or setSameSite=Strict
, seems like that would be ok we don't need these cookies shared? But might be good to have cookies flagged as secure whenever possible anyway.`New rev includes
memorable_forget
andsite-notification
.Conditionally setting secure value based on the
session.secure
val