{"version":"2.1.290","anchor":"sse-transport-can-require-stream-evidence-and-tracks-service","canonical_anchor":"sse-transport-can-require-stream-evidence-and-tracks-service","heading":"Remote connections can detect a proxy answering in place of the server","tier":"soon","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/sse-transport-can-require-stream-evidence-and-tracks-service","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote connections can detect a proxy answering in place of the server\n\nA new option makes a live-update connection fail when the reply is not a real event stream, which suggests a proxy or gateway answered\n\n**Unclear.** It is not clear which connections turn the strict mode on.\n\n**What**\n\nSome of Claude Code's connections use SSE (server-sent events), a way for a server to keep one connection open and stream updates over it. That connection has a new optional strict mode, called `requireStreamEvidence`. It is off by default. When it is on, Claude Code treats the connection as failed if both of these are true:\n\n- the reply is not marked as an event stream\n\n- the reply has no header from the session service\n\nIn that case it logs that a proxy or gateway may have answered instead of the real server.\n\nThe connection also now records the time the server reports in its reply when it first connects.\n\n**Why**\n\nOn some networks a proxy, a company gateway or a hotel-style login page answers in place of the real server. Without this check Claude Code could treat that reply as a working connection. This makes Remote Control and other remote connections fail clearly in that situation instead of quietly misbehaving.\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}