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

[PR #15581] [CLOSED] feat: prepare for subpath #23876

New Issue
Closed
opened 2026-04-20 05:05:45 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 05:05:45 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/15581
Author: @guenhter
Created: 7/8/2025
Status: ❌ Closed

Base: dev ← Head: prepare-for-subpath

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests to validate the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

The request of hosting Open WebUI under a subpath (e.g. http://localhost/foobar/) is not new. Some attempt were already done in the past, but non of them made it: https://github.com/open-webui/open-webui/pull/10440, https://github.com/open-webui/open-webui/pull/2148, https://github.com/open-webui/open-webui/pull/1701

All of them tried the same approach: Changing the OWUI to relative paths.

Using relative paths is a critical thing, because we'd have to consider a lot of edge cases. Having absolute paths is here way more robust and easy to develop.

This PR prepares now everything that subpathing can be done quite easy with only a few minor steps. So it is then very easy to host OWUI not longer directly under "/" but e.g. under "/some/".

It is important, that paths always stays absolute paths.

If no base-path is defined, nothing changes. All the paths stay exactly as they are!

Subpathing will be done with those (manual) steps:

  • Change two files in the Docker Container (index.html and some generated .js file)
  • Create a reverse proxy which strips the paths for the backend

When this PR gets merged, I'll create a new PR in the docs repo to give some guideline what needs to be done to make the subpath work.

Changed

  • Adapt a lot of URLs to support base-paths prepending

Screenshots or Videos

subpath

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/15581 **Author:** [@guenhter](https://github.com/guenhter) **Created:** 7/8/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `prepare-for-subpath` --- ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description The request of hosting Open WebUI under a subpath (e.g. http://localhost/foobar/) is not new. Some attempt were already done in the past, but non of them made it: https://github.com/open-webui/open-webui/pull/10440, https://github.com/open-webui/open-webui/pull/2148, https://github.com/open-webui/open-webui/pull/1701 All of them tried the same approach: Changing the OWUI to relative paths. Using relative paths is a critical thing, because we'd have to consider a lot of edge cases. Having absolute paths is here way more robust and easy to develop. This PR prepares now everything that subpathing can be done quite easy with only a few minor steps. So it is then very easy to host OWUI not longer directly under `"/"` but e.g. under `"/some/"`. It is important, that paths always stays absolute paths. **If no base-path is defined, nothing changes. All the paths stay exactly as they are!** Subpathing will be done with those (manual) steps: * Change two files in the Docker Container (`index.html` and some generated `.js` file) * Create a reverse proxy which strips the paths for the backend When this PR gets merged, I'll create a new PR in the docs repo to give some guideline what needs to be done to make the subpath work. ### Changed - Adapt a lot of URLs to support base-paths prepending --- ### Screenshots or Videos ![subpath](https://github.com/user-attachments/assets/0ece33e8-26bb-411b-a450-19974fd00c0e) ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 05:05:46 -05:00
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 pull-request
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#23876
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?