Back to product page
- Introduction
- License agreement
- Getting Started
- Objects
- Enumerations
- wodHttpDLX
- Methods
- Properties
- Authentication
- AutoRedirect
- BindIP
- Blocking
- CertErrors
- Certificate
- Compression
- Hostname
- HTTPversion
- IgnoreCertErrors
- KeepAlive
- LastError
- LastErrorText
- LocalCertBag
- Login
- MyHostname
- MyIP
- Notification
- Password
- Port
- ProxyAuthentication
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- Request
- Response
- Secure
- Socket
- SSLCipherList
- State
- Timeout
- URL
- UseIPv6
- Version
- Events
- wodHttpNotify
- HttpCookie
- HttpCookies
- HttpHeader
- HttpHeaders
- HttpRequest
- HttpRequestFormPost
- HttpRequestFormUpload
- HttpResponse
- How to get support?
- Technical information
- Fast notifications interface
- Error list
Certificate property
Holds local certificate to be used for authentication.
Type
An ICertificate object. Reference to instance that holds certificate (and private key).Syntax
- Basic
[Set] object.Certificate [= ICertificate]
The Certificate(object,ICertificate) syntax has these parts:
The Certificate(object,ICertificate) syntax has these parts:
object | An expression evaluating to an object of type wodHttpDLX. |
ICertificate | An ICertificate object. |
Remarks
If you don't plan to deal with certificates or private keys, most probably you will never use this property. But - if you plan to connect to servers that require client certificate for the connection, or you plan to create and use certificates/private keys for connecting for HTTP servers, you will need to specify this property. This property should be set to valid ICertificate object which is part of our 'Certificate Management library' shipped with the installation package of wodHttpDLX. It will allow you to Load, Save, Generate... keys and certificates which can be used directly by the server, or should by signed by 3rd party authority and then used with the server. It can combine both OpenSSL type certificates, as well ones located in your Microsoft Windows crypto stores - and handle them transparently. Setting certificate is really easy. Typically, you could do it like this:Set wodHttp1.Certificate = New Certificate
wodHttp1.Certificate.GenerateKey 0 'RSAkey
wodHttp1.Certificate.SaveKey "C:\mykey.txt"
or later on
Set wodHttp1.Certificate = New Certificate
wodHttp1.Certificate.LoadKey "C:\mykey.txt"
wodHttp1.Certificate.Load "C:\mycertificate.txt"
wodHttpDLX internally will never create this object (it only uses it), so if you don't plan to use ICertificate object, you don't have to distribute wodCertificate.DLL with your application.