{"version":"2.1.228","anchor":"api-client-request-handling-moved-to-a-middleware-chain","canonical_anchor":"api-client-request-handling-moved-to-a-middleware-chain","heading":"API client request handling moved to a middleware chain","tier":"internal","area":"API Client","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/api-client-request-handling-moved-to-a-middleware-chain","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### API client request handling moved to a middleware chain\n\nAPI requests are built through a middleware chain, and middleware errors no longer get retried as network failures.\n\n**What**\n\nClaude Code's copy of the Anthropic SDK builds requests through a middleware chain instead of overriding request preparation. Errors raised by middleware are no longer retried as if they were network failures.\n\n**Details**\n\n- Bedrock SigV4 signing and Vertex path rewriting run as middleware over a complete request; Vertex rewrites the URL path and strips the beta query parameter instead of editing a path field.\n- Bedrock reads the AWS region from the shared AWS config file and derives a default base URL from it.\n\n**Evidence**\n\n`middleware error (not retryable)`\n\n- Area: API Client\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}