We should set both attributes.
Firefox already gives a warning in console that in the future it will rejected if SameSite is none and it hasn't the secure attribute.
I translated the warning in the console:
The cookie "tswebsite_sessionid" will soon be rejected in the future because it specifies either "None" or an invalid value for the "SameSite" attribute without using the "secure" attribute. For more information about the "SameSite" attribute, see https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite.
I have already tested this new cookie placements for my site and it's working quite fine.
We should set both attributes. Firefox already gives a warning in console that in the future it will rejected if SameSite is
none
and it hasn't thesecure
attribute. I translated the warning in the console:I have already tested this new cookie placements for my site and it's working quite fine.
For the SameSite attribute we can discuss.