Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SameSite=None warning from Chrome DevTools console #320

Closed
naoyanickf opened this issue Feb 14, 2020 · 3 comments
Closed

SameSite=None warning from Chrome DevTools console #320

naoyanickf opened this issue Feb 14, 2020 · 3 comments

Comments

@naoyanickf
Copy link

As of today(02/14/2020), I got a warning with latest version(6.8.0.360)

A cookie associated with a cross-site resource at https://nr-data.net/ 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.

How can I clear this warning?

@mwlang
Copy link
Contributor

mwlang commented Feb 19, 2020

@naoyanickf I am researching this and will get back to you when I have some more info. Meanwhile, I did find an article on recent changes to how Chrome handles cookies: https://www.theregister.co.uk/2020/01/30/google_chrome_80_cookies/

@mwlang mwlang removed the in review label Feb 19, 2020
@mwlang
Copy link
Contributor

mwlang commented Feb 19, 2020

We are internally aware of this issue and working towards resolving across the board. It is definitely due to default behavior of the Chrome browser changing in how cookies are handled and the UI teams are working diligently towards resolution across the board.

For further reference and discussion, you may be interested in this forum thread: https://discuss.newrelic.com/t/chrome-warning-for-cookie-samesite-attribute/84976/43

Since this is not directly in the Ruby Agent code, I am closing this issue with this comment. If you have questions or concerns, please reach out to our support team.

@mwlang mwlang closed this as completed Feb 19, 2020
@naoyanickf
Copy link
Author

@mwlang Thank you so much! I got it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants