I wrote a small app on MacOS and hit a websocket server using ManagedClientWebSocket and an https server using ManagedHttpClientHandler, both of these types uses SslStream in their implementation. I verified the ssl handshake data sent over the wire using wireshark, and verified that it in fact sends the server_name TLS extension in the ClientHello. Can you provide a small repro app for this bug, along with the ssl handshake header information?
@karelz I've checked the master nightly build, everything is perfectly working!
Is there any chance to release this feature before 2.1? Then many people will be able to use MongoDB with ssl on Linux. :-)
If there is strong demand to have it in 2.0.x (i.e. it is adoption blocker for a few customers), we could consider it. So far I have seen moderate demand (5-ish people asking about it / reporting it - and only this one asking for servicing fix).
Also, the 2.0 servicing fix might be available quite close to 2.1 availability, so the value of porting goes down. If it is blocking you badly, did you consider porting the fix into 2.0.x branch and creating custom build with local fix?