HttpClient: How to disable hostcert verification when using SocketsHttpHandler ?

[kjpgit]

✅ SocketsHttpHandler has PooledConnectionLifetime property so DNS isn't cached forever
✅ HttpClientHandler has ServerCertificateCustomValidationCallback so our self signed certs for dev work
🛑 I have no idea how to make a HttpClient() that uses both of the above settings

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

✅ SocketsHttpHandler has PooledConnectionLifetime property so DNS isn't cached forever
✅ HttpClientHandler has ServerCertificateCustomValidationCallback so our self signed certs for dev work
🛑 I have no idea how to make a HttpClient() that uses both of the above settings

Author:	kjpgit
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[MihaZupan]

If you have a SocketsHttpHandler, you can set the handler.SslOptions.RemoteCertificateValidationCallback instead, which serves the same purpose as the property on HttpClientHandler.

[kjpgit]

@MihaZupan I looked at the doc previously:
https://learn.microsoft.com/en-us/dotnet/api/system.net.http.socketshttphandler.ssloptions?view=net-8.0

but it says:
Property Value
SslClientAuthenticationOptions
The set of options used for client TLS authentication.

So I didn't bother looking further at that class, because it implies it's for client certs, not server verification.

Never thought about looking at a class called SslClientAuthenticationOptions for this, but it does appear to be there. Thanks.

[kjpgit]

Suggest the doc be changed from:
"Gets or sets the set of options used for client TLS authentication."
to:
"Gets or sets the set of options used for TLS."

Saying client is a red herring, and ambiguous, because client can mean 'the c# code' or 'the local side of TLS'.