Streaming (SSE)
Not runSeven events. Watch when they arrive.
Run the check to collect evidence.
NETOKAY / SSE TEST
This browser → NetOkay · A short server-sent event stream
Seven events. Watch when they arrive.
Run the check to collect evidence.
The check requests https://netokay.net/v1/control/stream from this browser
and reads the response as it arrives. The server sends seven named events:
start, five tick events about 500 ms apart, then
done, in roughly 2.5 seconds. The table records when each event reached the
page and the gap since the previous one.
It is a browser-to-NetOkay control check: it shows whether a short server-sent event stream reaches this browser event by event through its current network path. It does not open your own endpoint and cannot see your proxies.
In a browser console, subscribe to the named events with EventSource. Each
event carries a sequence number and the server-side elapsed time in milliseconds.
const source = new EventSource('https://netokay.net/v1/control/stream');
for (const name of ['start', 'tick', 'done']) {
source.addEventListener(name, (event) => {
console.log(new Date().toISOString(), name, event.data);
if (name === 'done') source.close();
});
}
From a terminal, watch the same stream with output buffering disabled:
curl -N --max-time 15 https://netokay.net/v1/control/stream
The NetOkay CLI observes it with --transport sse and can point at your own
public HTTPS endpoint; see the CLI reference.
done, arrived within the 15-second limit. An unfinished stream is an
incomplete observation, not a diagnosis.
Arrival timing alone cannot say which application, intermediary, or client caused grouped delivery, and a 2.5-second stream cannot prove long-term stability.
When this check shows close together, or your own stream arrives in one block, something between the server and the reader is holding the response until it is complete. The check cannot tell these apart.
proxy_buffering is off for that route.
response.text() instead of reading the stream.
If this check arrives over time and your application does not, continue with SSE not streaming or arriving all at once?.
No. It only reads NetOkay's control stream. For your own public HTTPS endpoint, run the
NetOkay CLI with --transport sse from the failing machine, or watch it with
curl -N as shown above.
Because something on the path buffered them. Proxy response buffering and compression are the usual causes; the guide above shows how to check each side separately.
Server-sent events push text from server to client over an ordinary HTTP response,
reconnect on their own, and pass through any proxy that streams responses. WebSocket
carries messages in both directions but needs every hop to support the
Upgrade handshake. Choose by the direction your data flows.
Need to check your own endpoint? Check HTTP status, then compare with your device.