-
Notifications
You must be signed in to change notification settings - Fork 829
JAV-551 fix address binding logic, 0.0.0.0 should be replaced with a valid address #353
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,7 +7,7 @@ cse: | |
| registry: | ||
| address: http://127.0.0.1:30100 | ||
| rest: | ||
| address: 0.0.0.0:8080 | ||
| address: 127.0.0.1:8080 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 为什么需要修改这里的地址?不修改会影响用例正常运行吗?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 因为现在监听IP的时候不允许监听0.0.0.0了。我们的测试里面全都是provider配的监听0.0.0.0,consumer连接用的127.0.0.1,现在这样会连不上。 |
||
| handler: | ||
| chain: | ||
| Provider: | ||
|
|
||
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.
Is there any security reason for this change?
We need to tell add the release-note to tell user they cannot use "0.0.0.0" any more.
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.
I misunderstood the requirement. I've communicated with liubao and jimin, and ensure that our current mechanism is right. This pull request will be closed later.