SOAP and Proxy Servers (cont.)

The URL is not to the target resource, but rather to a SOAP server. This makes it harder, and less likely, for a proxy server to determine which resource is actually being targeted.

The proxy server would need to look inside the SOAP message to determine which resource is being requested.
- Further, the proxy server would need to understand the semantics of the message:

<?xml version="1.0"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

</getResource>

</soap:Body>

</soap:Envelope>

Does this mean that the client

is trying to access Resource 1?

The proxy server must understand

the semantics of every SOAP

application!

The URL is not to the target resource, but rather to a SOAP server. This makes it harder, and less likely, for a proxy server to determine which resource is actually being targeted.