-
Notifications
You must be signed in to change notification settings - Fork 3.9k
IPv6 compatibility fix #1342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 compatibility fix #1342
Conversation
|
@smagellan can you please add a test for this? |
|
@smagellan can you also take into consideration the changes in this PR #1099 ? |
|
@marcosnils Ok, I will introduce test. |
@smagellan Just wanted to make sure that changes proposed in #1099 still apply with this PR as well.Maybe @allanwax can make a quick review and leave his comments here. @smadasu an example is this change: https://github.com/xetorthio/jedis/pull/1099/files#diff-e8943893bffd99c67d703eabf84d0647R8. Seems like we should include this logic also, right? |
|
@smagellan can u please check #1344 ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parsing IPv6 addresses will always find a port, no matter whether the port is specified or not.
|
LGTM. Swall we merge this right away independently of redis current IPv6 issue? |
|
It's been a while since I looked at this and the stuff I checked into However, from what I code fragments I've seen in the posts, extracting public class HostAndPort { This fragment will make sure that the value of local host is whatever private String convertHost(String host) { This fragment does additional checks for IPV4/V6. '::1' is not the only The code I checked into git has additional functionality. If someone can send me the code in question, I can look further or the Allan Wax On 7/11/2016 3:53 AM, Marcos Nils wrote:
|
|
@smagellan can you please squash and add a nice commit text? Also why do you think redis IPv6 support has an issue? As far as I understand it seems like it always appends a color and the port to the host. So the parsing in this PR seems to be totally fine. Am I missing something? |
|
@xetorthio Done. |
|
Are you you pushed it after squashing? I can still see all the commits. |
|
@xetorthio Can you please check again? |
|
I can still see 4 commits instead of 1 |
Introduced tests for HostAndPort Introduced comments on IPv6 parsing logic Introduced 'aliases' of localhost address
|
@xetorthio I squashed it again |
|
Now it is perfect! Thanks! I think this is ready to be merged! |
|
LGTM!. |
Introduced tests for HostAndPort Introduced comments on IPv6 parsing logic Introduced 'aliases' of localhost address Conflicts: src/main/java/redis/clients/jedis/HostAndPort.java
|
Merged to master and 2.9 respectively. Thx!. |
|
@marcosnils @smagellan this is breaking functionality for me. This breaks connections to the Redis Sentinel (v3.2.2) on my localhost, since only loopback connections are allowed. I'm on OS X 10.11.6 FWIW (I think Would it be possible to fix this forward to resolve loopback? Or was there some need to resolve the external ip? Reverting to Jedis @ 2.8.2 resolves the issue I'm having. |
|
@tonyghita, can you please open separate issue for this problem? |
|
Will do! |
|
@smagellan I've created an issue for this at #1367 |
based upon #982