Timeout Error

[dtjohnson]

Very nice library!

Could you explain why you are throwing an error here:
https://github.com/Yaffle/EventSource/blob/master/eventsource.js#L601

I have a global error handler that displays errors to the user and this keeps triggering the error handler.

[Yaffle]

I want to show that you are not sending messages every 45 seconds. This is needed to detect disconnects.

[Leonidnei]

How do I overcome this exception?

[darrenscerri]

Send a heartbeat at least every 45 seconds to keep connection alive.

[fperezgaliana]

Hi! I know the server should send a 'heartbeat' every few seconds, but is there a way to avoid the console.error message?

I've tried handling the error like this:

es.addEventListener("error", (error) => {
        console.log("Error in SSE connection", error);
        
        return false;
      });

But it didn't make any change. Thanks.

[Yaffle]

@fperezgaliana ,
The code change is needed to.

May be, console.log() should be used here at line 596 - https://github.com/Yaffle/EventSource/blob/master/src/eventsource.js#L596

[karser]

Hello, I'm also getting Error: No activity within 45000 milliseconds. Reconnecting.. This is indeed annoying that you can't catch this error. I'd be happy if it's possible.
On another hand, the native EventSource also requires heartbeat, so it's better to enable it on your backend.

[Yaffle]

@karser, native EventSource may use TCP keepalives , I think

[farukhali]

I am experiencing a strange issue, for some clients connection is timing out though we are sending heartbeat. It's working fine for most of the users but for some users connection keep timing out. Most of these users are using Chrome latest version, any thoughts?

[Yaffle]

@farukhali , do you receive some other events? can you check on the client side if there is something unusual? if you are using plain text HTTP some antivirus software may block streaming responses.

[farukhali]

@Yaffle normal http requests are working fine. No event received through SSE. Content type for this request is text/event-stream; charset=utf-8. I also suspect antivirus/firewall but it's difficult to get connected with a customer having this problem.

[akaskj]

@farukhali @Yaffle I am facing the exact same issue, even though I am sending heartbeats every 15 seconds I am seeing this error thrown every 45 seconds. We also send other data as soon as the connection is established and even that data is not received by the customer.

@farukhali were you able to find a fix or a workaround for it?

[warrendodsworth]

To suppress the error use preventDefault()

es.addEventListener("error", (e) => {
        console.log("Error in SSE connection", error);
        e.preventDefault()
});

[kaesetoast]

@warrendodsworth it seems like this does not work any more. I did not check yet when it broke, but it works fine with 1.0.12. I just tried to implement this in a project using 1.0.22 and now the error-object is missing a preventDefault-function.

[kaesetoast]

I just realized that you don't actually throw a real error any more. So if I read your code right, there is no need to suppress anything really. I guess this can be closed then?

[Yaffle]

@kaesetoast , seems, so