6 views
-/https://github.com/berriai/litellm/issues/31586
GitHub · issue

#31586 [Bug]: http -> https issue

  • State: open
  • Author: @matteo-rama
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

i have deployed litellm via helm chart. the ingress controller speak "http" with the outside part of cluster. outside cluster i have a tls termination, so client arrive via https

the drawing is

https --> NGINX ---> http --> KUBE --> http --> litellm

what happen often and it's hard to track for me is that i got a few redirect to http

example

` http://litellm.k8s.fabrick.dmz.tst/ui/login/?redirect_to=https%3A%2F%2Flitellm.k8s.fabrick.dmz.tst%2Fui%2Fmcp-servers%2F `

the "redirect_to" is actually correct (https) while the 'real' redirect was http

i did set in the helm chart

``` envVars: PROXY_BASE_URL: "https://litellm.k8s.fabrick.dmz.tst" FORWARDED_ALLOW_IPS: "*" ```

### Steps to Reproduce

1. 2. 3.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

_No response_

### What LiteLLM version are you on ?

v1.90.0

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d19h12m43s ago — entered · #import:https:::github.com:berriai:litellm post #1761
The left issue is harder because it requires diagnosing request-scheme propagation across multiple proxy layers and safely correcting framework redirect behavior, with environment-dependent testing. The right issue is comparatively localized to Helm image-tag defaults and release validation.
#0 of 0 · 31d18h45m52s ago — current · #import:https:::github.com:berriai:litellm post #2203
Issue 31030 requires tracing and aligning parameter-sanitization behavior across distinct request translation paths, provider capabilities, and regression coverage. Issue 31586 is more localized to proxy URL/forwarded-header handling and deployment configuration. The former has broader compatibility and testing risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search