Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Same-site flags were removed in Chromium 91 - How can I disable them for local development?

Previously I could disable the verification of same-site cookie in the chrome://flags using the following flags (pic 1) but it seems that in Chromium 91 they were removed (pic 2).

What can I do to disable this verification?

enter image description here


enter image description here

like image 507
VitalyB Avatar asked May 30 '21 12:05

VitalyB


People also ask

How do I disable SameSite?

In Chrome do the following: Type chrome://flags in the browser address box and hit enter Type cook in the search flags box Change SameSite by default cookie setting to Disabled Click relaunch button in the lower right corner.

How do I disable cookies without SameSite must be secure?

If you are running Chrome 91 or newer, you can skip to step 3.) Go to chrome://flags and enable (or set to "Default") both #same-site-by-default-cookies and #cookies-without-same-site-must-be-secure. Restart Chrome for the changes to take effect, if you made any changes.

Should I disable SameSite by default cookies?

If, after clearing the Chrome browser cache and re-sideloading or redeploying, you still have issues connecting, then Chrome users should disable the SameSite by default cookies flag.


3 Answers

For the local development in chrome 91, we need to edit the cookie SameSite attribute and set it as None. enter image description here

like image 66
Sreekanth.S Avatar answered Oct 13 '22 05:10

Sreekanth.S


there is an temporary solution for this problem set an commond line in chrome/edge (v91) launch cofing like this:

Windows:open Chrome/edge shortcut's property,add: "--disable-features=SameSiteByDefaultCookies" after Target property

in my pc,it like ** "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=SameSiteByDefaultCookies ** finally

then restart your chrome/edge,try again

enter image description here

like image 26
家魁张 Avatar answered Oct 13 '22 05:10

家魁张


Starting from Chrome 91 these flags are not needed since it is now a default behavior. It means either this feature(s) must be configurable in settings or non-configurable at all (and this is our case!).

However, there are still similar launch feature flags available up until Chrome 94:

  • SameSiteByDefaultCookies
  • CookiesWithoutSameSiteMustBeSecure

For example, launch command in Linux then would be

google-chrome --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure

I guess after Chrome 94 one has to just deal with it

like image 2
amankkg Avatar answered Oct 13 '22 06:10

amankkg