curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vile2539 <...@git.apache.org>
Subject [GitHub] curator pull request #205: [CURATOR-392] Fixing connection string constructi...
Date Mon, 13 Mar 2017 20:56:19 GMT
GitHub user Vile2539 opened a pull request:

    https://github.com/apache/curator/pull/205

    [CURATOR-392] Fixing connection string construction for wildcard client addresses

    The client address in Zookeeper can be a wildcard (0.0.0.0), and if this is used by Curator,
it will attempt to create a new connection to 0.0.0.0 instead of the correct server address.
It is also possible that no client address or port is set, which should be counted as invalid
by Curator, since the appropriate information isn't contained in the data sent.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Vile2539/curator CURATOR-392

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/205.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #205
    
----
commit 9b73d11bc03c6e37567e237e96c36cdf93e4ff66
Author: Kenco <davelister@gmail.com>
Date:   2017-03-13T20:51:42Z

    Fixing connection string construction to ignore wildcard client addresses

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message