{"version":"2.1.239","anchor":"bedrock-streaming-responses-without-a-content-type-no-longer","canonical_anchor":"bedrock-streaming-responses-without-a-content-type-no-longer","heading":"Bedrock streaming responses without a content-type no longer fail","tier":"use","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/bedrock-streaming-responses-without-a-content-type-no-longer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Bedrock streaming responses without a content-type no longer fail\n\nBedrock streaming replies missing a content-type now work, and a new env var restores the old strict check.\n\n**What**\n\nA 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.\n\n**Details**\n\n- Only applies when the header is absent; a wrong content-type still fails the check.\n- Separately, the default AWS credential chain now builds its STS endpoint through a region helper instead of pasting the region into a hardcoded URL.\n\n**Evidence**\n\n`CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT`\n\n- Area: Bedrock\n- Names: `CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}