issue: random route responds with 200 instead of 401 #5487

New Issue

GiteaMirror · 2025-11-11T16:22:24-06:00

GiteaMirror commented

2025-11-11 16:22:24 -06:00

Originally created by @maurerle on GitHub (Jun 9, 2025).

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.13

Ollama Version (if applicable)

No response

Operating System

Debian 12

Browser (if applicable)

Firefox

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Visiting openwebui at /xmlrpc.php or whatever responds with a redirect which responds with a 200.

This triggers some Security products of our IT, demanding to switch of this behavior.
It would be good, if endpoints which do not exist fail early without a login and do not respond 200

Actual Behavior

any call is redirected and responded with 200 in the first place, even if it does not exist.
Having 401 when redirecting to /auth in

await goto(/auth?redirect=${encodedUrl}); might be a good fix for this

Steps to Reproduce

open Developer options in browser
visit http://openwebui/xmlrpc.php
see return code of requests

Logs & Screenshots

nothing provided

Additional Information

No response

Originally created by @maurerle on GitHub (Jun 9, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.13 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### Browser (if applicable) Firefox ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Visiting openwebui at /xmlrpc.php or whatever responds with a redirect which responds with a 200. This triggers some Security products of our IT, demanding to switch of this behavior. It would be good, if endpoints which do not exist fail early without a login and do not respond 200 ### Actual Behavior any call is redirected and responded with 200 in the first place, even if it does not exist. Having 401 when redirecting to /auth in `await goto(`/auth?redirect=${encodedUrl}`);` might be a good fix for this ### Steps to Reproduce 1. open Developer options in browser 2. visit http://openwebui/xmlrpc.php 3. see return code of requests ### Logs & Screenshots nothing provided ### Additional Information _No response_

GiteaMirror added the bug label 2025-11-11 16:22:24 -06:00

GiteaMirror closed this issue

2025-11-11 16:22:25 -06:00

GiteaMirror commented

2025-11-11 16:22:26 -06:00

@tjbck commented on GitHub (Jun 10, 2025):

We're using CSR (SPA) for Open WebUI, this is an intended behaviour. However, we're open to PRs addressing your described feature.

@tjbck commented on GitHub (Jun 10, 2025): We're using CSR (SPA) for Open WebUI, this is an intended behaviour. However, we're open to PRs addressing your described feature.

GiteaMirror referenced this issue

2026-04-19 20:30:43 -05:00

[GH-ISSUE #5487] Limit access to certain functions for various users #13999

GiteaMirror referenced this issue

2026-04-25 03:54:43 -05:00

[GH-ISSUE #5487] Limit access to certain functions for various users #29527

GiteaMirror referenced this issue

2026-05-05 13:45:51 -05:00

[GH-ISSUE #5487] Limit access to certain functions for various users #52665

Sign in to join this conversation.