Validate that received GOAWAY last-stream-ID fields are non-increasing in oghttp2.

This CL is a follow-up to a comment in cl/439588951 about enforcing this
section of the specification:

"An endpoint MAY send multiple GOAWAY frames if circumstances change. [...]
Endpoints MUST NOT increase the value they send in the last stream identifier,
since the peers might already have retried unprocessed requests on another
connection." (From https://httpwg.org/specs/rfc7540.html#GOAWAY)

This CL updates OgHttp2Session to follow this part of the specification, which
also increases parity with nghttp2 behavior:
http://google3/third_party/nghttp2/src/lib/nghttp2_session.c;l=4730-4738;rcl=439727518

PiperOrigin-RevId: 441023801
5 files changed
tree: 399153c8b96648b82d9023feb9e9b17eee09bfe0
  1. quiche/
  2. CONTRIBUTING.md
  3. LICENSE
  4. README.md
README.md

QUICHE

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.