Bug report for `trillium-sse`, `trillium-http`: SSE is sent with chunked encoding, but should not be
jbr opened this issue · comments
Currently, there is no way to send a http/1.1 response without either a Transfer-Encoding: Chunked
OR Content-Length
header. However, per the whatwg document.
Authors are also cautioned that HTTP chunking can have unexpected negative effects on the reliability of this protocol, in particular if the chunking is done by a different layer unaware of the timing requirements. If this is a problem, chunking can be disabled for serving event streams.