[jboss-jira] [JBoss JIRA] (WFCORE-2673) HTTP redirect if both http and https socket-binding is configured for http-interface

Ondrej Lukas (JIRA) issues at jboss.org
Thu Apr 13 08:05:00 EDT 2017


Ondrej Lukas created WFCORE-2673:
------------------------------------

             Summary: HTTP redirect if both http and https socket-binding is configured for http-interface
                 Key: WFCORE-2673
                 URL: https://issues.jboss.org/browse/WFCORE-2673
             Project: WildFly Core
          Issue Type: Bug
          Components: Domain Management
            Reporter: Ondrej Lukas
            Assignee: Brian Stansberry


In case when both http and https socket-binding is configured for management http-interface and http port is accessed then server tries to redirect automatically to https port. Access http is not possible.

It causes that it is impossible to connect to http-interface with clients which do not supports https (even if http port is provided by application server), i.e. following ModelControllerClient is not able to connect to http-interface when both http and https socket-binding is configured:
{code}
ModelControllerClient client = ModelControllerClient.Factory
        .create(new ModelControllerClientConfiguration.Builder()
                .setProtocol("remote+http")
                .setPort(9990)
                .setHostName("localhost")
                .setConnectionTimeout(10000).build())
{code}

See:
{code}
curl -v -H 'Upgrade: jboss-remoting' http://localhost:9990
* Rebuilt URL to: http://localhost:9990/
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 9990 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: localhost:9990
> Accept: */*
> Upgrade: jboss-remoting
> 
< HTTP/1.1 302 Found
< Connection: keep-alive
< Location: https://localhost:9993/
< Content-Length: 0
< Date: Thu, 13 Apr 2017 11:59:56 GMT
< 
* Connection #0 to host localhost left intact
{code}



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


More information about the jboss-jira mailing list