0

I have a legacy project running on .NET Framework 4.5, and we recently encountered issues because HttpClient relies on Windows for HTTPS connections.

Is there an alternative HttpMessageHandler that does not depend on Windows?

I couldn't find any solution using libraries like Bouncy Castle, and I would prefer not to implement a custom handler from scratch since this is a small project.

4
  • "we recently encountered issues" what issues? And why are you targetting .NET 4.5 if all current versions of Windows actually install v4.8 or v4.8.1 (you can't have multiple 4.x installed)? Commented Apr 1 at 13:17
  • The problem is the use of Windows 7. There's no support for many new ciphers under TLS 1.2. And here in Brazil a lot of Windows 7 are still in use. All .Net Framework versions dependes upon the Windows for that. Commented Apr 1 at 20:48
  • Fair enough, although use of Windows 7 is rather crazy given it is way out of support now, the upgrade is free or very cheap. Which ciphers are you missing that would cause you these issues? Normally client and server negotiate a common cipher, and TLS1.2 can be enabled on Windows 7, with the AES-256-CBC cipher. Commented Apr 2 at 0:12
  • The easiest way to "upgrade" a legacy client is using an intercepting HTTP proxy for such old clients. The client would then only establish a TLS connection to the proxy (which terminates it) which would then establish the actual connection to the server. Not a nice and clean solution but if somebody really stays with windows 7 and have ignored the possibility to upgrade to Win 10 (which has ended last year) then then they have to live with the consequences.
    – Robert
    Commented Apr 2 at 18:45

0

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.