Inconsistent fileConfig Restrictions for Custom Endpoints Between SidePanel and Direct File Upload #6297
Unanswered
skyking363
asked this question in
Troubleshooting
Replies: 1 comment
-
For custom endpoints, you need to use I will add support for using the custom endpoint name to single-out specific custom endpoints. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What happened?
Description
While using LibreChat, I’ve noticed that the
fileConfig
settings for custom endpoints (e.g., "Deepseek") correctly restrict file uploads in the SidePanel, but fail to do so in the direct upload interface (e.g., the paperclip icon), allowing unsupported file types to be uploaded. In contrast, other native endpoints (e.g., "bedrock") consistently applyfileConfig
restrictions in both the SidePanel and direct upload scenarios.Configuration Details
Here is the relevant section of my
librechat.yaml
file related tofileConfig
:Problem Details
Behavior in SidePanel:
In the SidePanel, when I attempt to upload an image file (MIME type "image/.") to the "Deepseek" endpoint, the system correctly blocks the upload and displays an error message. This is expected since "Deepseek"’s
supportedMimeTypes
only allows "text/.", "application/.", and "application/x-sh", explicitly excluding "image/.".Behavior in Direct Upload:
However, when I use the direct upload feature (e.g., clicking the paperclip icon) to upload the same image file to the "Deepseek" endpoint, the system allows the upload to succeed, despite the
fileConfig
explicitly restricting supported MIME types. This behavior is inconsistent with expectations.Behavior of Other Endpoints
The "bedrock" endpoint has the same
supportedMimeTypes
as "Deepseek", excluding "image/.*". It’s expected to block image uploads in both the SidePanel and direct upload. However, since the YAML doesn’t clarify whether "bedrock" is a custom endpoint, further confirmation is needed to determine if it exhibits the same inconsistency.Expected Behavior
The
fileConfig
settings for custom endpoints (e.g., "Deepseek") should consistently enforce restrictions in both the SidePanel and direct upload interfaces. For example, if "image/.*" is excluded fromsupportedMimeTypes
, image uploads should be blocked regardless of the upload method (SidePanel or direct upload).Request
Please investigate and fix the issue where custom endpoints fail to apply
fileConfig
settings correctly during direct uploads, ensuring that file upload restrictions are consistently enforced across all upload paths (SidePanel and direct upload).Version Information
LibreChat Version: v0.7.7
Steps to Reproduce
librechat.yaml
file related tofileConfig
:What browsers are you seeing the problem on?
No response
Relevant log output
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions