Using SOAP with default proxy

[FrancisGagne1]

I'm trying to POST a SOAP request on a service not under my control.

Since it's cross domain, I need to use a proxy.

I am only using Postman for now.

When I call the service directly, the response is good. But when I add https://myserver:3344/proxy.js? before my service url in postman. The service return me "Server was unable to process request. ---> Root element is missing." meaning that my xml I sent is not good anymore.

Can I have some help with SOAP request using the default proxy coming with WebApp Builder?

Is it supported?

Thanks.

[CCWeedcontrol]

Robert i have some questions if you don't mind.

What data are you retrieving from the CAMA system, what are you doing with it?

How exactly are you doing it?

[RobertScheitlin__GISP]

What data: All required parcel and improvement info for the selected parcel

What I do with it: Generate JS/HTML custom reports

How Exactly: Using esriRequest to my custom .Net web service that returns the CAMA data based a parcel number query.

[FrancisGagne1 · Accepted solution]

Instead of using the proxy in WAB to handle the cross domain problem, I passed in a service that handle CORS and all is fine now: https://cors-anywhere.herokuapp.com/ 

I'll setup a cors-anywhere on my client's server but at least I know that works with this one.