{"version":"2.1.274","anchor":"sse-transport-reconnect-fixed-stale-variable-bugs-in-header","canonical_anchor":"sse-transport-reconnect-fixed-stale-variable-bugs-in-header","heading":"SSE transport reconnect: fixed stale-variable bugs in header refresh and retry logging","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/sse-transport-reconnect-fixed-stale-variable-bugs-in-header","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### SSE transport reconnect: fixed stale-variable bugs in header refresh and retry logging\n\nFixed a bug where refreshed auth headers weren't actually applied on SSE reconnect, and retry logs showed the wrong status\n\n**What**\n\nWhen Claude Code's SSE (Server-Sent Events, a streaming connection type) transport reconnects, it refreshes authentication headers, but a bug meant the freshly computed headers weren't actually applied to the request \u2014 an undefined or stale variable was used instead. This is now fixed so the real refreshed headers are assigned. A related bug in POST-retry logging and telemetry, where the logged response status or error came from a mismatched variable left over from a previous iteration, is also fixed to report the actual current status.\n\n**Why**\n\nBefore this fix, a reconnecting SSE connection could silently keep using stale credentials, and retry logs could report misleading status information, both of which made connection problems harder to diagnose.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}