[jbossws-issues] [JBoss JIRA] (JBWS-4054) AbstractServerConfig#setWebServiceHost uses local hostname, then fails on verification

Alessio Soldano (JIRA) issues at jboss.org
Fri Mar 3 08:37:00 EST 2017


    [ https://issues.jboss.org/browse/JBWS-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13372267#comment-13372267 ] 

Alessio Soldano commented on JBWS-4054:
---------------------------------------

[~rsearls], isn't the test change in your PR simply needed because of https://github.com/jbossws/jbossws-common/blob/master/src/main/java/org/jboss/ws/common/management/AbstractServerConfig.java#L137 ?

> AbstractServerConfig#setWebServiceHost uses local hostname, then fails on verification
> --------------------------------------------------------------------------------------
>
>                 Key: JBWS-4054
>                 URL: https://issues.jboss.org/browse/JBWS-4054
>             Project: JBoss Web Services
>          Issue Type: Bug
>          Components: jbossws-integration
>         Environment: Wildfly 10.1.0
>            Reporter: Daniel Lichtenberger
>            Assignee: R Searls
>
> If "0.0.0.0" is passed to AbstractServerConfig#setWebServiceHost, it uses InetAddress.getLocalHost().getHostName() as the server host. This hostname is then verified using AddressUtils#isValidAddress, which uses the strict requirements for public hostnames.
> However, it's quite possible to use characters like "_" in local hostnames, so something like "my_desktop" as a hostname (or even non-ASCII characters) will cause this to fail.
> For Wildfly, our workaround is to use a specific IP address (like 127.0.0.1) in the "wsdl-host" of standalone.xml.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbossws-issues mailing list