4 ms·

Also this: https://catchjs.com/Blog/SameSiteCookies https://catchjs.com/Blog/SameSiteCookies

• masswerk 4y ago
  > The Chrome team insist that this behavior is a bug, but it is actually in line with this particular version of the spec. Or, why any other browser is the new IE. /s
• Xelynega 4y ago
  Isn't the issue here that a breaking change was introduced in a new standard version that only some browsers implement. Why can this not be solved with http version numbers instead of a method that allows Google to maintain a seperate standard that it forces developers to switch between with user agent strings?
• daveoc64 4y ago
  This was a huge issue for some of the software I maintain. The link explains the problem really well. User agent sniffing was the only option. We have a lot of end users on older iPads that can't upgrade to a newer browser. These users are the general public, so you can't force them to upgrade devices. We will have to continue to do the user agent sniffing for years to come.
  • tuukkah 4y ago
    From the link: > While the double cookie approach is what is recommended by Google, the ASP.NET team concluded otherwise - they found that going with a user-agent sniffing approach would be the safer approach. User-agent sniffing is hard to get right. It's hard to cover all the relevant browsers, and it's hard to do so in a way where you can be reasonably sure it won't break in user-agents of the future. But when someone gets it right, that becomes a readily copiable solution that anyone can use.