LiveCode Forums.

Hi folks,
Is there a way to intercept the POST function leaving the Revolution Engine, to check its structure? I have a working SOAP message (when tested with SOAP Client) that fails when I try to generate it from within Revolution.

I'm not getting any error response from the target server, so I suspect that I have an issue with headers or message format that means it is being dismissed - but I'm only guessing unless I can compare the Revolution output to the SOAP Client message.

Any ideas gratefully received.
Best,
Keith..

I thought I'd post my progress here, as it may help others. I have now moved libURLSetLogField to directly above the POST statement and this now appears to be trapping the outbound message - and revealing that all is not what it should be. So, now for some proper, informed debugging.

This new insight on outbound HTTP traffic from the libURLSetLogField revealed that the POST function was sending the custom HTTP headers but ignoring my SOAP message as its data load.

Loading the Resource Centre and downloading a video showed in the libURLSetLogField that the GET function works, so I think the SOAP message is too much for the POST function.

Meanwhile, I've now discovered the libSOAP library and will experiment with this.