mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 14:39:31 -05:00
[GH-ISSUE #22380] Bug: Analytics page fails to load data for models with slashes in their ID (URL encoding issue) #19709
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 @schmidt-silas on GitHub (Mar 8, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22380
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.8.8
Ollama Version (if applicable)
No response
Operating System
Ubuntu 24.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When viewing the Analytics page, the frontend should properly URL-encode the forward slash (converting / to %2F) in the model ID before making the API request. The charts and data should then load successfully for models that contain a forward slash in their ID.
Actual Behavior
The frontend fails to properly URL-encode the forward slash in the model ID. As a result, the API request is made with the unencoded slash included as part of the URL path directory, which causes the charts and data to fail to load.
Steps to Reproduce
Logs & Screenshots
When checking the Docker logs, it is clear that colons are being encoded, but slashes are not.
For a local model:
GET /api/v1/analytics/models/huihui_ai/gpt-oss-abliterated%3Alatest/overview?days=30 HTTP/1.1" 200
(Notice the : is encoded to %3A, but the / remains a /)
For the failing external model:
GET /api/v1/analytics/models/anthropic/claude-opus-4.6/overview?days=30 HTTP/1.1" 304
(Similarly, the unencoded slash is sent as part of the path)
Additional Information
No response
@Classic298 commented on GitHub (Mar 8, 2026):
https://github.com/open-webui/open-webui/pull/22382
Testing needed and wanted @schmidt-silas
@silentoplayz commented on GitHub (Mar 8, 2026):
I've tested the PR linked and confirm it works as expected to solve OP's reported issue. Thanks for the report @schmidt-silas!