[13.x] Ability to set session prefix for Redis#60700
Merged
taylorotwell merged 4 commits intoJul 11, 2026
Merged
Conversation
|
Thanks for submitting a PR! Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface. Pull requests that are abandoned in draft may be closed due to inactivity. |
Member
|
Hmm, if we set the prefix here would it override or stomp on the cache prefix. Is that object shared between the two? |
Contributor
Author
|
@taylorotwell I think its OK cause its cloned So, they are both seperate at least that's how I read it :D (I did test it locally and it worked) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On Redis providers like Upstash / clusters / ElastiCache and general managed redis services, you're limited to a single keystore (db0), so you can't isolate sessions from cache by using a separate store.
Sessions currently inherit the cache prefix by default with setups like:
This makes it extremely difficult to scan and figure out what's what, between cache and sessions. Meaning when you need to clear cache manually or clear space its complex.
This PR allows you to set a prefix, and is completely opt in, which mirrors the
session.connectionoption.it could be defaulted, but i'm not sure or in charge of those executive decisions. But, maybe this should be the default in 14.x to prevent confusion?
I can move this to 14.x if you'd prefer too
Alternatively, we can do something like the below, but it was a lot less discoverable and confusing, which is why I thought of this PR.
This PR will also assist #60705