Skip to content

docs(proxy): document LITELLM_CORS_EXPOSE_HEADERS env var#552

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
litellm_cors_expose_headers_doc
Open

docs(proxy): document LITELLM_CORS_EXPOSE_HEADERS env var#552
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
litellm_cors_expose_headers_doc

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Summary

Documents the new LITELLM_CORS_EXPOSE_HEADERS env var in the proxy environment variables reference, alongside the existing LITELLM_CORS_ORIGINS / LITELLM_CORS_ALLOW_CREDENTIALS entries. The var lets operators expose additional x-litellm-* response headers via Access-Control-Expose-Headers so browser clients calling the proxy cross-origin can read them (e.g. x-litellm-response-cost, x-litellm-model-api-base)

Pairs with the code change in BerriAI/litellm#33125. The litellm repo's documentation validation CI checks out this docs repo and asserts every os.getenv(...) key is documented in config_settings.md, so that check stays red until this merges

Link to Devin session: https://app.devin.ai/sessions/4db978bbfa1045a8a89c634e6648eeba

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Jul 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Jul 13, 2026 10:18pm

Request Review

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.

0 participants