Are there any good references to which HTTP/2 frames/sections end up in the TLS1.3 0-RTT data?
Like, does the request itself end up there? headers? cookies? only GETs, not POSTs? etc ...
-
-
It's not sane, implementation-wise, to require the 0-RTT/1-RTT boundary correspond to anything definite in the app layer.
-
Makes sense, so it treats 0-RTT as initial part of stream? Then if the server-hello says "no dice", starts over?
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.