@antirez how do you feel about merging this in v4 (and perhaps even in 3.2)?

i am very disappointed that this has been sitting here for months because presently i have no way of executing commands on my server using the cli because it's configured with a username.

@selfagency While adding this seems worthwile, your complaint makes no sense given that Redis does not handle usernames at any point. All you would gain is to use an uri instead of -h host -a password

@badboy to access a redis db with a username you pass the username in the uri: $user@$server:6379/$database.

But Redis itself has no concept of users.

@badboy i don't understand how that's the case, because i use elasticache, which is AWS's redis server, and it has a username

@selfagency Then that is completely non-supported and even this PR here won't solve it (as it simpyl drops the username part from the URI)

On heroku, you'll get a REDIS_URL like [email protected]:1234.

You can connect currently with redis-cli -h ec2-23-3445.compute.aws.com -p 1234 -a 48548458. The username part is the password.

Heroku is a significant enough provider at this point, and this is a convenient enough use case that adds little overhead into the executable, this seems very worthy of inclusion. 👍 The fact that user is dropped if provided is fine.

Thanks @itamarhaber ! Merged, sorry for the delay. I modified the commit message in order to reflect the subject of this PR. Your commit had an odd message, like if it was corrupted because of the '<>' chars or alike.