Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

Proxy request forwarding gains an explicit header allow/deny list

Proxy request forwarding now strips sensitive headers and keeps only an allowed set of prefixes

You'll notice Improvements
JSON All of v2.1.277
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.277,
ImprovementsSection of the release
What

When Claude Code forwards requests through a proxy, it now applies explicit rules about which HTTP headers (the metadata sent alongside a request) are allowed through. Headers considered sensitive or connection-specific, such as authorization, x-api-key, host, and content-length, are stripped out. Headers whose names start with certain prefixes, including anthropic-, x-stainless-, x-claude-gateway-, x-goog-, x-amz-, and x-amzn-, are kept. New validity checks also confirm header names and values are well-formed.

Why

This reduces the risk of sensitive credentials or connection-specific headers leaking through a proxied request, while still allowing the specific headers that upstream services need to function correctly.

See this entry in the whole of v2.1.277 →

Feedback