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
* class and setting the http://msdn.microsoft.com/en-us/library/system.net.servicepointmanager.servercertificatevalidationcallback.aspx[ServerCertificateValidationCallback]
254
-
* property.
252
+
* SSL can be configured via the `ServerCertificateValidationCallback` property on either `ServerPointManager` or `HttpClientHandler`
253
+
* depending on which version of the .NET framework is in use.
254
+
*
255
+
* On the full .NET Framework, this must be done outside of the client using .NET's built-in
* The bare minimum to make .NET accept self-signed SSL certs that are not in the Windows CA store would be to have the callback simply return `true`.
265
+
*
263
266
* However, this will accept **all** requests from the AppDomain to untrusted SSL sites,
264
267
* therefore **we recommend doing some minimal introspection on the passed in certificate.**
265
-
*
266
-
* IMPORTANT: Using `ServicePointManager` does not work on **Core CLR** as the request does not go through `ServicePointManager`; please file an {github}/issues[issue] if you need support for certificate validation on Core CLR.
267
268
*/
268
269
}
269
270
271
+
/*
272
+
* If running on Core CLR, then a custom connection type must be created by deriving from `HttpConnection` and
273
+
* overriding the `CreateHttpClientHandler` method in order to set the `ServerCertificateCustomValidationCallback` property:
0 commit comments