Once wodHttpDLX connects to SSL/TLS server, it will
receive server's certificate that holds information
about server's validity. It will contain information
such as server's name, organization, valid dates etc..
Certificates are usually signed by some known CA
(Certificate Authority) whose responsibility is to prove
that server is really the one he's representing to
be.
wodHttpDLX will try to detect if remote certificate
should be trusted or not. If any errors are found,
ErrorText will contain line-by-line
descriptions for all errors found, and ErrorCode will
contain first error that was found. If ErrorText is empty (and ErrorCode is 0), certificate should be trusted.
wodHttpDLX will load all certificates in your Windows
Certificate store (ROOT and MY stores) and remote
certificate will be tested against all certificates in
those stores.
Even if no error is found - make sure certificate's
CommonName property point to the
Hostname
you're connecting to! This test should be done by your
application.
If you think remote server's certificate is invalid,
you should set Accept parameter to
False and wodHttpDLX will immediately close the
connection.
In environments where this event is not available, you can set
IgnoreCertErrors to True so no connection is accepted
even if certificate is invalid.
HostCertificate
Event
