Decided to update my vcpkg version, and ran tests for my networking tests only for it to return QUIC_STATUS_NOT_SUPPORTED/E_NOINTERFACE for loading the config. Turns out someone decided to switch the default SSL implementation from OpenSSL to Schannel on Windows and didn't enable an option to put it back.

Now it returns an error if you provide a certificate file. Luckily if you enable 0-rtt it still forces OpenSSL 🙄

Yh, SSL, I was implementing OpenAI on C level for https://molodetz.nl/retoor/r and whatever I did, i couldn't get it to work while python does just work fine using the same system in the background. So ofc, it had to be me. After a long time of failure and rewrites I found out that in some cases (and thus mine also) SSL_set_tlsext_host_name has to be done. Meanwhile I've learned how to debug SSL in detail but forgot already how that's done. Thank god. In all examples of how to write a https request this was not mentioned and they worked for many sites, but not mine. Why I didn't use CURL: just forgot about it! But now I have my own http library that I can add to rlib. Happy about that. It's so satisfying to work with source you know in detail. I'm sure for example that mine is as efficient possible and only does what i want.

@retoor As long as you had fun writing it :D

It was just a really silly error since there was no change to MSQuic. Ended up finding what changed by walking through the code with a debugger, which in term let me find the PR on vcpkg - I wouldn't even have minded if they had left OpenSSL the default and made an option (that I can set with the damn manifest) to switch to the windows exclusive SSL lib

Sounds like the old debugger for c