On Mon, 2017-05-08 at 14:14 -0800, Dan Morphis wrote: > That appears to have fixed the issue.
Hmm, I wasn't expecting that :) I thought Node would throw an exception when sending an HTTP response after the connection has already been destroyed. But anyway, can you confirm the session is ending properly after that fault? You can look at whether the lastInform parameter is updated. -- Zaid Abdulla <[email protected]> _______________________________________________ Users mailing list [email protected] http://lists.genieacs.com/mailman/listinfo/users
