InvalidDefinitionException for HTTPS Endpoint
Hello, I'm to point of great frustration trying to add a new SOAP project to Ready! API (v1.5). I seem to have no issues adding HTTP endpoints but it throws errors when I tried to add two differ...
Forum Discussion
Ok, interesting. Looks like it is happening url redirection here and soapUI not able to get definition - Just wild guess, though.
That doesn't explain why Visual Studio would be able to download the WSDL. Also, just tried another tool called WCF Test Client and it too is able to successfully download the WSDL and call the webservice.
The networking aspect of it should be working the same across the board.