service discovery problem when using custom hostname
Summary: When an account has a custom hostname, the service discovery window defaults to the custom hostname, not the host element of the JID.
Steps to reproduce:
- Add an account with a valid JID (in my case nivex@jabber.nivex.net)
- Set the Use custom host/port in the Connection tab to something else (in my case atlantis.nivex.lan)
- Connect with this account
- Go to Actions, select Service Discovery with this account
Actual result: The address populated in the Service Discovery address window is the custom server, and an error is received:
The service could not be found
There is no service at the address you entered, or it is not responding. Check the address and try again.
Expected result: The address populated in the Service Discovery address window should be the host portion of the JID, and browsing should commence normaly.