The error message is misleading ...
You should add a protocol in front of the host, something like HTTP:// or whatever you want to use. There may be other circumstances in which this happens, according to this blog post , but setHostConfiguration deprecated, so this only applies to legacy code.
Client code must catch it earlier, and not so deep in the system, how can incorrect data go that far?
source share