mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 19:38:46 -05:00
[GH-ISSUE #22613] issue: File processing fails due to case-sensitive check for 'xl/sharedStrings.xml' in .xlsx files #35294
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FragsterAt on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22613
Check Existing Issues
Installation Method
Other
Open WebUI Version
v0.8.10
Ollama Version (if applicable)
No response
Operating System
windows server 2008
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
The file should be processed successfully, regardless of the case of internal filenames (e.g., SharedStrings.xml or sharedStrings.xml).
Actual Behavior
When attempting to upload and process a valid .xlsx file via the OpenWebUI API, the system fails with the error:
Copy
"There is no item named 'xl/sharedStrings.xml' in the archive"
However, upon manual inspection of the .xlsx file (which is a ZIP archive), the file xl/SharedStrings.xml does exist, but the first letter of the filename is uppercase (SharedStrings.xml instead of sharedStrings.xml).
This suggests that the file processing logic in OpenWebUI performs a case-sensitive check for the presence of xl/sharedStrings.xml, which fails for files where the filename uses a different case (e.g., SharedStrings.xml). This is problematic because:
The Office Open XML (OOXML) specification does not enforce a specific case for internal filenames in .xlsx files.
Many tools (including Microsoft Excel and LibreOffice) may generate .xlsx files with varying filename cases, leading to false negatives during processing.
Steps to Reproduce
Steps to Reproduce:
Upload test.xlsx file to OpenWebUI chat.
Observe the error: "There is no item named 'xl/sharedStrings.xml' in the archive".
Logs & Screenshots
Additional Information
No response
@tjbck commented on GitHub (Mar 24, 2026):
This is an upstream issue and needs to be addressed from openpyxl