{"version":"2.1.228","anchor":"gateway-no-longer-forwards-client-auth-headers-upstream","canonical_anchor":"gateway-no-longer-forwards-client-auth-headers-upstream","heading":"Gateway no longer forwards client auth headers upstream","tier":"notice","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-no-longer-forwards-client-auth-headers-upstream","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway no longer forwards client auth headers upstream\n\nThe self-hosted gateway strips your client's API key before calling upstream providers.\n\n**What**\n\nEvery path where the self-hosted gateway attaches its own operator credential to an upstream provider request now deletes the inbound `authorization` and `x-api-key` headers first, so a key supplied by the client can no longer reach the upstream alongside the gateway's own.\n\n**Evidence**\n\n`(r.delete(\"authorization\"), r.delete(\"x-api-key\"));`\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}