Hi Daniel, Thanks, but no worries: this one has my attention, I just need to find the time to look into it. Oh, in terms of what would help: automated testcases (especially those ready for integration with 'make check') are always very helpful for speeding up things...
Happy hacking! Christian On 10/29/18 8:09 AM, Daniel Bujnik wrote: > Hi Christian, > > I have created a mantis bug for the issue I had described hoping it will > get some more attention: > https://gnunet.org/bugs/view.php?id=5463 > > Please let me know if you have any questions or would like me to test > some more fixes. > > Kind regards, > Daniel > > > > > > > On Sat, 20 Oct 2018 at 11:46, Christian Grothoff <[email protected] > <mailto:[email protected]>> wrote: > > Dear Daniel, > > You didn't mention which thread mode you were using, but manual > inspection suggests your issue should occur in thread-per-connection > modes (only). In that case, I've pushed a (likely) fix in > b55cd46b..47281241 to Git master. > > Please test and report back! > > Happy hacking! > > Christian > > On 10/19/2018 03:53 PM, Daniel Bujnik wrote: > > Hello, > > > > I am using libmicrohttpd with MHD_OPTION_NOTIFY_CONNECTION > parameter to > > receive notifications for TCP connection opening/closing. > Notifications > > for opening case are coming through as expected, however I am > > experiencing problems with closing case, where I am NOT getting the > > callback when my client terminates, though I can see client FIN packet > > in tcpdump on the server side and connection stops appearing in > netstat. > > > > Eventually the closing notification is being delivered by > libmicrohttpd > > but that is just after a new TCP connection is opened. The sequence of > > callbacks I am seeing is as followed: > > > > 1) callback with MHD_CONNECTION_NOTIFY_STARTED - TCP connection A > opened > > 2) callback with MHD_CONNECTION_NOTIFY_STARTED - new TCP > connection B is > > opened > > 3) callback with MHD_CONNECTION_NOTIFY_CLOSED - TCP connection A > closed > > > > Of course I would expect nr 3 to come before nr 2. I am using nc to > > open/close sockets on client end. > > > > I would appreciate any comments on the described issue. Is that > behavior > > correct? If not is there a way to make it right? > > > > Kind regards, > > Daniel > > >
