Hello, I am using libmicrohttpd (0.9.69) in a RestFul API server that uses Digest authentication. All the endpoints are working fine except for a PUT on one of the endpoints where the client uploads a large (12~13MBytes) file to the application. This fails on all browsers/OSs expect Chrome on Ubuntu.
Using wireshark, I was able to see that: 1- The client/browser sends the initial PUT request and starts uploading the file. 2- After few msecs and part of the file uploaded, the application/libmicorohttpd sends the Auth fail 401 response (with new nonce). 3- This is immediately followed by the application/libmicrohttpd closing the TCP connection. 4- Only Chrome on Ubuntu re-opens a new TCP connection and uses the new nonce and hence the API request is accepted and the file is uploaded. Other browsers simply abort and show an error message. On all other endpoints, the initial API request, the 401 reply from the application/libmicrohttpd, and subsequent API request all happen on the same TCP connection, as expected. There is nothing different in how our application interacts with libmicrohttpd in regards to this endpoint, so I am suspecting that for some reason libmicrohttpd closes the TCP connection. Is there a way to prevent that? or even gain more insight on to why it is closing the connection? Any help would be appreciated. Thank you, Ahmed ----------------- Other info: 1 - This issue is happening in development settings, so there are no other connections to the application/libmicorohttpd 2- MHD_USE_EPOLL_INTERNALLY_LINUX_ONLY 3- MHD_OPTION_THREAD_POOL_SIZE, pool size 10 4- MHD_OPTION_CONNECTION_TIMEOUT, timeout 3 seconds
