401 (Unauthorized)

[chessl]

It appears in the console every time when opening the demo page and my site has the same issue. I checked and the site_id matches.

[umputun]

I think this is expected. UI is trying to determine if the user logged in or not. @Reeywhaar - pls confirm

[Reeywhaar]

Well, error handling should be there, this should be considered log spam.

[umputun]

so, smth to address on your side?

[Reeywhaar]

yep, it's a minor bug

[Reeywhaar]

oh, sorry, I've mistaken this with console.error message, but this is just plain network request log and nothing can be done here, it's browser thing that @umputun have described.

[umputun]

is it considered wrong/bad/annoying? Theoretically, we can address it by changing the response of /user call to return json with "status": "unauthorized", however, this feels odd to me because this is exactly what 401 supposes to represent

[Reeywhaar]

I think this clearly will be breaking change. Dunno, this kind of error pops on blink/webkit based browsers, why they have chosen to treat this as an error? In firefox you get this message if you turned on logging xhr requests in console which is not default.

[chessl]

Just found out a StackOverflow post addressing the same issue. It certainly is a chrome thing and I guess I'll just have to ignore it. Thank you!