Jamie Cameron

@iliarostovtsev we could do that, but it would make the dashboard slow to load if the user has a lot of complex status checks. Unless we can load that one...

Yes, that would be useful if we expect status monitors to take a long time to load.. However, it would mean changing the way the overall status is fetched so...

On the dashboard, since the server status is just one part of it, and the user would expect the other parts to load quickly..

Yeah, I'd rather not depend on node.js in Webmin. Can the server-side part of this be re-implemented in Perl?

That might be a nice feature, as it would match how the `ls` command works.

Can you tell from `tcpdump` or similar what data is being sent over these connections? Is it maybe a half-completed request?

Were you able to monitor any of these connections when they were first established?

Thanks for these network traces - they are very useful! However, it's surprising that the connection isn't closed after that "SSL mode" error. I will check in a fix for...

https://github.com/webmin/webmin/commit/f35b08dc94a48244d05d54e6a4f76c88921cfd62

@iliarostovtsev is this something that would be fixed by the work you've been doing recently on `link.cgi` ?