You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's relatively easy to implement an endpoint that will use Server-Sent Events to stream a response to a client, and it's also relatively easy to write HTTP proxy code that does not correctly support SSE responses.
So, we should expose an endpoint in go-httpbin that makes it easier to test/validate that proxies correctly handle SSE.
The text was updated successfully, but these errors were encountered:
Each event is a "ping" that includes an incrementing integer ID and an
integer Unix timestamp with millisecond resolution:
event: ping
data: {"id":9,"timestamp":1702417925258}
Fixes#150.
Each event is a "ping" that includes an incrementing integer ID and an
integer Unix timestamp with millisecond resolution:
event: ping
data: {"id":9,"timestamp":1702417925258}
Fixes#150.
It's relatively easy to implement an endpoint that will use Server-Sent Events to stream a response to a client, and it's also relatively easy to write HTTP proxy code that does not correctly support SSE responses.
So, we should expose an endpoint in go-httpbin that makes it easier to test/validate that proxies correctly handle SSE.
The text was updated successfully, but these errors were encountered: