Question about libcurl curl_easy_recv/curl_easy_send when working with https?

Question

C++ / C#

It just so happened that I had to work with libcurl in curl_easy_recv()/curl_easy_send() mode. The reason is the implementation of http steaming on a mobile device (c++). The regular mode of operation is not suitable - a long pullin GET request introduces curl_easy_perform () into an "eternal" loop (at the same time, callbacks are processed properly), it is not good to transfer it to a separate thread - if only because the "eternal" loop will eat part of the CPU, which will affect the battery. It’s just that sockets are not suitable, because as the server is on https, I don’t want to communicate with openSSL myself yet. The framework I use contains libcurl without ssl, but for tests, while I connect to the test brother of the prod server on http, everything works as it should. Now we need to write a request to the framework team (we work closely with them) to rebuild curl with ssl.
Question for the connoisseurs. After the framework is updated (curl with ssl), will I get curl_easy_recv() already decrypted data (request-response body ala-xml) or not? Waiting a week to check is too expensive, I can spend this time on an alternative solution.
Perhaps there is a generally more beautiful solution than curl. The task is to work on https streaming on win32/macos/ios/android platforms, C++ programming language