MUID cookie is now required for convsersation/create?

[JakeAve]

Starting this morning, I've ran into an issue where you can't create a chat without the MUID. It throws a 404. I have my own update to fix that, but I wanted to see if other people have been having that issue.

The MUID comes from Microsoft for ad tracking: https://learn.microsoft.com/en-us/clarity/setup-and-installation/cookie-list The format looks like a 32 digit hex uppercase / GUID, but you aren't able to spoof it - I tried. I wonder if you can use a blank MR or MR=true and it hits the same middleware and generates a new MUID. I don't know enough about the Microsoft cookies.

Once the MUID and _U are added to the cookie, it works like always.

const fetchOptions = { ...otherStuff, cookie: `MUID=<32-digit-hex>; _U=<user-token>; `} 

[RaschidJFR]

In what region are you @JakeAve ? I'm in Canada and I started getting 503 until I removed the use of the cookie. I'm not sure if this is the same behavior across different locations. Have you tried not using the cookie at all?

[JakeAve]

I’m in en-US UT/AZ and when I checked a few days ago I didn’t need it anymore. I’m going to check in Texas today or tomorrow and see what it’s like. Weird.

[NgWaiKong]

hey, i just met "Error: unexpected HTTP error createConversation 404: Not Found" today, have you ever seen? @JakeAve @RaschidJFR

[JakeAve]

That's exactly what I was seeing. And adding the MUID cookie in addition to the normal cookie fixed it. But just a few days ago, I was able to delete the MUID cookie and it still works. No idea why it's not consistent.

[RaschidJFR]

hey, i just met "Error: unexpected HTTP error createConversation 404: Not Found" today, have you ever seen?

@NgWaiKong I faced that error while I was playing around with some parameters. This happened to me while creating a conversation and setting the param isStartOfSession incorrectly. I don't know if this is related to your issue but feel free to share some code to check it out.

[NgWaiKong]

hey coming back to you guys, thanks for the details you mentioned. @RaschidJFR @JakeAve Now, I just changed my backend server to another region, and it worked. I was thinking it should related to the region policy of New Bing.