I'm experiencing an issue while operating the client on a Windows system with active antivirus (AV) software.
Here's what's happening: Upon executing shell commands that the AV software flags as malicious, the AV terminates the websocket without killing the process. This is expected. However, despite this termination, I observe that the client continues to send health check (GET) and device (POST) requests but it doesn't send request /client.
After reviewing the code, I've not found any segment that handles the unexpected termination of the websocket. Specifically, there's no apparent mechanism to recreate the socket if it gets killed or to stop sending requests once the socket is down.
I hope this description provides a clearer understanding of the issue. Please let me know if you need more information.
I'm experiencing an issue while operating the client on a Windows system with active antivirus (AV) software.
Here's what's happening: Upon executing shell commands that the AV software flags as malicious, the AV terminates the websocket without killing the process. This is expected. However, despite this termination, I observe that the client continues to send
health check (GET)anddevice (POST)requests but it doesn't send request /client.After reviewing the code, I've not found any segment that handles the unexpected termination of the websocket. Specifically, there's no apparent mechanism to recreate the socket if it gets killed or to stop sending requests once the socket is down.
I hope this description provides a clearer understanding of the issue. Please let me know if you need more information.