[GNUnet-SVN] [libmicrohttpd] branch master updated: clarify return value is intentionally ignored

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository libmicrohttpd.

The following commit(s) were added to refs/heads/master by this push:
     new bf7c90c3 clarify return value is intentionally ignored
bf7c90c3 is described below

commit bf7c90c30f7c6c0227fb873bfb1f361f03e6b1f7
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun Jun 2 22:13:00 2019 +0200

    clarify return value is intentionally ignored
---
 src/microhttpd/connection.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/src/microhttpd/connection.c b/src/microhttpd/connection.c
index 5c874d99..f6c1dbb5 100644
--- a/src/microhttpd/connection.c
+++ b/src/microhttpd/connection.c
@@ -924,12 +924,12 @@ MHD_lookup_connection_value (struct MHD_Connection 
*connection,
   const char *value;
 
   value = NULL;
-  MHD_lookup_connection_value_n (connection,
-                                 kind,
-                                 key,
-                                 (NULL == key) ? 0 : strlen(key),
-                                 &value,
-                                 NULL);
+  (void) MHD_lookup_connection_value_n (connection,
+                                        kind,
+                                        key,
+                                        (NULL == key) ? 0 : strlen(key),
+                                        &value,
+                                        NULL);
   return value;
 }
 
@@ -1811,9 +1811,9 @@ build_header_response (struct MHD_Connection *connection)
             simply only force adding a content-length header if this
             is not a 'connect' or if the response is not empty
             (which is kind of more sane, because if some crazy
-            application did return content with a 2xx status code, 
+            application did return content with a 2xx status code,
             then having a content-length might again be a good idea).
-           
+
             Note that the change from 'SHOULD NOT' to 'MUST NOT' is
             a recent development of the HTTP 1.1 specification.
           */

-- 
To stop receiving notification emails like this one, please contact
address@hidden