Back to feature list...
Standards and platform support
On this page:
- 100% managed .NET code with no external dependencies
- .NET 6.0/5.0
- .NET Framework on Windows
- .NET Core
- .NET Standard
- Mono on Linux
- Universal Windows Platform
- Legacy platform support
- .NET Compact Framework
- Internet RFC specifications
- FIPS 140-2 mode
- Proxy servers
- Cryptographic algorithms
- Private key formats
- Scripting platforms
- Authentication methods
- Other technologies
- Rebex HTTPS is written in 100% managed C# code.
- No external dependencies. It only needs Windows and .NET Framework.
- No open source code used.
- Fully CLS-compliant.
- Supports any .NET language (C#, VB.NET, C++/CLI, etc.)
- Platform-independent code. Same assemblies for both 32-bit and 64-bit applications.
- Windows 11 (x64, x86, ARM64)
- Windows 10 (x64, x86, ARM64)
- Windows Server 2019 (x64, x86)
- Windows Server 2016 (x64, x86)
- Windows Server 2012 R2 (x64, x86)
- Windows 8.1 (x64, x86)
- Windows 7 SP1 (x64, x86) (end-of-life platform)
- Linux (x64, ARM64, ARM32)
- macOS (x64, ARM64)
Please note that support for the following .NET 6.0 platforms is currently in preview mode:
- Android (x64, ARM64, ARM32)
- iOS/tvOS (x64, ARM64, ARM32)
We will fully support Android and iOS/tvOS platforms as soon as the corresponding .NET 6.0 update is published.
Rebex HTTPS supports the following .NET Framework platforms:
- .NET Framework 4.8
- .NET Framework 4.7.x
- .NET Framework 4.6.x
- .NET Framework 4.5.x
- .NET Framework 4.0
- .NET Framework 3.5 SP1
- Both 32-bit and 64-bit versions (same DLLs)
Legacy binaries for .NET Framework 2.0/3.0 are available as well.
For details and a trial version download link, see Support for Legacy Platforms.
Supported IDE versions:
- Microsoft Visual Studio 2022
- Microsoft Visual Studio 2019
- Microsoft Visual Studio 2017
- Microsoft Visual Studio 2015
- Microsoft Visual Studio 2013
- Microsoft Visual Studio 2012
Supported Windows versions:
- Windows 11
- Windows 10
- Windows Server 2019
- Windows Server 2016
- Windows 8.1
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2 (end-of-life platform)
- Windows Server 2008 (end-of-life platform)
- Windows 7 (end-of-life platform)
Rebex HTTPS is also known to work on Windows 8, Windows Vista, Windows XP SP3, Windows Server 2003 R2, Windows Embedded Standard 2009 and Windows Embedded POSReady 2009. However, these platforms already reached end-of-life (most of them many years ago), which means we cannot guarantee support for Rebex HTTPS on these operating systems.
Rebex HTTPS supports .NET Core platform.
- .NET Core 3.1
- .NET Core 2.1 (end-of-life platform)
Supported operating systems:
Rebex HTTPS supports .NET Standard 2.1 on .NET 6.0, .NET Core 3.1, Mono 6.10 (or higher), Xamarin.Android 10.1 (or higher) and Xamarin.iOS 13.10 (or higher). It also supports .NET Standard 2.0 on .NET Core 2.1. Support for .NET Standard 2.0 on Universal Windows Platform (build 16299 or higher) and Xamarin.Mac (version 6.0 or higher) is experimental.
- Visual Studio with Xamarin.iOS 13.10 or later
- iOS 10.2 or later
To target Xamarin.iOS platform, reference .NET Standard 2.1 binaries.
- Visual Studio with Xamarin.Android 10.1 or later
To target Xamarin.Android platform, reference .NET Standard 2.1 binaries.
Rebex HTTPS features experimental support for Xamarin.Mac 6.0 or later via .NET Standard 2.0.
Rebex HTTPS features experimental support for Universal Windows Platform (UWP/UAP) applications on Windows 10 or Windows 11 via .NET Standard 2.0.
- Windows 11
- Windows 10 (version 1709 or higher)
- Windows 10 IoT (version 1709 or higher)
In order to use Rebex HTTPS on these platforms, make sure to specify at least Windows 10 Fall Creators Update (10.0; Build 16299) in your Universal Windows project.
Rebex HTTPS can be used within an ASP.NET web page. However, you have to keep in mind specific features of the ASP.NET platform (it is stateless, multi-threaded, it may be limited by MediumTrust security level...).
Further info on using Rebex components in web environment can be found in How to use Rebex SFTP or FTP/SSL in ASP.NET knowledge base article. The article discusses SFTP and FTP/SSL, but implications for Rebex HTTPS component are the same.
Legacy edition of Rebex HTTPS for the following platforms is available as a separate product:
- .NET Compact Framework 3.5/3.9
- .NET Framework 2.0/3.0
Legacy platforms are platforms that are no longer covered by our Standard Support, but have not yet reached End of Life. For details, see the following KB articles:
Rebex HTTPS supports .NET Compact Framework on Microsoft's legacy embedded, handheld and mobile platforms based on Windows CE.
- .NET Compact Framework 3.9
- .NET Compact Framework 3.5 (end-of-life)
Supported operating systems:
- Windows Embedded Compact 2013
Known to work on the following end-of-life platforms:
- Windows Embedded Compact 7
- Windows Embedded Handheld 6.5
- Windows Embedded CE 6.0
- Windows CE 5.0
- Windows Mobile 5.0, 6.0, 6.1, 6.5
Please note .NET Compact Framework is a legacy platform, which means that Rebex HTTPS for .NET CF is available as a separate product with different lifecycle and pricing.
Due to popular demand, we will continue to provide and maintain binaries for .NET Compact Framework 3.5 until 2023-10-10, as long as your legacy support contract remains active. However, support for these binaries is no longer included in the Rebex Support Contract.
Implemented HTTP RFC:
Implemented TLS RFC:
- RFC 2246 (TLS 1.0)
- RFC 4346 (TLS 1.1)
- RFC 5246 (TLS 1.2)
- RFC 8446 (TLS 1.3)
- RFC 5746 (TLS Renegotiation Indication Extension)
Please note that some non-essential features might not be supported. Let us know if you need to add anything.
Rebex HTTPS can operate in a FIPS 140-2 compliant mode. When enabled, only FIPS-approved
cryptographic modules from MS CryptoAPI are used. FIPS mode is activated automatically when Windows is running in FIPS mode.
To switch on the FIPS mode manually, set
- SOCKS4a (Socks4 with domain name resolving)
- HTTP proxies with CONNECT method support
- Tunneling through SSH servers
Learn how to use proxy servers in Rebex HTTPS.
- DSA (legacy)
- Diffie-Hellman key exchange
- Elliptic curve Diffie-Hellman key exchange (ECDH)
- Tripple DES
- DES (legacy)
- Blowfish (legacy)
- ArcFour (compatible with RC4, legacy)
- ArcTwo (compatible with RC2, legacy)
- SHA-2 (SHA-256, SHA-384, SHA-512)
- MD5 (legacy)
- MD4 (legacy)
- PKCS #12
- DER (binary or base64 encoded)
- CER (binary or base64 encoded)
External private key formats
- PKCS #8 keys
- OpenSSH/OpenSSL (SSLeay) keys
- PuTTY .ppk keys
Rebex HTTPS is designed primary for use in .NET framework applications. However, it can be used in several other scripting and hosting environments:
- Microsoft SQL Server SSIS packages
- Microsoft SQL Server SQL CLR stored procedures
- Microsoft PowerShell scripts
See how to use Rebex HTTPS in SSIS, SQL CLR and PowerShell environments.
- NTLM (not supported on Linux in .NET Core)
- Kerberos v5 (not supported on Linux, Android and iOS)
- Negotiate (not supported on Linux, Android and iOS)
Single sign-on authentication is supported for NTLM, Negotiate, Kerberos.
See more about authentication.