Navigation :
Concepts
Setting up Gloo Mesh Enterprise
Guides overview
Operations
Reference
-
API reference
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
-- access_logging.proto
-- access_logging.proto
-- access_policy.proto
-- applied_policies.proto
-- ca_options.proto
-- certificate_request.proto
-- certificate_verification.proto
-- csrf.proto
-- dashboard.proto
-- destination.proto
-- extauth.proto
-- issued_certificate.proto
-- istio_installation.proto
-- istio_installation_instance.proto
-- keepalive.proto
-- mesh.proto
-- metrics.proto
-- networking_extensions.proto
-- pod_bounce_directive.proto
-- rate_limit.proto
-- rate_limit_client_config.proto
-- rate_limit_server_config.proto
-- request_matchers.proto
-- role.proto
-- route.proto
-- route_table.proto
-- selectors.proto
-- service_dependency.proto
-- settings.proto
-- status.proto
-- status.proto
-- string_match.proto
-- traffic_policy.proto
-- transformation.proto
-- vault_ca.proto
-- virtual_destination.proto
-- virtual_gateway.proto
-- virtual_host.proto
-- virtual_mesh.proto
-- wasm_deployment.proto
-- weighed_destination.proto
-- workload.proto
-- xds_config.proto
-
CLI reference
-
Helm value reference
- Registered ClusterRole Definition
-
Version reference
- Gloo Mesh Enterprise changelog
-
Gloo Mesh Security and CVE report
Support and services
Package : envoy.type.v3
Top
http.proto
Table of Contents
CodecClientType
Name
Number
Description
HTTP1
0
HTTP2
1
HTTP3
2
[#not-implemented-hide:] QUIC implementation is not production ready yet. Use this enum with caution to prevent accidental execution of QUIC code. I.e. != HTTP2 is no longer sufficient to distinguish HTTP1 and HTTP2 traffic.
