Buschfunk
15 years agoFrequent Contributor
[Res] Invalid endpoint for SSL mock services
Hello,
Using soapUI Pro 3.6.1 I encounter the following problem.
Steps for reproducing
Shouldn't it be https://myHost:9000/path in this case? We have the problem that the client is configured to call https://myHost:9000/path and notices the above mismatch as a possible man-in-the-middle attack.
Thanks,
Robert
Using soapUI Pro 3.6.1 I encounter the following problem.
Steps for reproducing
- Generate a mock service out of an WSDL, running on port 8088.
- Call the WSDL via HTTP in a web browser. The address location in the WSDL is something like http://myHost:8088/path
- Enable SSL for the mock service, running on port 9000.
- Call the WSDL via HTTPs in a web browser. The address location in the WSDL is https://myHost:8088/path
Shouldn't it be https://myHost:9000/path in this case? We have the problem that the client is configured to call https://myHost:9000/path and notices the above mismatch as a possible man-in-the-middle attack.
Thanks,
Robert