mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 06:03:26 -05:00
[PR #17223] [MERGED] feat: Added support for redis as session storage #24361
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?
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/17223
Author: @cableman
Created: 9/5/2025
Status: ✅ Merged
Merged: 9/25/2025
Merged by: @tjbck
Base:
dev← Head:feature/session-in-redis📝 Commits (1)
4ca4300feat: Added support for redis as session storage📊 Changes
2 files changed (+42 additions, -7 deletions)
View changed files
📝
backend/open_webui/main.py(+41 -7)📝
backend/requirements.txt(+1 -0)📄 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:
devbranch.Changelog Entry
Description
Added support for using Redis for session storage during oAuth redirects for better state handling, with fallback to current session handling.
Added
Additional Information
In Kubernetes with multi pod setup, we see a lot of these errors:
OAuth callback error: mismatching_state: CSRF Warning! State not equal in request and response.And from what I have been able to figure out. The current session handling is stored browser side and encrypted. This may fail do to browser setting or extension.
This PR adds support for using Redis as storage across pod's, with fallback to the current session handling.
See issue: https://github.com/open-webui/open-webui/issues/15373
Screenshots or Videos
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.