litellm - 💡(How to fix) Fix Give Feedback / Get Help: [2 comments, 2 participants]

LiteLLM.Info: If you need to debug this error, use `litellm._turn_on_debug()'. LocalProtocolError Traceback (most recent call last) 102 except Exception as exc: The above exception was the direct cause of the following exception: LocalProtocolError Traceback (most recent call last) The above exception was the direct cause of the following exception: APIConnectionError Traceback (most recent call last) APIConnectionError: Connection error.

TL;DR

Remove the newline character from the Bearer token to fix the Illegal header value error.

Guidance

• Verify that the Bearer token does not contain any newline characters (\r\n) by checking how the token is generated and added to the request headers.
• Check the code that sets the Authorization header to ensure it properly handles the Bearer token without adding any newline characters.
• Use a debugger or print statements to inspect the Authorization header value before the request is sent to identify if the newline character is being added during the request preparation.
• Consider using a library or function that properly encodes and handles headers to avoid similar issues in the future.

Notes

The error message suggests that the issue is related to the formatting of the Bearer token in the Authorization header. However, without more information about how the token is generated and added to the request, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Remove any newline characters from the Bearer token before adding it to the Authorization header. This should fix the immediate issue, but it's recommended to investigate why the newline character is being added in the first place to prevent similar issues in the future.