The state machine around EndOfEarlyData is a bit messy, which caused a problem introducing the new message in QUIC. We keep waffling on whether that state junction should no-op the EndOfEarlyData state or skip it. Since skipping it caused us to miss this spot, let's try no-op-ing it. As a test, so this CL is easier to cherry-pick, I've just duplicated the basic server test. Better, however, would be to run all the extensions tests under QUIC. (In particular, this is missing 0-RTT coverage.) But this is a large diff and requires improving the mock QUIC transport, etc., in runner. That work is done in follow-up CLs, which replace this duplicated test. Change-Id: I25b6feabdc6e5393ba7f486651986a90e3721667 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/44985 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com>chromium-5359
parent
f4a88296fc
commit
71ed9d7538
2 changed files with 57 additions and 19 deletions
Loading…
Reference in new issue