You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the 0.3.x version of Milo, it fails to parse IPv6 addresses.
The problem is in the endpoint pattern which is expected. An IPv6 address may look like [fe80::9289:e377:bacb:f608%enp0s31f6], and thus may contain :, % and [].
The result is a complain about an unsupported protocol:
Exception in thread "main" java.util.concurrent.ExecutionException: UaException: status=Bad_InternalError, message=unsupported protocol: null
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
at de.dentrassi.ece2017.milo.step02.Browse.main(Browse.java:31)
Caused by: UaException: status=Bad_InternalError, message=unsupported protocol: null
at org.eclipse.milo.opcua.stack.client.DiscoveryClient.getEndpoints(DiscoveryClient.java:189)
at de.dentrassi.ece2017.milo.step01.Connect.createClient(Connect.java:54)
at de.dentrassi.ece2017.milo.step01.Connect.connect(Connect.java:67)
... 1 more
The text was updated successfully, but these errors were encountered:
This isn't recognizing or validating IPv6 addresses so much as just
allowing the possibility of an IPv6 address in the hostname position by
allowing anything inside a pair of square brackets to be treated as a
hostname.
fixes#509
This isn't recognizing or validating IPv6 addresses so much as just
allowing the possibility of an IPv6 address in the hostname position by
allowing anything inside a pair of square brackets to be treated as a
hostname.
fixes#509
In the 0.3.x version of Milo, it fails to parse IPv6 addresses.
The problem is in the endpoint pattern which is expected. An IPv6 address may look like
[fe80::9289:e377:bacb:f608%enp0s31f6]
, and thus may contain:
,%
and[]
.The result is a complain about an unsupported protocol:
The text was updated successfully, but these errors were encountered: