Hi All,
We have an issue where the messages are being blocked by a proxy when SOAP calls are made from javascript but not when a designer WSDL based data connection is used.
I've checked the meesages and there is a different user agent doing the work within Acrobat.
Designer WSDL based queries use
User-Agent: Mozilla/3.0 (compatible; Spider 1.0; Windows)
SOAP.invoke methods uses
User-Agent: Mozilla/3.0 (compatible; Acrobat Annots 10.1.1 )
Could this be causing the proxy issue?
Kind Regards
Kev
North America
Europe, Middle East and Africa
Asia Pacific