{"version":"2.1.310","anchor":"websocket-and-google-auth-transport-changed","canonical_anchor":"websocket-and-google-auth-transport-changed","heading":"WebSocket and Google sign-in connections are set up differently","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/websocket-and-google-auth-transport-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### WebSocket and Google sign-in connections are set up differently\n\nWebSocket connections now get their own TLS settings, and the Google sign-in client takes its network options from a shared helper\n\n**Unclear.** What connection options the shared helper supplies, and so what changes for Google sign-in users, is not stated.\n\n**What**\n\nTwo kinds of network connection changed how they are set up:\n\n- WebSocket connections (a long-lived two-way connection) now pass TLS settings, which control encrypted connections.\n\n- The Google sign-in client now takes its connection options from a shared helper instead of one fixed setting.\n\n**Why**\n\nThis may change how proxies and encrypted connections are handled when using Google Vertex or Google sign-in.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}