CODEWITHSUNDEEP
javascriptphpgoogle-chromecookiessamesite
Fullstack_Developer
Fullstack_Developer

Reputation: 115

Trying the SameSite attribute fix for the google recaptcha v2 warning on Chrome 77 doesn't seem to be working for me?

I apologize if I'm repeating this question but I've spent over 6 days on this and I'm losing my mind. I can't seem to get that warning to disappear even though I've meticulously tried and retried to add these in my php index before the and tags. I've tried posts on SameSite warning Chrome 77 to use 

response.setHeader("Set-Cookie", "HttpOnly;Secure;SameSite=Strict");

as well as posts here How to solve `SameSite` attribute to use

header('Set-Cookie: cross-site-cookie=name; SameSite=None; Secure');

as well as the examples on here https://github.com/GoogleChromeLabs/samesite-examples/blob/master/php.md

and I'm still getting the warning even though everything else hasn't changed. Am I missing something or doing something wrong? Sorry, I suppose it shouldn't be a big deal but I'm so ocd over these warning messages and errors that's popping up I wish they would go away! Thx in advance.

-update- sorry the warning that pops up in console in question is this

A cookie associated with a cross-site resource at http://google.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. 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.

Upvotes: 5

Views: 7029

Answers (1)

rowan_m
rowan_m

Reputation: 3050

The warning is specifically for the cookie coming from "google.com" so you will not be able to affect it. If any of the console warnings refer to domains you control, then you should be following that advice to update your SameSite attributes.

It does mean that you will continue to see these warnings until the affected domains update their cookies, which should be happening over the coming months. The enforcement of this behaviour is not planned until Chrome 80, which will be stable in February. So, no actual site/service functionality should be affected in stable Chrome before then.

Upvotes: 6

Related Questions