Dragana Damjanovic
Dragana Damjanovic
On the client side: nss writes tls finish message to stream 0 and after that sets the connection state to CONNECTED. The last handshake messages will be encrypted after the...
WebSockets over HTTP/2 are not supported by many servers. There can be different reasons for that. Support for WebSockets over HTTP/3 is a new IETF draft. The clients do not...
If a stream is block but still have data we will try to write on every iteration. We should handle this better and wait for stream to be unblocked.
#47 resolved the issue by clamping the delay to zero and adding a debug-assert. That was never a proper fix. Now we have a test that is failing with the...
We need to propagate neqo_transport::Connection to this function and call this function: https://github.com/mozilla/neqo/blob/25a862e97072a06b2ac93a6d5035e0202c0c7d6f/neqo-http3/src/connection.rs#L1048
Currently, we only buffer a certain fixed number of datagrams. If a UDP pack contains more HTTP datagrams than we would buffer, we will just drop them without informing the...
**The spec says:** > If at any point a session ID is received that cannot a valid ID for a client-initiated bidirectional stream, the recepient MUST close the connection with...
Currently, neqo-http3 allows the use of WebTransport during the ZeroRtt phase. The spack does not allow it.