[PR #9068] [MERGED] **feat** Add user related headers when calling an external embedding api #22312

New Issue

GiteaMirror · 2026-04-20T04:04:04-05:00

GiteaMirror commented

2026-04-20 04:04:04 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/9068
Author: @df-cgdm
Created: 1/29/2025
Status: ✅ Merged
Merged: 2/5/2025
Merged by: @tjbck

Base: dev ← Head: main

📝 Commits (1)

6ca295e Add user related headers when calling an external embedding api

📊 Changes

6 files changed (+70 additions, -32 deletions)

View changed files

📝 backend/open_webui/retrieval/utils.py (+40 -14)
📝 backend/open_webui/routers/files.py (+4 -2)
📝 backend/open_webui/routers/knowledge.py (+6 -2)
📝 backend/open_webui/routers/memories.py (+4 -4)
📝 backend/open_webui/routers/retrieval.py (+15 -9)
📝 backend/open_webui/utils/middleware.py (+1 -1)

📄 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:

[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 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 for validating 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?
[X ] Prefix: To cleary 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

Add X-OpenWebui headers when calling external embeddings API if ENABLE_FORWARD_USER_INFO_HEADERS=True

Added

Add X-OpenWebui headers when calling external embeddings API if ENABLE_FORWARD_USER_INFO_HEADERS=True

related to "Forward user information when using openai for embedding" discussion

_{🔄 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/9068 **Author:** [@df-cgdm](https://github.com/df-cgdm) **Created:** 1/29/2025 **Status:** ✅ Merged **Merged:** 2/5/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `main` --- ### 📝 Commits (1) - [`6ca295e`](https://github.com/open-webui/open-webui/commit/6ca295ec59452e292f32a077c895e248709b4ca0) Add user related headers when calling an external embedding api ### 📊 Changes **6 files changed** (+70 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/retrieval/utils.py` (+40 -14) 📝 `backend/open_webui/routers/files.py` (+4 -2) 📝 `backend/open_webui/routers/knowledge.py` (+6 -2) 📝 `backend/open_webui/routers/memories.py` (+4 -4) 📝 `backend/open_webui/routers/retrieval.py` (+15 -9) 📝 `backend/open_webui/utils/middleware.py` (+1 -1) </details> ### 📄 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? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests for validating 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? - [X ] **Prefix:** To cleary 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 - Add X-OpenWebui headers when calling external embeddings API if ENABLE_FORWARD_USER_INFO_HEADERS=True ### Added - Add X-OpenWebui headers when calling external embeddings API if ENABLE_FORWARD_USER_INFO_HEADERS=True --- [related to "Forward user information when using openai for embedding" discussion](https://github.com/open-webui/open-webui/discussions/9005) --- <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 04:04:04 -05:00

GiteaMirror closed this issue

2026-04-20 04:04:04 -05:00

GiteaMirror referenced this issue

2026-04-25 09:27:30 -05:00

[GH-ISSUE #22312] feat: Tool for list collection #35223

GiteaMirror referenced this issue

2026-05-05 23:01:53 -05:00

[GH-ISSUE #22312] feat: Tool for list collection #58360

GiteaMirror referenced this issue

2026-05-13 07:00:44 -05:00

[GH-ISSUE #22312] feat: Tool for list collection #74298