{"version":"2.1.228","anchor":"vertex-clients-no-longer-send-a-stale-authorization-header","canonical_anchor":"vertex-clients-no-longer-send-a-stale-authorization-header","heading":"Vertex clients no longer send a stale Authorization header","tier":"notice","area":"Vertex","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/vertex-clients-no-longer-send-a-stale-authorization-header","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Vertex clients no longer send a stale Authorization header\n\nOn Vertex, stale Authorization headers no longer clash with Google's own credentials.\n\n**What**\n\nWhen Claude Code talks to Anthropic models on Google Vertex, the HTTP client now blanks out `Authorization` (and `X-Api-Key`, unless a check passes) so Google's own auth client is the only thing supplying credentials. If auth resolution is skipped, your own `Authorization` value is passed through instead.\n\n**Details**\n\n- The blanking happens through default headers set at client construction time, so it applies to every request that client makes.\n- Where credential resolution is bypassed, the caller-supplied value travels as a separate `wireAuthorization` field rather than being dropped.\n- The client's internal auth promise now has a no-op catch, so a failed credential fetch no longer surfaces as an unhandled promise rejection.\n\n**Evidence**\n\n`wireAuthorization`\n\n- Area: Vertex\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}