5ebdc79955
* Instead of creating an OpenSSL context ofor each socket, use a global one and initialize it lazily when the first SecureSocket is created * Load the certificates from our certificate list so SSL certificates sent by servers can be validated. * Add a callback for signalling that certificate validation failed, the default implementation proceeds with the connection anyway (to keep the old behavior). * Introduce BCertificate class, that provides some information about a certificate. Currently it's only used by the callback mentionned above, but it will be possible to get the leaf certificate for the connection after it's established. Review of the API and implementation is welcome, before I start making use of this in HttpRequest and WebKit to allow the user to accept new certificates. |
||
---|---|---|
.. | ||
AbstractSocket.h | ||
Certificate.h | ||
DatagramSocket.h | ||
DataRequest.h | ||
FileRequest.h | ||
HttpAuthentication.h | ||
HttpForm.h | ||
HttpHeaders.h | ||
HttpRequest.h | ||
HttpResult.h | ||
net_settings.h | ||
NetAddress.h | ||
NetBuffer.h | ||
NetDebug.h | ||
NetEndpoint.h | ||
NetworkAddress.h | ||
NetworkAddressResolver.h | ||
NetworkCookie.h | ||
NetworkCookieJar.h | ||
NetworkDevice.h | ||
NetworkInterface.h | ||
NetworkNotifications.h | ||
NetworkRoster.h | ||
SecureSocket.h | ||
Socket.h | ||
Url.h | ||
UrlContext.h | ||
UrlProtocolAsynchronousListener.h | ||
UrlProtocolDispatchingListener.h | ||
UrlProtocolListener.h | ||
UrlProtocolRoster.h | ||
UrlRequest.h | ||
UrlResult.h | ||
UrlSynchronousRequest.h |