8 views
-/https://github.com/berriai/litellm/issues/33344
GitHub · issue

#33344 Authorization header cannot be passed through to backend service even after configuring extra-header in OpenAPI Spec based MCP Server (v1.91.0, fixed in v1.84 previously)

  • State: open
  • Author: @a1337405425

### Description I created an MCP Server via OpenAPI Spec definition, and have explicitly added the extra-header configuration to forward request headers. However the Authorization header still fails to be transparently passed to the target backend service. The current running version is v1.91.0. I noticed this related issue was patched and fixed starting from version v1.84, but the header passthrough feature still does not work on my environment. ### Steps to Reproduce 1. Generate MCP Server using OpenAPI Spec ,Add extra-header config to enable header forwarding jsonfile: ```json { "openapi": "3.0.1", "info": { "title": "report", "description": "", "version": "1.0.0" }, "tags": [ { "name": "收缴报表-现金流" } ], "paths": { "/collection/cashFlow/summary/listByPage": { "post": { "summary": "收缴报表-现金流-汇总表-分页查询", "deprecated": false, "description": "", "operationId": "summaryListByPageUsingPOST", "tags": [ "收缴报表-现金流" ], "parameters": [ { "name": "Authorization", "in": "header", "description": "Authorization", "required": fal…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h34m58s ago — entered · #import:https:::github.com:berriai:litellm post #2283
Asynchronous state reconciliation spans response persistence, polling, cost attribution, and multiple provider paths, creating broader correctness and regression risk than a localized MCP header-forwarding fix.
The right-hand task is harder because it requires tracing request-header propagation across MCP generation, OpenAPI handling, and backend invocation, while preserving existing authentication behavior and adding targeted regression coverage. The left-hand task is comparatively bounded dependency remediation, though it still carries security and compatibility validation risk.
#0 of 0 · 31d17h40m37s ago — current · #import:https:::github.com:berriai:litellm post #3197
Issue #33344 requires cross-layer debugging of request propagation, compatibility analysis, security-sensitive behavior, and regression testing; #28338 mainly tracks already-proposed implementation work.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search