From 321a372a0c6d859f47e1099a76b13fee8d9efe88 Mon Sep 17 00:00:00 2001 From: gdamore Date: Wed, 8 Oct 2025 21:54:34 +0000 Subject: deploy: af596b6ccf14b4d2fc2f5c6ef04870186d99d828 --- ref/api/http.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'ref/api/http.html') diff --git a/ref/api/http.html b/ref/api/http.html index aac5ec43..67c7048e 100644 --- a/ref/api/http.html +++ b/ref/api/http.html @@ -410,7 +410,7 @@ for display to users.

Retrieving Headers

const char *nng_http_get_header(nng_http *conn, const char *key);
-bool nng_next_header(nng_http *conn, const char **keyp, const char **valuep, void **next);
+bool nng_http_next_header(nng_http *conn, const char **keyp, const char **valuep, void **next);

The nng_http_get_header returns the header value matching key that was received over conn, or NULL if no such header exists.

@@ -776,7 +776,8 @@ final argument is the nng_a it may simply let the framework do so on its behalf. The server will perform this step if the callback has not already done so.

Response headers may be set using nng_http_set_header, and request headers -may be accessed by using nng_http_get_header.

+may be accessed by using nng_http_get_header. They can also be iterated +over using nng_http_next_header

Likewise the request body may be accessed, using nng_http_get_body, and the response body may be set using either nng_http_set_body or nng_http_copy_body.

-- cgit v1.2.3-70-g09d2