github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-08 12:58:11 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #14530] issue: incorrect user name encoding after Trusted Header Auth sign up #55958

New Issue
Closed
opened 2026-05-05 18:22:52 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-05 18:22:52 -05:00
Owner
Copy Link

Originally created by @theuargb on GitHub (May 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14530

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.10

Ollama Version (if applicable)

No response

Operating System

Windows

Browser (if applicable)

Chrome

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

Non-ascii characters supported for users signed up with Trusted Headers

Actual Behavior

If the trusted header "name" is cyrrylic - OpenWebUI user name is broken, but account works fine overall

Steps to Reproduce

  1. Configure Trusted Headers Auth
  2. Sign In with account with cyrrylics in the name

Logs & Screenshots

Image

Image

Additional Information

No response

Originally created by @theuargb on GitHub (May 30, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14530 ### 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.10 ### Ollama Version (if applicable) _No response_ ### Operating System Windows ### Browser (if applicable) Chrome ### 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 Non-ascii characters supported for users signed up with Trusted Headers ### Actual Behavior If the trusted header "name" is cyrrylic - OpenWebUI user name is broken, but account works fine overall ### Steps to Reproduce 1. Configure Trusted Headers Auth 2. Sign In with account with cyrrylics in the name ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/4e8a32cf-c17b-483e-9544-f72c2108dc4d) ![Image](https://github.com/user-attachments/assets/283967e9-4d7c-403b-847d-0a04710bb218) ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-05 18:22:52 -05:00
GiteaMirror commented 2026-05-05 18:22:53 -05:00
Author
Owner
Copy Link

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

HTTP headers officially only support ASCII as per the HTTP standards, so non-ASCII names (like Cyrillic) aren’t supported by spec by default, hence the issue. PR welcome if you want to add optional Base64 (for encoding and decoding non-ascii chars) support, but we won't officially support it as it’s against the HTTP standard.

<!-- gh-comment-id:2954133563 --> @tjbck commented on GitHub (Jun 8, 2025): HTTP headers officially only support ASCII as per the HTTP standards, so non-ASCII names (like Cyrillic) aren’t supported by spec by default, hence the issue. PR welcome if you want to add optional Base64 (for encoding and decoding non-ascii chars) support, but we won't officially support it as it’s against the HTTP standard.
GiteaMirror commented 2026-05-05 18:22:54 -05:00
Author
Owner
Copy Link

@theuargb commented on GitHub (Jun 8, 2025):

hi @tjbck
thank you for the reply

traefik/whoami, which I use to test headers, supports them in cyrrylics somehow without me base64encoding them before.

if I understood you correctly you proposing to manually base64 them on the authenicator side and then decode inside the openwebui?

<!-- gh-comment-id:2954147375 --> @theuargb commented on GitHub (Jun 8, 2025): hi @tjbck thank you for the reply `traefik/whoami`, which I use to test headers, supports them in cyrrylics somehow without me base64encoding them before. if I understood you correctly you proposing to manually base64 them on the authenicator side and then decode inside the openwebui?
GiteaMirror commented 2026-05-05 18:22:54 -05:00
Author
Owner
Copy Link

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

Yes, sounds about right!

<!-- gh-comment-id:2954292088 --> @tjbck commented on GitHub (Jun 8, 2025): Yes, sounds about right!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#55958
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?