-
Notifications
You must be signed in to change notification settings - Fork 15
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
Allow zero-length QUIC frames to be sent #67
Comments
A more quic-centric explanation: Currently, quicker only sends new STREAM frames if there is actual data for that stream. Ending a stream is just sending a STREAM frame with the appropriate frame type (FIN, length and offset are specified in the frame type, rather than a specific flag or something). Due to how our flow control now creates new frames from streams, this is an edge case we don't deal with yet. Expected behaviour: |
At the moment, doing
QuicStream.end()
without buffering new data will result in the stream end not being sent to the other endpoint. This is a result of zero-length QUIC frames not being supported by QUICker yet.The text was updated successfully, but these errors were encountered: