Makes the `FLAGS_` prefix implicit in calls to `GetQuicFlag()`.

This refactoring will allow us to define separate sets of flags for QUICHE in google3 vs //third_party/envoy/external_quiche. This will be necessary to import upstream Envoy PR [#22907](

CL automatically created by:
    replace_string \
      'GetQuicFlag\(FLAGS_' \

    replace_string \
      'SetQuicFlag\(FLAGS_' \

  $ blaze test //third_party/quic/core/... //gfe/gfe2/quic:all //net/quic/... //third_party/castlite/agent/net/... //video/streaming/quic:all
PiperOrigin-RevId: 473802782
51 files changed
tree: b2bb88f0cb5d7bb462344fa473bc181ac7bee521
  1. build/
  2. quiche/
  3. .bazelrc
  4. BUILD.bazel
  9. WORKSPACE.bazel


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

QUICHE is only supported on little-endian platforms.