Hi Colin,
Most probably the SOAP engine's HTTP client inside the plug-in is so simple that it doesn't understand about HTTP redirection status code. In any case I guess you are talking about the SOAP address location URL inside the WSDL file, not the WSDL file URL itself, aren't you?
To solve that issue, you can modify the URL that the plug-in is using to invoke the SOAP service like this:
- Using the "Update a SOAP host" workflow, you can edit the content of the WSDL file and change the URL of the service.
- Using the "Update a SOAP host with an endpoint URL" workflow (from the version 1.0.1 of the plug-in, recommended), you can edit directly the URL of the service without editing the whole WSDL.
But just to try it... when you create a SOAP host with the plug-in, if you import the WSDL file from a URL via HTTP you get an HTTP SOAP address location URL. But if you try to import the WSDL file from the same URL via HTTPS, do you get the same HTTP SOAP address location URL or is it HTTPS one? Maybe if the WSDL is auto-generated you'll get the proper HTTPS URL for the service if you try to import the WSDL from a HTTPS URL.
And keep in mind that if you are using HTTPS you'll need to import the SSL certificate into vCO. You can do it manually from the vCO Web Configurator, or it will be automatically added if you add the SOAP host importing the WSDL file from a HTTPS URL.
I hope it helps.
Regards,
Sergio
