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

#27458 [Bug]: Header value must be str or bytes, not float

  • State: open
  • Author: @xhejtman
  • Labels: bug, proxy, llm translation, claude code

### Check for existing issues

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

### What happened?

Hello,

it seems that if some extra headers are present, even latest stable version throws exception: ``` 2026-05-08T12:21:49.200718182+02:00 stderr F ^[[92m10:21:49 - LiteLLM Proxy:ERROR^[[0m: endpoints.py:121 - litellm.proxy.proxy_server.anthropic_response(): Exception occured - litellm.InternalServerError: InternalServerError: Hosted_vllmException - Header value must be str or bytes, not <class 'float'>. Received Model Group=kimi-k2.6 2026-05-08T12:21:49.200762885+02:00 stderr F Available Model Group Fallbacks=None LiteLLM Retried: 2 times, LiteLLM Max Retries: 2 2026-05-08T12:21:49.200768846+02:00 stderr F Traceback (most recent call last): 2026-05-08T12:21:49.200773695+02:00 stderr F File "/app/.venv/lib/python3.13/site-packages/litellm/llms/custom_httpx/llm_http_handler.py", line 180, in _make_common_async_call 2026-05-08T12:21:49.200778404+02:00 stderr F response = await async_httpx_client.post( 2026-05-08T12:21:49.200782983+02:00 stderr F ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-05-08T12:21:49.200788603+02:00 stderr F …

Open on GitHub

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d18h57m16s ago — entered · #import:https:::github.com:berriai:litellm post #1925
-/https://github.com/berriai/litellm/issues/272763:1-/https://github.com/berriai/litellm/issues/27458⭐
The right-side task requires coordinated schema normalization across API variants, provider compatibility handling, and broader regression coverage. The left-side task is narrower, mainly involving validation or normalization of outbound metadata values, with comparatively limited behavioral surface area.
#0 of 0 · 31d18h45m22s ago · #import:https:::github.com:berriai:litellm post #2130
-/https://github.com/berriai/litellm/issues/264114:1-/https://github.com/berriai/litellm/issues/27458⭐
A cross-layer asynchronous protocol and lifecycle fix requires deeper investigation, state handling, and end-to-end testing, whereas the other issue is likely a localized input-normalization or header-validation correction.
#0 of 0 · 31d18h36m31s ago · #import:https:::github.com:berriai:litellm post #2271
-/https://github.com/berriai/litellm/issues/328904:1-/https://github.com/berriai/litellm/issues/27458⭐
The left requires security-sensitive changes to outbound request handling, careful validation across execution paths, and regression testing for bypasses and network edge cases. The right is more likely a localized input-normalization fix with narrower testing and integration scope.
#0 of 0 · 31d17h44m16s ago — current · #import:https:::github.com:berriai:litellm post #3150
-/https://github.com/berriai/litellm/issues/291903:1-/https://github.com/berriai/litellm/issues/27458⭐
29190 requires validating an uncertain interaction, changing authentication precedence safely, and adding regression coverage across proxy and provider flows; 27458 is comparatively localized input validation and error-handling work.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search