Added todo about an error when a user hits a route over sockets that does a res.redirect cross-domain (this is because we would need to spin up a websocket client on the backend to proxy the request, and this seems like a bad idea).  Another alternative is to have the browser-side SDK support HTTP-302-style redirects, but if we go that route, there should still be a solid fallback since we don't want to create any hard dependencies on ANY front-end code.