Consuming a .NET web service - auto discovery?

I’m not a PHP developer, so excuse my ignorance. I’m the author of a .NET Web Service and one of my consumers is using PHP. We recently made some changes to our network and service structure. All other consumers have no issues.

One major change is that we have a custom reverse-proxy application that essentially takes all requests to and forwards it to is, as the name suggests, internal and not visible to the web. When the consumer uses to call the service, they tell me they see a message indicating the service at cannot be found.

Does PHP use the <soap:address location="..." /> from the wsdl to determine the address to call? If so, it’s using the internal address, which is wrong. Can the developer specify the address and override this behavior?

Sponsor our Newsletter | Privacy Policy | Terms of Service