SameSite RRS feed

  • Question

  • Chrome is changing their default behavior for the SameSite cookie attribute in version 80 (February).  While testing our site with the experimental flags enabled, I noticed that some Bing cookies are blocked because the SameSite attribute is not set.  Maps appear to be working fine, but I am not sure if there are other implications?

    The Bing cookies that were blocked were: MUID, MUIDB, _EDGE_S, _EDGE_V

    Monday, January 13, 2020 8:02 PM

All replies

  • There should be little difference when compared to a browser with Cookies turned off.  The control works with or without cookies enabled.  They really just allow for caching so the site doesn't need to download map tiles repeatedly but you are unlikely to notice a difference on a normal network connection these days.
    Monday, January 13, 2020 11:29 PM
  • Thanks for clarifying.  In a number of searches that I did on these cookies, they were categorized as tracking cookies.

    Is Bing planning to update the SameSite attribute on these cookies to ensure optimal functionality? 

    Tuesday, January 14, 2020 2:44 AM
  • I am not familiar with "SameSite" but I will ask the team if they know the status of that http tag. After a quick search, it looks like other "teams" at Microsoft are accommodating the change by Chrome so I assume Bing is as well. (

    As a side note, I think "tracking" is the correct term for such cookies as they do track location of the mapview etc.

    Tuesday, January 14, 2020 7:53 PM
  • Any update from the team as to their plan for these cookies?
    Friday, January 17, 2020 9:33 PM
  • No. FYI this likely will not be a fast answer. When cookies are involved there is a full review process as cookies are wide rather than just within Bing Maps.
    Saturday, January 18, 2020 7:30 PM