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
Quite strange, and thank you for your patience.
Do you, by chance, have any different wsdl running on https ? If so, will you please try to see the problem reproducible?
Do you, by chance, have any different wsdl running on https ? If so, will you please try to see the problem reproducible?
I tried another HTTPS endpoint and had the same result.
I should have mentioned it earlier, but I have entries in my host file so that I get routed to a specific server in our environment (by-passing the load-balancer). When I commented our my host file entries and restarted Ready! API, everything seems to work.
When I re-add my host file entries and restart Ready! API, I get the error referenced everytime.
Thanks,
Marshall
If not apparent, when my hosts file entries are enabled, I am able to access the endpoints in a browser and via Visual Studio. I have verified that both are respecting my hosts file by using wireshark to ensure the traffic is going to the expected IP address.
- 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.