This content has been marked as final. Show 4 replies
We had the same problem. Our work around involved saving the WSDL locally and then using that to run the web service. As long as the WSDL contains a service port element, it will still send the data to the correct server.
In order to ensure that the WSDL stayed up to date, we have a scheduled task that hits the server and downloads the WSDL on a regular basis. Of course, CFHTTP has problems with SSL as well, so you need to include 2 custom headers when you post. You should be able to find them by doing a search on cfhttp and SSL.
Thanks for response:
can you explain me a little bit more how to do your solution.
where do you store the WSDL File, with wath extension ?
wath you mean with service port element?
Thanks for Help
**Sorry for such stupid questions, i am new to that topic.**
No problem. Simply save the WSDL file as a .wsdl on the server that will be performing the web service call. If you actually look at the contents of the WSDL, you'll notice at the bottom of the document an element that specifies the location of the actual web service. As long as this points to the web service on xyz.com's servers, it doesn't actually matter where the WSDL file resides.
Our SSL Proxy is just a forwarding service.
the webservice runs on servername.int.com, there is no way to store the WSDL File on the xyz.com server, because there is only a cgi script file that forwards the url request.