You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I sent a request to Gemini on Litellm proxy with the image in URL format instead of BASE64 format.
In that case, if the image URL ended with an extension, it succeeded without any problem.
However, when the image URL did not end with an extension, a 500 error occurred.
There are many cases where the URL of an image does not end with an extension, such as a signed URL in S3 or a SAS URL in Azure BLOB Storage.
Therefore, we would appreciate it if you could add a process to properly determine the file type in order to combine this with a mechanism to securely publish sensitive data.
Relevant log output
No response
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
What happened?
Hi there!
I sent a request to Gemini on Litellm proxy with the image in URL format instead of BASE64 format.
In that case, if the image URL ended with an extension, it succeeded without any problem.
However, when the image URL did not end with an extension, a 500 error occurred.
Request Format
Error Message
From the error message, I think the cause is that the following process determines the file type at the end of the URL.
https://github.com/BerriAI/litellm/blob/main/litellm/llms/prompt_templates/factory.py#L666-L678
There are many cases where the URL of an image does not end with an extension, such as a signed URL in S3 or a SAS URL in Azure BLOB Storage.
Therefore, we would appreciate it if you could add a process to properly determine the file type in order to combine this with a mechanism to securely publish sensitive data.
Relevant log output
No response
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: