Why Rebex HTTPS?

TLS 1.2 and SHA-2 certificates on legacy platforms - Trying to download a file from the web or access a secure web service from your .NET Compact Framework application? .NET CF's HttpWebRequest doesn't support TLS 1.2, TLS, 1.1 or SHA-2 based certificates. Rebex HTTPS implements modern TLS features on all supported platforms including .NET Compact Framework 2.0/3.x (Windows Mobile 5/6, Windows CE, Pocket PC) and .NET 2.0/3.x (even on Windows XP SP3 or Windows Vista).

Rebex HTTPS supports the following TLS/SSL features:

• TLS 1.2, 1.1, 1.0
• SHA-2 certificates
• SHA-2 hashing algorithms
• Server Name Indication (SNI) extension
• Renegotiation Indication extension
• Support for legacy SSL 3.0 protocol

Drop-in secure WebRequest and WebClient replacement - Replace System.Net.WebRequest's standard HTTPS/HTTP request handler with Rebex implementation that supports modern security standards. Just call Rebex.Net.HttpRequestCreator.Register() and you are (almost) done. Both WebRequest and WebClient are supported. In many cases, there is no need to change your old code (except registering Rebex HTTPS).

Drop-in secure WebServices transport replacement - Easily replace the transport layer of SOAP web services with new, secure HTTPS implementation. No need to change your old code (except registering Rebex HTTPS).

Additional features

• Stand-alone HTTP/HTTPS client - WebClient object makes it simple to perform basic operations
• ZLIB compression
• HTTP CONNECT and SOCKS4/SOCKS5 proxy support
• Advanced communication logging