12

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

VitalyB
  • 12,397
  • 9
  • 72
  • 94
  • 1
    I gave up fighting with Chrome over that. I've followed a guide to convert my localhost devserver to HTTPS to mimic completely the behavior of the deployed, production environment instead: https://web.dev/how-to-use-local-https/ – VitalyB Jun 08 '21 at 12:41

3 Answers3

10

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

家魁张
  • 121
  • 4
  • 9
    Note that this will no longer work in Chrome 94+. The flags will be removed entirely. See https://www.chromium.org/updates/same-site?pli=1 – chlily Jun 01 '21 at 19:48
2

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

Sreekanth.S
  • 541
  • 4
  • 4
2

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

amankkg
  • 4,503
  • 1
  • 19
  • 30