JSON-RPC: Remove IPv6-untested warning from --jsonrpcbindip docs / improve empty address warning #2958
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IPv6 was tested successfully by @ann0see in jamulussoftware#2917 (comment)
pljones
approved these changes
Nov 10, 2022
5 tasks
References: jamulussoftware#2917 (comment) Co-authored-by: Peter L Jones <peter@drealm.info>
ann0see
approved these changes
Nov 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Short description of changes
JSON-RPC: Remove IPv6-untested warning from --jsonrpcbindip docs
IPv6 was tested successfully by @ann0see in JSON-RPC: Add option to specify bind address for server #2917 (comment)
JSON-RPC: Improve empty-bind-address warning for --jsonrpcbindip
References: JSON-RPC: Add option to specify bind address for server #2917 (comment)
CHANGELOG: SKIP
Context: Fixes an issue?
Does this change need documentation? What needs to be documented and how?
Status of this Pull Request
What is missing until this pull request can be merged?
Checklist