The 301 redirect support was added for when a user tries to log in to the old server after a server or deployment region was changed on the cloud. Unfortunately, if the user is already logged in, the websocket receives a 301 redirect from the old server location and receives a 301 redirect and the redirect is not handled properly. This is treated as a non fatal error and the sync connection will continue to attempt to use the old server.

Update the websocket handling of the 301 redirect error to treat it as a fatal error and log the user out. This will force the user to obtain an access token again, which will handle the redirection to update the server and websocket URL location information.

Also, if the anonymous user is currently logged in, it will not hit the server again if log in when log in is called. Update the http redirect handling to ensure the current logged in users have their access token invalidated if a redirection occurs.