Can't open connection to https://dir.xiph.org and download xml file /yp.xml System.ComponentModel.Win32Exception (0x80090331): The client and server cannot communicate, because they do not possess a common algorithm. #26
-
Hi, thank you for building this package! I'm trying to use it and download a 4Mb xml file from this ICE cast server: I've checked and they only support TLS 1.3 it seems. I'm running windows 10 Pro and using .Net 9.0 in visual studio 2022. Exception thrown: 'System.Net.Http.HttpRequestException' in System.Private.CoreLib.dll The SSL connection could not be established, see inner exception. System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. I've configfured the httphandler like this:
Method is get via the httpclient, and sending the same headers as postman:
client.DefaultRequestHeaders.Add("Accept", "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7"); I hope you can help me get me on the right track. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Are you sure TLS 1.3 is enabled on your OS ? Which cipher suite is the server using ? Is there a corresponding cipher supported by your OS ? |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply! TLS 1.3 (server has no preference)TLS_AES_128_GCM_SHA256 (0x1301) ECDH x25519 (eq. 3072 bits RSA) FS | 128 I checked using https://www.ssllabs.com/ssltest/analyze.html?d=dir.xiph.org |
Beta Was this translation helpful? Give feedback.
I've done more research and you are 100% correct!
Windows 10 (any version) does not support .Net (any version) TLS 1.3
I've enabled it via the registry, via Edge browser (the experimantal TLS 1.3). I even tried installing the used cypher TLS_CHACHA20_POLY1305_SHA256.
Nothing works. A workaround is to make use of a "non dot net" TLS 1.3 supporting HTTPclient OR install windows 11 :)
After installing windows 11, TLS 1.3 was supported AND working. MS likes us to move to Windows 11 it seems!