{"version":"2.1.277","anchor":"gateway-upstream-providers-can-now-set-custom-headers","canonical_anchor":"gateway-upstream-providers-can-now-set-custom-headers","heading":"Gateway upstream providers can now set custom headers","tier":"use","area":"Gateway Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/gateway-upstream-providers-can-now-set-custom-headers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Gateway upstream providers can now set custom headers\n\nGateway upstream provider configs can now include custom headers\n\n**What**\n\nThe gateway's configuration schema for upstream providers (Bedrock, AnthropicAws, Vertex, and Foundry) now supports a `headers` field, letting an administrator attach custom HTTP headers to a specific upstream provider's requests alongside its existing authentication settings.\n\n**Why**\n\nThis gives self-hosted gateway operators more control over outgoing requests to each provider, for example to satisfy provider- or network-specific header requirements.\n\n- Area: Gateway Proxy\n- Names: `headers`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}