On 09/20/2012 07:03 PM, Glenn wrote: > > Following up on today's digest --- > > I'm going through the libmicrohttpd tutorial and working through the > examples. One question that comes to my mind is why the second invocation of > the connection handler is necessary/desirable. In the tutorial it is stated: > "This is because the content of the message body will not be received if a > response is queued in the first iteration. Furthermore, the connection will > be closed right after the response has be transferred then." Apparently I'm > missing something. Can someone supply details (or a pointer to where this has > already been discussed) as to the requests and responses that MHD is going > through? > > Glenn
Yeah, this is turning into a bit of a FAQ... Some pointers, in no particular order: http://lists.gnu.org/archive/html/libmicrohttpd/2011-09/msg00027.html http://lists.gnu.org/archive/html/libmicrohttpd/2009-02/msg00000.html http://lists.gnu.org/archive/html/libmicrohttpd/2008-08/msg00009.html http://lists.gnu.org/archive/html/libmicrohttpd/2012-04/msg00001.html http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html http://curl.haxx.se/mail/lib-2004-08/0002.html http://www.iandennismiller.com/blog/2009/09/curl-http1-1-100-continue-and-multipartform-data-post/ Happy hacking! Christian
