Confusion about soap endpoints
Hi,
I use a web application that essentially serves a class per endpoint. For example: https://blah/WS/authentication has a login operation. https://blah/WS/folder has a retrieve folder metadata operation.
When I read about monitoring soap traffic with soapui or tcpmon it wants me to start by entering "the endpoint". Am I supposed to create a separate monitor for each endpoint, or do I have the wrong interpretation of "endpoint". I tried setting up an http tunnel using the host as the endpoint to which I would add the path /WS/authentication etc. I also tried using https://blah/WS/ and it then says it can't connect.
In addition to my application, I want to monitor a closed source program that uses the same web service. But it expects both a web service and the login form, i.e. https://blah/WS and https://blah/login (displays a login form). So, would that typically work through the tunnel also? In other words listen on localhost and forward traffic to both paths when the path is appended: https://127.0.0.1:8888/WS and https://127.0.0.1:888/login?
So far, every variation I have thought of so far, does not work (the connection is closed or the application reports an invalid response).
Ideas?
I use a web application that essentially serves a class per endpoint. For example: https://blah/WS/authentication has a login operation. https://blah/WS/folder has a retrieve folder metadata operation.
When I read about monitoring soap traffic with soapui or tcpmon it wants me to start by entering "the endpoint". Am I supposed to create a separate monitor for each endpoint, or do I have the wrong interpretation of "endpoint". I tried setting up an http tunnel using the host as the endpoint to which I would add the path /WS/authentication etc. I also tried using https://blah/WS/ and it then says it can't connect.
In addition to my application, I want to monitor a closed source program that uses the same web service. But it expects both a web service and the login form, i.e. https://blah/WS and https://blah/login (displays a login form). So, would that typically work through the tunnel also? In other words listen on localhost and forward traffic to both paths when the path is appended: https://127.0.0.1:8888/WS and https://127.0.0.1:888/login?
So far, every variation I have thought of so far, does not work (the connection is closed or the application reports an invalid response).
Ideas?