rkrauss
14 years agoNew Contributor
REST requests missing resource path after switching endpoint
Hi,
I'm using SoapUI 4.0.1 to test a REST service in the development and the production environment.
In the development environment, the service is running in the root webapp of a tomcat (server1), whereas in the production environment, the service is mapped to a base path /ws/app/REST.
All the testcases run fine as long as I'm using the development service endpoint server1.
Let's say a teststep with the development service endpoint 'http://server1' issues a GET request with the following resulting URL:
http://server1/Resource1?PARAM1=abc&PARAM2=def
After changing the service endpoint from http://server1' to the production endpoint 'https://server2/ws/app/REST', the teststep will issue the following request
https://server2/ws/app/REST?PARAM1=abc&PARAM2=def
Changing the service endpoint to anything with an additional path will cause the resource path (Resource1) to be excluded from the request url.
Please correct me if I'm wrong, but I would expect that the second case would result in the following URL:
https://server2/ws/app/REST/Resource1?PARAM1=abc&PARAM2=def
Regards
Ralf
I'm using SoapUI 4.0.1 to test a REST service in the development and the production environment.
In the development environment, the service is running in the root webapp of a tomcat (server1), whereas in the production environment, the service is mapped to a base path /ws/app/REST.
All the testcases run fine as long as I'm using the development service endpoint server1.
Let's say a teststep with the development service endpoint 'http://server1' issues a GET request with the following resulting URL:
http://server1/Resource1?PARAM1=abc&PARAM2=def
After changing the service endpoint from http://server1' to the production endpoint 'https://server2/ws/app/REST', the teststep will issue the following request
https://server2/ws/app/REST?PARAM1=abc&PARAM2=def
Changing the service endpoint to anything with an additional path will cause the resource path (Resource1) to be excluded from the request url.
Please correct me if I'm wrong, but I would expect that the second case would result in the following URL:
https://server2/ws/app/REST/Resource1?PARAM1=abc&PARAM2=def
Regards
Ralf