We have several applications running on a on-premise installation. Our servers are all running on Microsoft Windows Server and use IIS to serve the mendix applications to the outside world. All the applications are deployed\installed according to the available deployment guide, https://docs.mendix.com/howto6/deploy-mendix-on-microsoft-windows.
All the applications are served over a https connection for obvious security reasons. This secure connection is handled by IIS. The connection between IIS and the mendix application is based on plain HTTP, because that is all internall traffic.
The application are all running fine and working normally. There is only one thing that's causing confusion and discussion with partners that connect to our applications via webservices. That thing is that the generated WSDL's, are pointing to an HTTP (so plain connection, that is even not active) soap address, instead of the desired https connection. See the screenshot below for an example. You can see that the endpoint is set to HTTP instead of HTTPS. For the record, I created this screenshot from a HTTPS page, https://xxxxx.nl/ws-doc/ExcelImporterTemplateXSD?wsdl.
I can imagine that this behaviour is a bit logical, because although the connection between the client and IIS is secure, the connection between IIS en the mendix application isn't. So maybe that is why the WSDL generator returns an plain HTTP address. However, maybe somebody knows a java parameter or something, to force the WSDL generator to always use HTTPS, nevertheless what the requesting url is. Or maybe I am all wrong and I did something else incorrect that causes his behaviour.