3 ms·
Love to see stuff like this on the HN front page, when I know tons of web devs that have never even heard of SSE. Tangentially, I’m having a massive problem wi
by asynchronous 3y ago
Love to see stuff like this on the HN front page, when I know tons of web devs that have never even heard of SSE.
Tangentially, I’m having a massive problem with SSE datastreams erroring out about two minutes in for “ERR: Network chunk encoding” reasons, anyone else seen this before?
- no_wizard 3y agoTry sending the messages without compression. A lot of servers don't know how to handle this for SSE (since its a uncommon content type)
- bullen 3y agoYou need to send "keep-alive" "noop" to keep the routers happy, I do it ever 5 seconds.
- yababa_y 3y ago“Operator, please keep this line clear!”
- asynchronous 3y agoSee I tried that, still issues. Wondering if it is just a problem with internal firewalls and routing rules
- bullen 3y agoTry the connection from other server + client locations.
- chrismorgan 3y agoHas there been traffic during that two minutes? In theory, a TCP session can remain alive forever. In practice, various things got in the way, and you need traffic to keep it alive (keep-alive, ping, heartbeat, it gets given various names). I believe once a minute should be enough. I’ve encountered "ping" and "" used as SSE event names for this purpose.