Flip restart flags for staging and gfe-dev-co production locations.

Also changes the default value in tests that do not specify values for these flags.

gfe2_restart_flag_blackhole_duplicate_vips
When the same VIP is present more than once in the cloud config, treat the config as valid but blackhole traffic to that VIP.

gfe2_restart_flag_cwc_invalidation_at_mc_experiment
Additionally send lookups to the next cache layer (aka MediumCache) after hits in the GFE in-memory cache every --gfe2_in_memory_to_mc_invalidation_checks_experiment_ttl to simulate the extra load created by pushing invalidation rules to MediumCache rather than the GFE (see b/238182160).

gfe2_restart_flag_quic_map_original_connection_ids
Store original QUIC connection IDs in the dispatcher's map

PiperOrigin-RevId: 462146028
1 file changed
tree: d5f3e8b136271665a8f090ccb9dfb75b89863f5a
  1. build/
  2. quiche/
  3. .bazelrc
  4. BUILD.bazel
  5. CONTRIBUTING.md
  6. LICENSE
  7. README.md
  8. WHITESPACE
  9. WORKSPACE.bazel
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.