Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report for trillium-sse, trillium-http: SSE is sent with chunked encoding, but should not be #583

Open
jbr opened this issue Feb 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jbr
Copy link
Contributor

jbr commented Feb 19, 2024

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.

@jbr jbr added the bug Something isn't working label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant