Open larseggert opened 3 months ago
the second connection seems to run into idle timeouts on both client and server.
I am assuming that you are basing this on the following log line?
0s269ms INFO Closing timer expired
I can reproduce locally. That said, the timer (log line above) does not seem to correlate with the --idle
flag. Setting the --idle
flag to 10
still has the client terminate immediately, not wait for 10s, but still print the line above.
I can debug further on Monday.
0-RTT resumption via --resume
seems to not work at all. At least I only see one handshake in the pcap when I run the test. Also, the client prints [Client ba48fde68c1e6a18] 0-RTT rejected
and the files for objects requested over 0-RTT are empty.
(It does seem to work when passing --qns-test zerortt
to the client.)
I used the following patch to
test/test.sh
to introduce a 0-RTT resumption (in order to debug the QNS failures, see #1874).Now when I run
test/test.sh
, the second connection seems to run into idle timeouts on both client and server.@mxinden any thoughts?