You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we use a VerifyCallback, however there's a lot of in built verification in SslContext (eg you can just provide it with a root CA file and it does the rest). Making HttpConnector take a fn(&mut SslContext) would be more useful (one can still attach verify callbacks directly, so no functionality is lost)
I have a pre-unboxed closure patch here, if its design feels okay I can move it to unboxed closures.
The text was updated successfully, but these errors were encountered:
On Mon, Jan 12, 2015, 10:37 AM Manish Goregaokar [email protected]
wrote:
Currently we use a VerifyCallback, however there's a lot of in built
verification in SslContext (eg you can just provide it with a root CA
file and it does the rest). Making HttpConnector take a fn(&mut
SslContext) would be more useful (one can still attach verify callbacks
directly, so no functionality is lost)
I have a pre-unboxed closure patch here Manishearth@a815cdd,
if its design feels okay I can
—
Reply to this email directly or view it on GitHub #244.
Currently we use a
VerifyCallback
, however there's a lot of in built verification inSslContext
(eg you can just provide it with a root CA file and it does the rest). MakingHttpConnector
take afn(&mut SslContext)
would be more useful (one can still attach verify callbacks directly, so no functionality is lost)I have a pre-unboxed closure patch here, if its design feels okay I can move it to unboxed closures.
The text was updated successfully, but these errors were encountered: