Soap.SOAPHTTPTrans.SOAPInvokeOptions
Delphi
SOAPInvokeOptions = (soNoValueForEmptySOAPAction, { Send "" or absolutely no value for empty SOAPAction }
soIgnoreInvalidCerts, { Handle Invalid Server Cert and ask HTTP runtime to ignore }
soNoSOAPActionHeader, { Don't send SOAPAction - use very very carefully!! }
soAutoCheckAccessPointViaUDDI, { If we get a status code 404/405/410 - contact UDDI }
soPickFirstClientCertificate { If certificate info is not specified - use first }
);
C++
enum DECLSPEC_DENUM SOAPInvokeOptions : unsigned char { soNoValueForEmptySOAPAction, soIgnoreInvalidCerts, soNoSOAPActionHeader, soAutoCheckAccessPointViaUDDI, soPickFirstClientCertificate };
Properties
Type | Visibility | Source | Unit | Parent |
---|---|---|---|---|
enum | public | Soap.SOAPHTTPTrans.pas Soap.SOAPHTTPTrans.hpp |
Soap.SOAPHTTPTrans | Soap.SOAPHTTPTrans |
Description
SOAPInvokeOptions and TSOAPInvokeOptions represent flags that customize how to handle a SOAP message.
TSOAPInvokeOptions is a set of TSoapInvokeOption values. TSoapInvokeOption values are flags that specify how THTTPReqResp manages the sending and receiving of SOAP messages. The following table lists the possible values:
Value | Meaning |
---|---|
soNoValueForEmptySOAPAction |
When calling Web services that specify empty SOAP actions, omit the SOAPAction header rather then generating a SOAPAction header whose value is an empty string. |
soIgnoreInvalidCerts |
When the server uses SSL but has an invalid certificate, treat it as if the certificate had been valid. This is useful when debugging applications that use a secure server. |
soNoSOAPActionHeader |
Always omit the SOAP action header when calling Web services. It is advised that you only use this option with extreme caution. |
soAutoCheckAccessPointViaUDDI |
Provide fail-over support for messages that result in a status code of 404, 405, or 410. This option causes THTTPReqResp to look up the UDDI entry that was used to import the Web Service description and attempt to locate a new binding. |