| commit | a366010c5f5736436338acad1e2a11d17f80c0fe | [log] [tgz] |
|---|---|---|
| author | fkastenholz <fkastenholz@google.com> | Wed Aug 28 05:19:24 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 29 15:36:46 2019 -0700 |
| tree | 3c38a7154914e7fdc93e394b0204f019917fd972 | |
| parent | edeeb47d60bc7342c61c310f814f4989183dcfed [diff] |
Have framer store frame type currently being processed This CL has QuicFramer save the frame type for the frame that it currently is extracting from the packet and processing. This is done so that the IETF QUIC Transport Connection Close can get the type of frame that precipitated the close. If the frame-type was not saved like this then it would need to be passed around in the call stack -- one more parameter threaded throughout many calls in QUIC. This done only when IETF Framing (version 99) is enabled. Tests in quic_framer_test.cc have been modified to check that the right frame type has been saved (done in all of the On...Frame upcalls, so that the testing is fairly complete). Also checks that the saved type is 0 when not processing a frame (eg, when doing header processing) OR when not doing IETF QUIC Framing. gfe-relnote: N/A is only for Version 99/IETF QUIC Framing. PiperOrigin-RevId: 265888094 Change-Id: If068d49c9f72b4e3c0e8eb3e7ab7460abde85f8a
QUICHE (QUIC, Http/2, Etc) is Google‘s implementation of QUIC and related protocols. It powers Chromium as well as Google’s QUIC servers and some other projects.
The code is currently in process of being moved from https://cs.chromium.org/chromium/src/net/third_party/ into this repository. Please excuse our appearance while we're under construction.