Thanks for taking the time to report this bug and try to make Ubuntu better!
I was able to reproduce what you mentioned even in Groovy. Checking the code, the warning about specifying the port number with --server seems something desired by upstream since it is not IPv6 friendly [1]. I did not go through details of implementation but it might be an upstream bug, when the ':<port>' is passed the host is correctly parsed otherwise not and it fallback to localhost.
Interestingly, if you check the manpages those options are not listed there, and it is not a bug in the Ubuntu package but the upstream doc seems outdated [2].
This sounds like an upstream bug to me. The best route to getting it fixed
in Ubuntu in this case would be to file an bug with the upstream project. Would you like to do that?
If you do end up filing an upstream bug, please link to it from here. Thanks!
Thanks for taking the time to report this bug and try to make Ubuntu better!
I was able to reproduce what you mentioned even in Groovy. Checking the code, the warning about specifying the port number with --server seems something desired by upstream since it is not IPv6 friendly [1]. I did not go through details of implementation but it might be an upstream bug, when the ':<port>' is passed the host is correctly parsed otherwise not and it fallback to localhost.
Interestingly, if you check the manpages those options are not listed there, and it is not a bug in the Ubuntu package but the upstream doc seems outdated [2].
This sounds like an upstream bug to me. The best route to getting it fixed
in Ubuntu in this case would be to file an bug with the upstream project. Would you like to do that?
If you do end up filing an upstream bug, please link to it from here. Thanks!
[1] https:/ /github. com/alanxz/ rabbitmq- c/blob/ master/ tools/common. c#L223 /github. com/alanxz/ rabbitmq- c/tree/ master/ tools/doc
[2] https:/