Maybe you have an off_t 32-bit/64-bit confusion in your code (did you
build your main C application with AC_SYS_LARGEFILE?). If that is the
case, it might be that the "content-size" returned by your server is
larger than what the callback is able/willing to provide. Then, when the
server dies and closes the TCP connection, the HTTP client will
interpret that as the 'end of response' and ignore content-size, which
would explain your observation.
I would suggest looking at the network traffic with wireshark, and my
guess is that the HTTP server will have delivered the full response and
the client is just waiting for more.
Happy hacking!
Christian
On 02/27/2015 05:10 AM, Bob Furber wrote:
I have a microhttpd based server program (mhdServer ) that happily
serves files and more, when run on a 64-bit LinuxPC and is accessed
through requests such as http://localhost:8080/filename.html.
However, porting this program to a remote 32-bit Arm-Linux platform is
proving to be a challenge: It ALMOST WORKS:
* It replies with a “404 File not found” response to requests for
non-existing files ..as it should
But, requests for existing files do not get the anticipated reply:
* Client hangs waiting for requested web page files
* However, the web page is displayed by the client as soon as the
mhdServer program is terminated!!
Examination of the mhdServer program with a remote debugger indicates that:
* All client requests are being received
* The requested files are indeed located and fopen'ed
* MHD_create_response_from_callback() returns MHD_YES (1)
* MHD_queue_response() returns 1, indicating success ..yet the client
keeps waiting patiently for its response ..which only arrives upon
mhdServer's dying breath
I have been banging my head against this for days. Can anyone suggest
any tests that might shed light on this strange behaviour?