Skip to content

fix: remove raw request flag from providers which don't support it - #4058

Merged
akshaydeo merged 1 commit into
devfrom
06-04-fix_remove_raw_request_flag_from_providers_which_don_t_support_it
Jun 5, 2026
Merged

fix: remove raw request flag from providers which don't support it#4058
akshaydeo merged 1 commit into
devfrom
06-04-fix_remove_raw_request_flag_from_providers_which_don_t_support_it

Conversation

@TejasGhatte

@TejasGhatte TejasGhatte commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

When an Anthropic-type route's default provider is not found in the available providers list, the router falls back to the first available provider. However, raw request body passthrough is only valid for providers that natively speak the Anthropic Messages API (Anthropic, Vertex, Azure). If the fallback provider is something like Bedrock, leaving the raw passthrough flag enabled causes incorrect behavior since Bedrock requires its own format conversion.

Changes

  • When the router falls back to the first available provider on an Anthropic-type route, the BifrostContextKeyUseRawRequestBody flag is explicitly cleared if the fallback provider is not one of the natively Anthropic-compatible providers (Anthropic, Vertex, Azure). This ensures the selected provider performs its own format conversion rather than attempting to pass through an incompatible raw request body.

Type of change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (React)
  • Docs

How to test

Configure an Anthropic-type route where the default provider is unavailable and the fallback resolves to a non-native provider such as Bedrock. Send a request and verify that the provider correctly performs format conversion rather than passing through the raw Anthropic-formatted body.

go test ./...

Breaking changes

  • Yes
  • No

Related issues

Security considerations

None.

Checklist

  • I read docs/contributing/README.md and followed the guidelines
  • I added/updated tests where appropriate
  • I updated documentation where needed
  • I verified builds succeed (Go and UI)
  • I verified the CI pipeline passes locally if applicable

Summary by CodeRabbit

  • Bug Fixes

    • Ensure Anthropic-type routes disable raw request/response passthrough when a fallback provider requires its own request/response formatting, so downstream providers receive data in their expected format.
  • Tests

    • Added an integration test validating passthrough flags are cleared and handler behavior when such a fallback provider is selected.

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 50b64419-5fc8-42b9-9653-53a9db31c64d

📥 Commits

Reviewing files that changed from the base of the PR and between c0094f5 and 6ae8983.

📒 Files selected for processing (2)
  • transports/bifrost-http/integrations/router.go
  • transports/bifrost-http/integrations/router_test.go

📝 Walkthrough

Walkthrough

Router adjustments ensure that for Anthropic routes, when the model catalog falls back to a non-native provider (e.g., Bedrock), the handler clears Bifrost context flags that enabled raw request/response passthrough so the downstream provider performs its own conversion. An integration test verifies this behavior.

Changes

Anthropic Provider Fallback Handling

Layer / File(s) Summary
Raw request & passthrough flag adjustment + test
transports/bifrost-http/integrations/router.go, transports/bifrost-http/integrations/router_test.go
When GenericRouter.createHandler selects a fallback provider for an Anthropic route that is not schemas.Anthropic, schemas.Vertex, or schemas.Azure, it clears BifrostContextKeyUseRawRequestBody, BifrostContextKeySendBackRawResponse, and BifrostContextKeyPassthroughOverridesPresent. Adds TestCreateHandler_AnthropicRouteClears_UseRawRequestBody_WhenCatalogSelectsBedrock to assert the flags are cleared when Bedrock is selected.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

  • akshaydeo
  • danpiths

Poem

🐰 In Bifrost halls I nudge the flow,
When Anthropic falls where Bedrock goes,
I clear the flags of raw request,
So downstream formats do their best. ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: removing/clearing the raw request flag when fallback providers don't support it.
Description check ✅ Passed The description covers all essential template sections including summary, changes, type of change, affected areas, testing instructions, breaking changes, and checklist items.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 06-04-fix_remove_raw_request_flag_from_providers_which_don_t_support_it

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"


Comment @coderabbitai help to get the list of available commands and usage tips.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


tejas ghatte seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Copy Markdown
Collaborator Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@TejasGhatte
TejasGhatte marked this pull request as ready for review June 4, 2026 14:35
@greptile-apps

greptile-apps Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

Safe to merge — the change is narrowly scoped to the model-catalog fallback path on Anthropic-type routes, and the three context flags are now cleared together rather than partially.

The fix correctly identifies and clears all three passthrough context keys when the catalog selects a non-native provider. The new test exercises the full path (claude-code user-agent → passthrough flags set → catalog selects Bedrock → flags cleared) and will catch a regression if the clearing is removed. The only observation is a pre-existing design nuance around mixed-provider lists with failover, which is not a regression introduced here.

No files require special attention; both changed files are clean.

Important Files Changed

Filename Overview
transports/bifrost-http/integrations/router.go Adds flag-clearing logic when the model-catalog fallback lands on a non-native provider; all three passthrough context keys are now reset together.
transports/bifrost-http/integrations/router_test.go Adds a regression test that verifies all three passthrough flags are false in the RequestConverter when the catalog selects Bedrock as the fallback provider on an Anthropic-type route.

Reviews (2): Last reviewed commit: "fix: remove raw request flag from provid..." | Re-trigger Greptile

Comment thread transports/bifrost-http/integrations/router.go
Comment thread transports/bifrost-http/integrations/router.go
@TejasGhatte
TejasGhatte force-pushed the 06-04-fix_remove_raw_request_flag_from_providers_which_don_t_support_it branch from c0094f5 to 6ae8983 Compare June 4, 2026 16:45

akshaydeo commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Merge activity

  • Jun 5, 1:43 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jun 5, 1:44 PM UTC: @akshaydeo merged this pull request with Graphite.

@akshaydeo
akshaydeo merged commit cc70134 into dev Jun 5, 2026
15 of 16 checks passed
@akshaydeo
akshaydeo deleted the 06-04-fix_remove_raw_request_flag_from_providers_which_don_t_support_it branch June 5, 2026 13:44
@akshaydeo akshaydeo mentioned this pull request Jun 7, 2026
akshaydeo pushed a commit that referenced this pull request Jun 7, 2026
…4058)

## Summary

When an Anthropic-type route's default provider is not found in the available providers list, the router falls back to the first available provider. However, raw request body passthrough is only valid for providers that natively speak the Anthropic Messages API (Anthropic, Vertex, Azure). If the fallback provider is something like Bedrock, leaving the raw passthrough flag enabled causes incorrect behavior since Bedrock requires its own format conversion.

## Changes

- When the router falls back to the first available provider on an Anthropic-type route, the `BifrostContextKeyUseRawRequestBody` flag is explicitly cleared if the fallback provider is not one of the natively Anthropic-compatible providers (Anthropic, Vertex, Azure). This ensures the selected provider performs its own format conversion rather than attempting to pass through an incompatible raw request body.

## Type of change

- [x] Bug fix
- [ ] Feature
- [ ] Refactor
- [ ] Documentation
- [ ] Chore/CI

## Affected areas

- [ ] Core (Go)
- [x] Transports (HTTP)
- [x] Providers/Integrations
- [ ] Plugins
- [ ] UI (React)
- [ ] Docs

## How to test

Configure an Anthropic-type route where the default provider is unavailable and the fallback resolves to a non-native provider such as Bedrock. Send a request and verify that the provider correctly performs format conversion rather than passing through the raw Anthropic-formatted body.

```sh
go test ./...
```

## Breaking changes

- [ ] Yes
- [x] No

## Related issues

## Security considerations

None.

## Checklist

- [ ] I read `docs/contributing/README.md` and followed the guidelines
- [ ] I added/updated tests where appropriate
- [ ] I updated documentation where needed
- [ ] I verified builds succeed (Go and UI)
- [ ] I verified the CI pipeline passes locally if applicable

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

* **Bug Fixes**
  * Ensure Anthropic-type routes disable raw request/response passthrough when a fallback provider requires its own request/response formatting, so downstream providers receive data in their expected format.

* **Tests**
  * Added an integration test validating passthrough flags are cleared and handler behavior when such a fallback provider is selected.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
akshaydeo added a commit that referenced this pull request Jun 7, 2026
## ✨ Features

- **OpenAI Compaction** — Added OpenAI conversation compaction support
across core, framework, logging, and the API surface (#4053)
- **Multi-Customer & Org Hierarchy** — Logs and usage tracking now
support multiple customers, teams, and business units, including
business unit CRUD, team assignment, and governance endpoints in the
OpenAPI spec (#4066, #4041, #4082)
- **Provider-Level Governance** — Budgets & limits are now scope-aware
and can be applied at the virtual-key top level and per provider, wired
from the model configs table, with UI filters for scope and providers
(#3938, #3937, #3939, #3981, #3962)
- **Customer Budgets** — Customers support multiple budgets and
`calendar_aligned` budget windows (#3998, #3997)
- **Virtual Key Attribution & Controls** — Added a `created_by` user
attribution column and a `blacklisted_models` column for virtual key
provider configs (#3672, #3653)
- **Request Header Capture** — OTel and Maxim observability plugins
capture `request_headers` by pattern, with wildcard support (e.g.
`x-custom-*`); logging gained the same wildcard header capture (#4012,
#3958)
- **OTel Content Controls & Collectors** — New `disable_content_logging`
option drops message/tool content from exported spans, plus support for
multiple OTel collectors (#4064, #3894)
- **xAI x_search** — Added xAI `x_search` tool support (#3976)
- **URL Validation** — Added fetch URL validation with private-network
configuration and link-local blocking (#3947, #3991)
- **File Scheme Pricing URLs** — Pricing source URLs now accept the
`file://` scheme for air-gapped and self-hosted deployments (#4045)
- **Paginated Virtual Keys** — Virtual key fetching is paginated to
handle deployments with very large numbers of keys (#3957)
- **Client IP Resolution** — Resolve client IP from
`X-Forwarded-For`/`X-Real-IP` headers
- **SCIM Provisioning** — Added `attributeType`/`attributeValue` SCIM
provisioning fields
- **Helm/Config Schema** — Added `roles` RBAC governance config and
`per_user_oauth` MCP auth to the Helm chart and config schema (#4004,
#4009)
- **Log Navigation UI** — Added a "View logs" menu item to customer,
team, and virtual key tables, clickable links in log detail views, a
customer detail sheet, and a reusable `BudgetDisplay` component (#4073,
#4054, #4026, #4055)
- **Faster First Paint** — Added an inline loading shell to `#root`
before React mounts (#4063)
- **Materialized View Alias** — Added an `alias` column to the
materialized view with filter support (#4078)

## 🐞 Fixed

- **Fetch URL IP Checks** — Hardened fetch URL IP checks against SSRF
(#4092)
- **Mantle Model Matching** — Broadened Mantle model matching to all
`gpt` variants (#4091)
- **Empty Thinking Blocks** — Strip thinking blocks when the signature
is empty (#4079)
- **OpenAI Stream Usage** — Removed usage from the `responses.created`
event in the OpenAI stream (#4080)
- **Prompt Cache Key** — Set the prompt cache key from the Anthropic
integration (#4086)
- **Upstream Failure Status** — Map upstream connection failures to 502
instead of 400 (#3929) (thanks
[@chris-colinsky](https://github.com/chris-colinsky)!)
- **Gemini Schema Constraints** — Accept numeric schema integer
constraints for Gemini (#3994) (thanks
[@yanhao98](https://github.com/yanhao98)!)
- **Files Provider Param** — Accept the `?provider=` query param on `GET
/v1/files` (#3971) (thanks [@alexef](https://github.com/alexef)!)
- **Optional Batch Model** — Made the `model` field optional on `POST
/v1/batches` (#3973) (thanks [@alexef](https://github.com/alexef)!)
- **Helm Azure Config** — Added missing `azure_key_config` fields to the
Helm schema (#3996) (thanks
[@axelray-dev](https://github.com/axelray-dev)!)
- **Text Completion Chunk Model** — Added the missing `Model` field to
`TextCompletionChunkResponse` (#3970) (thanks
[@kuishou68](https://github.com/kuishou68)!)
- **MCP Inline stdio Env** — MCP stdio server configs accept inline
environment variable assignments (#3861) (thanks
[@Shushmitaaaa](https://github.com/Shushmitaaaa)!)
- **Orphaned Tool Results** — Orphaned tool results in the OpenAI to
Anthropic conversion flow are no longer rejected by the Anthropic API
(#3919)
- **Node Usage Reconciliation** — Added a monotonic `inc_number` log
cursor so node usage reconciliation does not skip late async log writes
(#3664)
- **Bedrock Output Assessments** — Corrected the type of
`outputAssessments` in Bedrock responses (#4028)
- **Model Pool Pricing Reloads** — Preserve non-pricing model pool
entries across pricing reloads (#3999)
- **Ghost Node Reconciliation** — Replicate the VK hierarchy flow for
ghost node reconciliation (#4088)
- **VK Double Usage Counting** — Fixed double usage counting when
creating a virtual key (#4070)
- **Model Config Lifecycle** — Cascade deletes for model configs and
removal of stale in-memory model configs (#4051, #4043)
- **FTS Index Cap** — Reduced the FTS index `left()` cap from 800k to
250k chars to stay within the tsvector limit (#4057)
- **Sync Worker Drift** — Reduced the sync worker ticker period to 5m to
prevent threshold drift (#4023)
- **Passthrough** — Fixed passthrough budgets, gated passthrough models
per VK, model extraction for Azure passthrough, and restricted
fallbacks/provider selection to the VK boundary (#3941, #3988, #3983,
#3924)
- **Provider Response Headers** — Strip provider response headers and
add a content-type filter (#3955, #4024)
- **Stream Handling** — Drain non-SSE stream readers and retry stale
connections (#3956, #3967)
- **Azure Claude** — Strip Azure diagnostic property for Claude models
(#3925)
- **Compat max_tokens** — Preserve chat `max_tokens` during param
filtering (#3992)
- **Raw Request Flag** — Removed the raw request flag from providers
that don't support it (#4058)
- **UI Fixes** — Standardized page container layout, virtual key model
configs UI, and dashboard chart tooltips (#4046, #4052, #4044)

## 🔧 Maintenance

- **Dependency Upgrades** — Bumped transitive `golang.org/x`
dependencies (crypto, net, sys, text) for Docker Scout CVE remediation
and `recharts` to 3.8.1; cascaded version bumps across all modules
(#3900, #4003)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants