Skip to content
Discussion options

You must be logged in to vote

The litellm x-pass- workaround failed to change behavior, so litellm is probably not the culprit (header filtering would have been bypassed). The most likely cause is one of:

  1. cliproxyapi strips or rewrites anthropic-beta headers on the OAuth-mediated path. This is the leading hypothesis — the project (router-for-me/CLIProxyAPI) normalizes requests for OAuth compatibility.
  2. Anthropic's Max OAuth path itself doesn't accept extended-cache-ttl-2025-04-11. The March 2026 default downgrade from 1h → 5m may have actually been a capability removal on the subscription path, not
    just a default change. The ENABLE_PROMPT_CACHING_1H workaround may only work for Claude Code's native OAuth flow, which t…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by ironbelly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant