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

Brian Stansberry (JIRA) issues at jboss.org
Thu Nov 9 09:37:00 EST 2017


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

Brian Stansberry commented on WFCORE-2673:
------------------------------------------

My rule of thumb is if something involves new user controllable behavior, it's a Feature Request. The user controllable part means all the use case analysis and documentation steps we do for features should come into play, even if they are trivial.  An Enhancement is where we take something existing and make it better without involving any user control. Those might benefit from the heavier process, but usually it's unnecessary overkill.

Just a rule of thumb but IMHO a pretty good one.

> 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: Feature Request
>          Components: Domain Management
>            Reporter: Ondrej Lukas
>
> 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.5.0#75005)


More information about the jboss-jira mailing list