Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Bedrock streaming responses without a content-type no longer fail

Use it now
Useful4 Signal3
Bedrock Notable not in their notes

Bedrock streaming replies missing a content-type now work, and a new env var restores the old strict check.

CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT
What

A Bedrock streaming response that arrives with no content-type header at all is now treated as application/vnd.amazon.eventstream instead of being rejected. Set CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT to turn the defaulting off and get the old strict behaviour.

Details
  • Only applies when the header is absent; a wrong content-type still fails the check.
  • Separately, the default AWS credential chain now builds its STS endpoint through a region helper instead of pasting the region into a hardcoded URL.
Evidence

CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →