tree a9adbb84d1907062cc807428e4fd7feda619086d
parent 8da3bbb0b08b151d410de69a6fbe73b1974a044e
author QUICHE team <quiche-dev@google.com> 1725390274 -0700
committer Copybara-Service <copybara-worker@google.com> 1725390332 -0700

Add a new message status for sending HTTP Datagrams before SETTINGS are received.

Previously, `QuicSpdySession::SendHttp3Datagram` returned `MESSAGE_STATUS_INTERNAL_ERROR` if it was called before a SETTINGS frame was received. In this CL, I added a new enum called `MESSAGE_STATUS_SETTINGS_NOT_RECEIVED` to distinguish this case from other internal errors. This will allow a caller to take proper measures (e.g., drop or buffer datagrams) based on the return value of the method.

In QUICHE, callers report errors or log the `MESSAGE_STATUS_INTERNAL_ERROR`, so I added the `MESSAGE_STATUS_SETTINGS_NOT_RECEIVED` case in the callers to preserve the existing behavior.

In Envoy, `HttpDatagramHandler` is the only caller of the method. This change will not alter its behavior since both message statuses will be treated the same and reset the stream.

In Chromium, `QuicChromiumClientStream::Handle::WriteConnectUdpPayload()` treats both message statuses the same, so this CL will not change its behavior. After this CL is landed, the caller no longer needs to check `stream_->SupportsH3Datagram()` and instead can treat `MESSAGE_STATUS_SETTINGS_NOT_RECEIVED` the same way it treats `MESSAGE_STATUS_BLOCKED`.

PiperOrigin-RevId: 670652644