Plan with Http and Https

Stream: lean4

[Alfredo Moreira-Rosa]

This question is maybe more for @Sofia Rodrigues ,
I see a lot of great advancement in foundations for Async, TCP/UDP, Files stack for lean 4.25.
I also saw you have a custom Http layer in a repository.
So my questions are:

• Is the plan to roll Http API starting from lean 4.26 or are there more foundational building blocks needed before that's possible ?
• For Https, is the plan to make OpenSSL bindings in lean Std Internal ?

If so, do you need help ? I would love to help in this subject. I'm familliar with OpenSSL C library.

[Markus Himmel]

We do not plan to add TLS support to the Lean HTTP server. Recommended way to deploy the Lean HTTP server will be behind a reverse proxy like Nginx or Apache that handles TLS.

[Alfredo Moreira-Rosa]

I can understand for server, but what about client Https ?

[Markus Himmel]

It will come eventually, but it's not on the roadmap yet since this is a big and complicated project (especially since we're using LibUV for TCP). For the same reason this isn't the best project for a community contribution, since just reviewing and testing such a contribution will require a major time investment from the maintainers which needs some planning and coordination.

[Alfredo Moreira-Rosa]

I understand.
So since i want to advance this topic, i guess this means it has to be made outside of lean.
I'll keep you all informed anyway. And i'll make sure my work is reusable with proper licence so that if in the future you want to take a look at it as an inspiration you'll be able to do so.