You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@g123k AFAIR the user-agent is used by the OFF server for stats, so any change would have an impact on the server stats, cc @stephanegigandet
IMHO the easiest solution would be not to force the user-agent when used in web mode. I assume that the browser user-agent will overwrite that void, which would be a relatively relevant approximation for the OFF server. Or it will be kept null, which would also solve the current issue.
Btw we can easily detect "web" usage, we already do with code like that - we consider the "js" version as "web":
Hi everyone,
I have received several complaints about the SDK when used on the web.
Every time the error is
ClientException: XMLHttpRequest error.
.After digging a little bit, the real Exception is:
Refused to set unsafe header "User-Agent"
Today, the way we send the custom header on mobile and desktop is OK.
However, on the web, a User-Agent must follow a strict format.
So we have two choices here:
The text was updated successfully, but these errors were encountered: