without the `SameSite` attribute
-
These cookie samesite warnings go away when I disable Jetpack.
Cookie: tk_tc on .widgets.wp.com
A cookie associated with a cross-site resource at http://widgets.wp.com/ was set without the
SameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.Cookie: tk_tc on .wp.com
A cookie associated with a cross-site resource at http://wp.com/ was set without the
SameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.And there are other cookie samesite warnings go away when I disable Jetpack, for domain
http://wordpress.com/
http://public-api.wordpress.com/
-
The warning is visible only in the browser console on Chrome. I assume this is something relatively new. Down the road these cookies will be required to have a SameSite attribute.
You can see them on your site as well if you want to dig deeper: https://jetpack.com/
The topic ‘without the `SameSite` attribute’ is closed to new replies.
