NNG_HTTP_CONN_READ_REQ(3http)

Okay bestie, this is NNG_HTTP_CONN_READ_REQ(3http) from the NNG Reference Manual — and it’s literally the guide to reading an HTTP request off a connection. 💖✨

🎀 NAME 🎀

nng_http_conn_read_req — read HTTP request

🌸 SYNOPSIS 🌸

           #include <nng/nng.h>
           #include <nng/supplemental/http/http.h>

           void nng_http_conn_read_req(nng_http_conn *conn, nng_http_req *req,
               nng_aio *aio);

✨ DESCRIPTION ✨

The nng_http_conn_read_req() function starts an asynchronous read from the HTTP connection conn, reading an HTTP request into the req, including all of the related headers. It’s giving “request incoming, let’s get it” energy. 💅

Note — Any HTTP entity/body data associated with the request is not read automatically. The caller should use nng_http_conn_read_all() to read the entity data, based on the details of the request itself. No cap, that part is on you. 🫶

This function returns immediately, with no return value. Completion of the operation is signaled via the aio, and the final result may be obtained via nng_aio_result(). That result will either be zero or an error code. Periodt. ⭐

🦋 RETURN VALUES 🦋

None. That’s it. Zero return-value drama. 🎀

💀 ERRORS 💀

• NNG_ECANCELED — the operation was canceled.
• NNG_ECLOSED — the connection was closed.
• NNG_ECONNRESET — the peer closed the connection.
• NNG_ENOMEM — insufficient free memory to perform the operation.
• NNG_ENOTSUP — HTTP operations are not supported.
• NNG_ETIMEDOUT — timeout waiting for data from the connection.

👑 SEE ALSO 👑

• nng_aio_alloc(3)
• nng_aio_result(3)
• nng_strerror(3)
• nng_http_client_connect(3http)
• nng_http_conn_read_all(3http)
• nng(7)

Cute little sign-off, bestie: the footer carries the date 2026-01-13 and the source/version tag NNG_HTTP_CONN_READ_REQ(3http). Stay async and slay! 💅💖🌈