litellm/gateway
Yujong Lee 1949baf3de fix(proxy): restore the client's peer behind Rust instead of trusting the Rust hop
Python now sees each request as if the client had connected to it directly.
The Rust hop sends the real TCP peer in x-litellm-rust-peer, an app middleware
puts it back into the ASGI scope, and uvicorn's ProxyHeadersMiddleware then
runs with the same trust settings Python alone would use. Server-level proxy
headers are off in supervised mode for uvicorn and gunicorn, since they would
judge the loopback hop. The trust-list merge that always trusted 127.0.0.1 is
gone, so operators keep the exact FORWARDED_ALLOW_IPS behavior they had.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 13:01:20 +09:00
..
routes feat(pass-through): add eu/jev decision API pass-through with spend tracking (#46875) 2026-10-29 17:52:43 -07:00
Dockerfile build: rename gateway distribution to litellm-proxy 2026-11-03 13:01:20 +09:00
launch.py fix(proxy): restore the client's peer behind Rust instead of trusting the Rust hop 2026-11-03 13:01:20 +09:00
main.py fix(proxy): preserve state through composed lifespans (#44214) 2026-10-02 10:56:52 -07:00