// register request creator to handle HTTP and HTTPS 
// requests (replaces .NET's default HttpWebRequest)
var creator = new HttpRequestCreator();

// TLS 1.2, 1.1 and 1.0 are now enabled on all platforms

// use WebRequest as usual now - it will use Rebex
// HttpRequestCreator to handle HTTP and HTTPS requests
WebRequest request = 
Show me more code...
Rebex HTTPS is an HTTP and HTTPS library for .NET. It brings TLS 1.2, 1.1, SHA-2, SNI, AES/GCM and other modern security-related features to legacy platforms. It is designed as a drop-in replacement for HttpWebRequest/WebRequest, WebClient and can be used as an alternative SOAP web services transport layer.

Why Rebex HTTPS?

TLS 1.2 and SHA-2 certificates - even on Windows XP and Windows CE

Trying to download a file from the web or access a secure web service from your .NET Compact Framework application? Watch out for WebException. .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 3.5/3.9 (Windows Mobile 5/6, Windows CE, Pocket PC, Windows Embedded Compact) and .NET 2.0/3.0/3.5 (even on Windows XP SP3 and Windows Vista).

Rebex HTTPS supports the following TLS/SSL features:

  • TLS 1.2, 1.1, 1.0
  • Elliptic Curve DSA and Elliptic Curve Diffie-Hellman ciphers
    (requires plugin on some platforms)
  • AES/GCM ciphers
  • SHA-2 certificates
  • SHA-2 hashing algorithms
  • Server Name Indication (SNI) extension
  • Renegotiation Indication extension
  • Support for legacy SSL 3.0 protocol
And more...

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
And more...

.NET Compact Framework app
connected to a SOAP web service over HTTPS.
TLS 1.2 and SHA-2 support enabled.


  • .NET Framework
    2.0, 3.0, 3.5. 4.0, 4.5.x, 4.6.x, 4.7 (32-bit and 64-bit) on Windows XP or later; Visual Studio 2008, 2010, 2012, 2013, 2015, 2017
  • .NET Core
    1.1, 2.0 (32-bit or 64-bit) on All .NET Core platforms; Visual Studio 2017
  • .NET Compact Framework
    3.5, 3.9 on Windows Mobile, Windows CE, Pocket PC, Windows Embedded Compact 7, Windows Embedded Compact 2013; Visual Studio 2008, 2012, 2013
  • Mono
    3.x, 4.x, 5.x on Linux and Apple macOS (OS X)
  • Xamarin.iOS
    Xamarin.iOS 8.6 or later; Xamarin Studio
  • Xamarin.Android
    Xamarin.Android 4 or later; Xamarin Studio

Supports Visual Studio 2008, 2010, 2012, 2013, 2015 and 2017.

Learn more about supported standards and platforms.

Support for .NET Standard 1.5/1.6/2.0 on .NET Core (experimental on .NET Framework 4.6.x.)

Experimental support for .NET Core on Linux and macOS.

Experimental support for Universal Windows Platform (Windows 10, Windows 10 Mobile, Windows 10 IoT).

Experimental support for Xamarin.Mac platform (assemblies are suitable for Xamarin.Mac Mobile and Xamarin.Mac .NET 4.5 Framework projects).