Simple pass through proxy for SOAP web-service

[#1]

I have several SOAP web-services all running at a particular domain which is SSL protected. I can see the WSDL file (https://<apigeeurl>/<path>/myfile.asmx?wsdl&apikey=<my-user-key>) but when I try and make a SOAP request to https:////myfile.asmx?apikey=,>/<path>/myfile.asmx?apikey=<my-user-key>, the request hits my server but requests the wrong method (myfile.asmx has multiple methods, the first one is "hit" despite the correct method being specified within the SOAP request) and thus an invalid response is returned.

Adding some debug information to my web service, I can see that none of my parameters within the SOAP request are actually making it to the web service which leads me to the conclusion that the request body is being removed by the Apigee service. The annoying thing is that the web-service hasn't changed since we used to use Apigee at the end of 2013 but we no longer have the original API/products/etc set-up in Apigee.

Can anyone provide instructions on how to correctly set up an API in Apigee for complete pass-through so that all Apigee does is check for a valid apikey and in the case of a WSDL file, replace some endpoint URLs?

[jonesfloyd · Accepted solution]

Hi Martin -

If you haven't seen this, check out the following topic that describes how to create a SOAP passthrough proxy:

http://apigee.com/docs/api-services/content/exposing-soap-service-api-proxy#creatingapassthroughprox...

There's actually quite a bit that Edge does to make this happen, and that topic talks about how to create a passthrough proxy from scratch. If you're not wanting to create new passthrough proxies, maybe you can try one out and see exactly what Edge is doing. Might help you troubleshoot your existing proxies.

Hope that helps.

Floyd