[6.x] RedisBroadcaster - Ignore Redis Prefix When Verifying Channel Access #30597
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.
Since 5.8 Laravel ships with Redis configured with a prefix to prevent conflicts when apps share a Redis store. This prefix is also used in the RedisBroadcaster to broadcast events and verify channels.
While using Laravel Echo Server some developers want to match the prefixing in their configurations with that in their Laravel app. This can work by add the keyPrefix to the server config, however, when authorizing private channels the prefix conflicts with the private channel definition in Laravel. For example:
With prefixing the channel is read as
laravel_database_private-App.User.1
inRedisBroadcaster::auth
instead ofprivate-App.User.1
.