I am doing some SSE testing. I make a connection to my server with APIDog just fine. My server sends a keep alive packet every 10 seconds and APIDog is showing receipt of this packet in the timeline. I would expect the connection to stay alive, however after the request timeout duration expires, which by default is 5 minutes, I get a message on the timeline that the says “Disconnected from http://localhost:5575/sse”, and I no longer see any updates come in. So the first issue is that I would expect that since there is data coming in, that the timeout event should not trigger, however I can see that could be up to debate. However, the bigger issue is that when I receive that message on the timeline, my server does not see a disconnect. The connection to the server stays alive. The only way to actually disconnect is to kill the APIDog application altogther. When I actually kill the APIDog process, my server does get the disconnect. So even though the message in the timeline is saying it has disconnected, it looks like the underlying HTTP connection itself is not disconnecting and stays open but becomes an orphan because there is no way to manually disconnect it.
Yes, I know that, and I do that. My point of the post is about the connection being active when it states it is actually disconnected. That would seem to be a bug to me. If one gets a message saying that it is disconnected, it should be disconnected, and it is not, and can cause issues with the server being tested, as well as having an orphaned connection within the Apidog app itself.
Thank you for your feedback. We will investigate and fix this issue as soon as possible.