Rebex HTTPS does not actually aim to replicate the behavior of .NET HttpWebRequest 1:1, and our developers are not even supposed to look into related .NET source code - we don't want any copyright infringement! Instead, Rebex HTTPS aims to provide a drop-in replacement that supports TLS 1.2 and 1.3 on legacy platforms, and which is stable, usable and behaves in a predictable way. So far, this approach has worked very well for most of our clients, and I hope you and the rest will be satisfied with the next release, which will make the connection establishment process much more customizable. I just sent you the link to the enhanced version.