Re: [libmicrohttpd] MHD_NotifyConnectionCallback

2018-02-14 Thread Miguel Sancho
Sorry, let me re-write the scenario: I am noticing that in my application and curl command as http client - with MHD 0.9.50 the MHD_CONNECTION_NOTIFY_CLOSED is received immediately after HTTP is processed - with MHD 0.9.55 the MHD_CONNECTION_NOTIFY_CLOSED is NOT received immediately af

[libmicrohttpd] MHD_NotifyConnectionCallback

2018-02-14 Thread Miguel Sancho
Hi MHD Team, I am noticing that in my application: - with MHD 0.9.50 the MHD_NotifyConnectionCallback is executed by MHD (OK) - with MHD 0.9.55 the MHD_NotifyConnectionCallback is not executed by MHD (KO) is this known? do I need to make any update in my application for MHD 0.9.55? a

Re: [libmicrohttpd] socket_context not set (libmicrohttpd-0.9.50)

2017-06-05 Thread Miguel Sancho
ok, I understand now, thanks!

Re: [libmicrohttpd] socket_context not set (libmicrohttpd-0.9.50)

2017-06-05 Thread Miguel Sancho
Christian, > Eh, what is that "*" doing in the "if" line? reason is that in definition of the MHD_ConnectionInfo union, I see socket_context defined as "void**", maybe it should be just "void*" > Also, what code do you use in the connection notification callback to set the socket_contest? MyCon

Re: [libmicrohttpd] socket_context not set (libmicrohttpd-0.9.50)

2017-06-02 Thread Miguel Sancho
Christian, thanks for your answer, I need to recheck, already doing the following in the #MHD_AccessHandlerCallback and the *socket_context appears to be NULL: *MHD_get_connection_info(connection,MHD_CONNECTION_INFO_SOCKET_CONTEXT);* Regards 2017-06-01 17:11 GMT+02:00 Miguel Sancho : >

[libmicrohttpd] socket_context not set (libmicrohttpd-0.9.50)

2017-06-01 Thread Miguel Sancho
Hi, finding the following issue (libmicrohttpd-0.9.50), I would like to check whether this is already known. Seems that socket_context is not set in #MHD_AccessHandlerCallback. - In #MHD_NotifyConnectionCallback (STARTED), **socket_context object is created - In #MHD_AccessHandlerCallbac

Re: [libmicrohttpd] Sleeping a request thread

2017-05-24 Thread Miguel Sancho
Ken, thanks a lot for your comments, this really helps I agree it doesn't seem to be related to reaching the maximum number of threads Regards Miguel 2017-05-24 10:53 GMT+02:00 Miguel Sancho : > Christian, thanks a lot for your answer, > here are more details, maybe you have see

Re: [libmicrohttpd] Sleeping a request thread

2017-05-24 Thread Miguel Sancho
or a "long" while() (lasting for example 4s) May the MHD thread sleep have an impact in other threads not related to MHD, any approach to work-around this? Miguel 2017-05-19 0:22 GMT+02:00 Miguel Sancho : > Hi, > using the MHD_USE_THREAD_PER_CONNECTION mode, > are there any issue

[libmicrohttpd] Sleeping a request thread

2017-05-18 Thread Miguel Sancho
Hi, using the MHD_USE_THREAD_PER_CONNECTION mode, are there any issues in "sleeping" the request thread some seconds waiting for response? any known drawback in MHD? for example to wait 4s: usleep(400) MHD_queue_response (..) Thanks

Re: [libmicrohttpd] RPM package for MHD v0.9.50

2017-02-20 Thread Miguel Sancho
Hi Silvio, thanks for your response, I should have added that the *MHD v0.9.50.rpm package* we are looking for, should be compatible with the* CentOS Linux distro and i386 arquitecture*, any link for this? 2017-02-17 12:47 GMT+01:00 Miguel Sancho : > Hi MHD Team, > I am looking for RPM pa

[libmicrohttpd] RPM package for MHD v0.9.50

2017-02-17 Thread Miguel Sancho
Hi MHD Team, I am looking for RPM packages for MHD version 0.9.50 or later. is this available? otherwise, any hint to generate .RPM package from MHD source? Thanks Miguel

Re: [libmicrohttpd] MHD_RESPMEM_PERSISTENT

2017-01-25 Thread Miguel Sancho
thanks for your responses, so this code is not safe: * response = MHD_create_response_from_buffer(size,(void*)buffer, MHD_RESPMEM_PERSISTENT); ret = MHD_queue_response (connection, 200, response); MHD_destroy_response (response); free(buffer);* the following work-aroun

Re: [libmicrohttpd] MHD_RESPMEM_PERSISTENT

2017-01-24 Thread Miguel Sancho
Hi Silvio, thanks for answering, > Could you show what error and how the buffer was assigned? The error is that the downloaded binary file from the MHD server with the MHD_RESPMEM_PERSISTENT option is corrupt: - Same size as the original - The initial bytes are ok - but from a certain p

[libmicrohttpd] MHD_RESPMEM_PERSISTENT

2017-01-24 Thread Miguel Sancho
Hi, using the *MHD_RESPMEM_PERSISTENT* option I am getting an error. The following HTTP response gives a corrupt file when downloading from libmicrohttpd.0.9.50. However same code with *MHD_RESPMEM_MUST_COPY option *works fine: response = MHD_create_response_from_buffer(size,(void*)buffer, *MHD_R