aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2015-01-11 00:31:54 +0000
committerChristian Grothoff <christian@grothoff.org>2015-01-11 00:31:54 +0000
commit61876d057853557018e73cf4bde84d8021d11fbe (patch)
tree3c1c27a4da7df66eb05278c30bc95f3eb5af22dc
parentf52cd063f107d39fb14e4e3830666051321f403d (diff)
downloadlibmicrohttpd-61876d057853557018e73cf4bde84d8021d11fbe.tar.gz
libmicrohttpd-61876d057853557018e73cf4bde84d8021d11fbe.zip
fix documentation
-rw-r--r--doc/libmicrohttpd.texi31
1 files changed, 20 insertions, 11 deletions
diff --git a/doc/libmicrohttpd.texi b/doc/libmicrohttpd.texi
index c225b374..c0ad91a1 100644
--- a/doc/libmicrohttpd.texi
+++ b/doc/libmicrohttpd.texi
@@ -1097,17 +1097,26 @@ the data being uploaded (excluding headers):
1097@cindex POST method 1097@cindex POST method
1098@cindex PUT method 1098@cindex PUT method
1099 1099
1100@itemize 1100@code{POST} data @strong{will} be made available
1101@item 1101incrementally in @var{upload_data}; even if @code{POST}
1102for a @code{POST} that fits into memory and that is encoded with a 1102data is available, the first time the callback is
1103supported encoding, the @code{POST} data will @strong{NOT} be given in 1103invoked there won't be upload data, as this is done
1104@var{upload_data} and is instead available as part of 1104just after MHD parses the headers. If supported by
1105@code{MHD_get_connection_values()}; 1105the client and the HTTP version, the application can
1106 1106at this point queue an error response to possibly
1107@item 1107avoid the upload entirely. If no response is generated,
1108very large @code{POST} data @strong{will} be made available 1108MHD will (if required) automatically send a 100 CONTINUE
1109incrementally in @var{upload_data}; 1109reply to the client.
1110@end itemize 1110
1111Afterwards, POST data will be passed to the callback
1112to be processed incrementally by the application. The
1113application may return @code{MHD_NO} to forcefully
1114terminate the TCP connection without generating a
1115proper HTTP response. Once all of the upload data has
1116been provided to the application, the application
1117will be called again with 0 bytes of upload data.
1118At this point, a response should be queued to complete
1119the handling of the request.
1111 1120
1112@item upload_data_size 1121@item upload_data_size
1113set initially to the size of the @var{upload_data} provided; this 1122set initially to the size of the @var{upload_data} provided; this