Are there any good references to which HTTP/2 frames/sections end up in the TLS1.3 0-RTT data?
One caveat maybe: presumably only GETs can be pipelined within the 0-RTT? E.g. a GET, POST pipeline would be bad(tm).
-
-
So it might force a re-ordering of pipelined requests? which is crossing an app layer boundary.
-
Not sure I follow POST/GET issue. 0-rtt data is all/nothing. If reject, app layer should get signal to retry everything
- 2 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.