Developer forum

Forum » CMS - Standard features » SameSite error

SameSite error

Kim Hansen
Reply

Hi,

Google Chrome version 80 (release date feb 4th 2020) will not accept cookies from 3rd party HTTP requests.

When i log in to a 9.7.5 solution, i get a lot (7) of warnings of calls to http://doc.dynamicweb.com

How will this affect the use of DW Backend from tomorrow?

Error:

A cookie associated with a cross-site resource at http://doc.dynamicweb.com/ was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers 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.

Thanks

/Kim Hansen


Replies

 
Nicolai Pedersen
Reply
This post has been marked as an answer

Hi Kim

I guess you mean from www.dynamicweb.com? The backend tries to retrieve a json feed of news from Dynamicweb.com - that will give this error. It comes from the news widget in the home dashboard. You can just remove the widget, and problem 'gone'.

We have a tasks to change the feature to do this server-to-server. We already have this problem because of CORB issues as well.

Do you get the error other places than in the console?

BR Nicolai

Votes for this answer: 1
 
Kim Hansen
Reply

Hi Nicolai,

Perfect. Removing the widget worked.

I was worried that it had to do with the login procedure, licencing and what not...

No, i have not seen the SameSite warning elsewhere. (Quite a bit of non-unique id warnings on lists all over the backend thou)

 

/Kim

 

You must be logged in to post in the forum