gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] r34877 - libmicrohttpd/doc


From: gnunet
Subject: [GNUnet-SVN] r34877 - libmicrohttpd/doc
Date: Sun, 11 Jan 2015 01:31:55 +0100

Author: grothoff
Date: 2015-01-11 01:31:54 +0100 (Sun, 11 Jan 2015)
New Revision: 34877

Modified:
   libmicrohttpd/doc/libmicrohttpd.texi
Log:
fix documentation

Modified: libmicrohttpd/doc/libmicrohttpd.texi
===================================================================
--- libmicrohttpd/doc/libmicrohttpd.texi        2015-01-10 19:06:21 UTC (rev 
34876)
+++ libmicrohttpd/doc/libmicrohttpd.texi        2015-01-11 00:31:54 UTC (rev 
34877)
@@ -1097,17 +1097,26 @@
 @cindex POST method
 @cindex PUT method
 
address@hidden
address@hidden
-for a @code{POST} that fits into memory and that is encoded with a
-supported encoding, the @code{POST} data will @strong{NOT} be given in
address@hidden and is instead available as part of
address@hidden()};
address@hidden data @strong{will} be made available
+incrementally in @var{upload_data}; even if @code{POST}
+data is available, the first time the callback is
+invoked there won't be upload data, as this is done
+just after MHD parses the headers.  If supported by
+the client and the HTTP version, the application can
+at this point queue an error response to possibly 
+avoid the upload entirely. If no response is generated,
+MHD will (if required) automatically send a 100 CONTINUE
+reply to the client.
 
address@hidden
-very large @code{POST} data @strong{will} be made available
-incrementally in @var{upload_data};
address@hidden itemize
+Afterwards, POST data will be passed to the callback
+to be processed incrementally by the application. The
+application may return @code{MHD_NO} to forcefully 
+terminate the TCP connection without generating a
+proper HTTP response. Once all of the upload data has
+been provided to the application, the application
+will be called again with 0 bytes of upload data.
+At this point, a response should be queued to complete
+the handling of the request.
 
 @item upload_data_size
 set initially to the size of the @var{upload_data} provided; this




reply via email to

[Prev in Thread] Current Thread [Next in Thread]