/AFAIK, t/he only difference between PUT and POST is that PUT must be
idempotent. That is a semantic distinction of relevance to your
application, it changes nothing for the wire protocol or the MHD API.
MHD internally makes no distinction between PUT and POST and will pass
you all of the data in the same way(s). Which way you get the PUT data
depends -- just as with POST -- on the specifics of how you instructed
the browser to submit it.
Happy hacking!
Christian
On 08/24/2012 06:58 PM, [email protected] wrote:
Hey all,
I noticed that the method passed to:
Function Pointer: int *MHD_AccessHandlerCallback (void *cls, struct
MHD_Connection * connection, const char *url, const char *method, const char
*version, const char *upload_data, size_t *upload_data_size, void **con_cls)
will always be GET, POST, PUT or DELETE. This is all well and good for GET,
POST, and DELETE, but for PUT I was wondering how that worked in terms of
upload_data? Is it the same as POST where for small chunks of data it is
directly accessible via MHD_get_connection_values() whereas for larger requests
it is via upload_data?
Cheers,
Mike
