-
1. Re: Undertow redirect port for HTTPS
ctomc Dec 9, 2013 9:02 AM (in response to froed)1 of 1 people found this helpfulHey,
the best way to configure it to create jira issue for this.
I have it on my todo list for a while but never managed to get it done.
It should be easy fix in the subsystem with re-introduction of redirect-port attribute on http connector.
--
tomaz
-
2. Re: Undertow redirect port for HTTPS
froed Dec 9, 2013 9:58 AM (in response to ctomc)1 of 1 people found this helpfulOK, thank you for the response.
Done!
see: [WFLY-98] http -> https redirect port not respecting offset - JBoss Issue Tracker
-
-
4. Re: Undertow redirect port for HTTPS
froed Dec 19, 2013 5:34 AM (in response to ctomc)Thank you Tomaz,
your changes were merged already,
but it looks like it was not merged completely.
see my comment in PR
I used the nightly build and it doesn't work with the last build #831:
-
5. Re: Undertow redirect port for HTTPS
ctomc Dec 19, 2013 6:04 AM (in response to froed)Hey,
there was extra commit to implement [WFLY-1070] Add a redirect-socket configuration to the web connector config - JBoss Issue Tracker which helps in domain deployments or in scenarios when you want to have many servers running on same machine by just defining port-ofset.
in short, instead of having static port defined in redirect-port you now have redirect-socket which is reference to port-binding that you can find on bottom of standalone.xml
by default redirect-socket has value of "https" and as such references <socket-binding name="https" port="${jboss.https.port:8443}"/>
so in short if you want to redirect to 443, all you need to do is change socket binding to 443.
--
tomaz
-
6. Re: Undertow redirect port for HTTPS
froed Dec 19, 2013 6:57 AM (in response to ctomc)got it now :-)
for my scenario using cloud service I defined:
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="https-ext" port="${jboss.https.port:443}"/>
and the http-listener with:
<http-listener name="default" socket-binding="http" redirect-socket="https-ext" />
assuming the cloud provider configuration above, this will lead to:
redirected to https://domain.net/ instead of https://domain.net:8443/ if the user types http://domain.net in his browser
nice solution, thanks for your effort
-
7. Re: Undertow redirect port for HTTPS
dnovo Mar 13, 2015 1:24 PM (in response to froed)Hi,
How to redirect without changing web.xml? It's possible?
<security-constraint>
<web-resource-collection>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>