Web service suspending bug
E
Elijah Rastorguev
The bug isn't strictly security-related, but rather has to do with the logic behind service shutdowns. If you run a NodeJS web service and use a Long Polling connection internally, for example for Telegram bots (Telegraf library), and then stop the web service, HTTP connections stop working (as expected), and the console reports that the server is stopped. However, the bots continue to run (via Long Polling), meaning the server is still running, even though it's listed as stopped. Free Tier was used where a bug occurred.
I would be happy to receive a nice bonus if this report helps make your services better.
My Workspace ID:
tea-csppavl6l47c73cudpd0
Log In
E
Elijah Rastorguev
This may be due incorrect handling of the SIGTERM / SIGKILL commands. Even after several hours, the service continues to work, although the status is "Stopped" and the logs also show that the status is "Stopped"