[
https://issues.apache.org/jira/browse/PROTON-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640268#comment-17640268
]
ASF subversion and git services commented on PROTON-2656:
---------------------------------------------------------
Commit 010aced388f3cbc73a03065d4c3e8e668263fd3c in qpid-proton-dotnet's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=010aced ]
PROTON-2656 Try to parse address strings as IP address values first
Instead of going into DNS lookup APIs for all string address values we can
first attempt a parse to see if we have a raw IP Address and simply use
the value given as what was intended.
> [proton-dotnet] Loopback IP Address lookup can fail on some systems
> -------------------------------------------------------------------
>
> Key: PROTON-2656
> URL: https://issues.apache.org/jira/browse/PROTON-2656
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-dotnet
> Affects Versions: proton-dotnet-1.0.0-M6
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Major
> Fix For: proton-dotnet-1.0.0-M7
>
>
> When resolving an IP Address from the string form the client uses a DNS entry
> lookup but for some addresses like local host (127.0.0.1) the DNS entry
> returned can contain the machine address first which matches the basic
> criteria and is hard to validate isn't what was intended based on the limited
> API. We can first attempt a straight parse for raw IP Address vs a host name
> value and use the raw parsed value as truth instead of going to the DNS
> lookup API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
