Synthesize an EndOfGroup object when FIN arrives without data. Currently, when parsing a has_end_of_group stream, when the object is complete but no FIN has arrived, it can't be delivered because we don't know the status yet. If a FIN arrives later, the object's status will change to kEndOfGroup. This introduces object delivery latency. Furthermore, there is a bug in that it can induce calls to OnObjectFragment() where the offset is > 0 and the payload is empty, which is not envisioned in the API and is causing QUICHE_BUG in interop. This CL removes the kAwaitingNextByte state; any object with payload can be delivered. If a FIN arrives immediately after, the parser will create a synthetic kEndOfGroup object. If the payload is delivered in parts, it is possible for the object_status to suddenly change from Normal to EndOfGroup. PublishedObjectMetadata no longer regards this as a malformed track. This might open up some shenanigans where two publishers have different EndsOfGroup, but detection of that is best-effort. There is a performance advantage because if the last Normal object is delivered with EndOfGroup status, it is able to be FINed / EOGed immediately rather than waiting for a separate, synthetic object to arrive. PiperOrigin-RevId: 997993975
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.
QUICHE has binaries that can run on Linux platforms.
Follow the instructions to install Bazel.
sudo apt install libicu-dev clang lld cd <directory that will be the root of your quiche implmentation> git clone https://github.com/google/quiche.git cd quiche CC=clang bazel build -c opt //... ./bazel-bin/quiche/<target_name> <arguments>
There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
Usage: quic_client <URL>
quic_server: listens forever on --port (default 6121) until halted via ctrl-c.
masque_client: tunnels to a URL via an identified proxy (See RFC 9298).
Usage: masque_client [options] <proxy-url> <urls>
Usage: masque_server
web_transport_test_server: a server that clients can connect to via WebTransport.
moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.
Usage: moqt_relay
Most log messages in QUICHE use the QUICHE_DLOG macro. In standalone quiche, these all either go to stderr, or are suppressed, based on the --stderrthreshold flag.
To send INFO level log messages to a file, you would therefore invoke
<binary> <args> > <logfile> 2>&1
Use the --helpfull flag for more.