Wildfly 11.0.0alpha: Communication with Mod_cluster not working over https.

[rahurb11]

We have installed wildfly 11.0.0alpha1 and trying to configure https communication between apache http server and wildfly (Modcluster over https). However, the httpd connection is not being established. Communication over AJP is working fine.

We had been successfully able to establish the same in wildfly 10.0.0Final. Could anyone please let me know whether is there any difference between the way it is configured In 10.0.0Finald 11.0.0alpha1?

[ctomc]

how does your undertow subsystem config look like?

[ctomc]

Also, is it any different with latest nightly build https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.lastFinished/wildfly-11.0.0.Beta1-SNAPSHOT.zip

As there ware some fixes in this exact area last week.

[rahurb11]

Thanks Tomaz,

The https is working now,it was not working due to some mis-configuration,

However, now we were facing an issue with proxy redirection.

We have below configuration:

Client --> Apache http server (2.4) --> Wildfly11.0.0alpha1

Apache is forwarding request over https to wildfly using mod_cluster.

Apache is listening over : https://uat1.myapp.co.uk

Wildfly is configured to listen over : https://wildflyhost:11443/mpla/    (mpla is an application context)

When user is browsing the application using the url: https://uat1.myapp.co.uk/mpla, in the browser the url is getting redirected to : https://wildflyhost:11443/mpla

In jboss 6.4: there were attributes: ProxyHost and ProxyPort, where we used to provide the url and port being used by client (Browser). however these options are not present in wildfly.

could you please help on this?