Hi there,
I have implemented SSE to one of my go-app written apps. I implemented it with my own methods and it works but the problem is on firefox, it gets NS_BIND_ABORTED error after exactly 30 seconds and I'm sure everything is correct with headers and stuff, I also tested locally without any reverse proxy, still behaves the same.
The reason as far as I came-up with is, because server sends text/event-stream and it's being read by golang not the browser native EventSource of JS, then firefox thinks that it never being consumed and closes the connection.
I also confirmed that hard-reload makes it work for a while but subsequent reloads are still having same 30seconds error.
I'm not gonna deep dive into the code and try to question how you consume the response, my question is this, have you tested this code on firefox if that works?
Hi there,
I have implemented SSE to one of my go-app written apps. I implemented it with my own methods and it works but the problem is on firefox, it gets
NS_BIND_ABORTEDerror after exactly 30 seconds and I'm sure everything is correct with headers and stuff, I also tested locally without any reverse proxy, still behaves the same.The reason as far as I came-up with is, because server sends text/event-stream and it's being read by golang not the browser native
EventSourceof JS, then firefox thinks that it never being consumed and closes the connection.I also confirmed that hard-reload makes it work for a while but subsequent reloads are still having same 30seconds error.
I'm not gonna deep dive into the code and try to question how you consume the response, my question is this, have you tested this code on firefox if that works?