We have an issue accessing SOAP WebServices that are secured with HTTP/Basic authentication. We use WebServices extension 2.2.24.
In our basic setup we have an Appway Server and a middleware server providing a SOAP WebService used by Appway. In the Integration Link, the default URL for the SOAP service is configured to the middleware server. Sometimes for development purpose, we need to change the service URL of the SOAP Client. After doing this, the SOAP request is routed to the correct machine, but the HTTP header does not contain any Authorization information anymore. A workaround to getting back the Authorization information is to define the service URL using the IP address instead of the hostname. In the case of the middleware server, it works with both, the IP address and the host name.
Do you have any fix or explanation for this strange behavior?
In our basic setup we have an Appway Server and a middleware server providing a SOAP WebService used by Appway. In the Integration Link, the default URL for the SOAP service is configured to the middleware server. Sometimes for development purpose, we need to change the service URL of the SOAP Client. After doing this, the SOAP request is routed to the correct machine, but the HTTP header does not contain any Authorization information anymore. A workaround to getting back the Authorization information is to define the service URL using the IP address instead of the hostname. In the case of the middleware server, it works with both, the IP address and the host name.
Do you have any fix or explanation for this strange behavior?