[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)

data-plane-api(Azure Pipelines) 323a64b103 aws_request_signing_filter hash payload by default (#15846 ) canonical must include the hashed payload for most services. The prior behavior of using UNSIGNED-PAYLOAD is an exception to the rule, which select services like s3 support, since hashing the payload may be impractical if the payload is very large. A new filter option is introduced, so that the filter may be explicitly configured to use the UNSIGNED-PAYLOAD string literal as specified in the S3 signing docs: https://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html fixes #13904 Additional Description: The original implementation was seemingly very specific to S3 and was subsequently amended to extend the same niche singing behaviors for ES and Glacier. This changes the filter's default behavior to match the general SigV4 guidelines while providing a configuration option to enable the specialized UNSIGNED-PAYLOAD behavior. https://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html Risk Level: Medium? Deployments using the filter will now buffer requests by default, which could result in 413 responses for requests with bodies exceeding the buffer limit. These users can mitigate buffering by enabling the `unsigned_payload` option. Testing: I tested locally with a filter config. I anticipate updating the automated tests based on feedback from maintainers. Docs Changes: Added Signed-off-by: Jonathan Stewmon <jstewmon@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 80e1ca899e3170c8f87dfd300c9c5dacc76d100b		4 years ago
.circleci	ci: remove docs/format jobs. (#619 )	7 years ago
bazel	api: fix go importpath for OT dep (#15825 )	4 years ago
ci	ci: remove docs/format jobs. (#619 )	7 years ago
envoy	aws_request_signing_filter hash payload by default (#15846 )	4 years ago
examples/service_envoy	Add license declarations to some BUILD files. (#223 )	7 years ago
test	deps: update protobuf to 3.14 (#14253 )	4 years ago
tools	deps: Resolve conflicting python updates (#15703 )	4 years ago
versioning	protos: Move simple_http_cache config proto to api (#16230 )	4 years ago
.clang-format	adding check_format and fix_format (#300 )	7 years ago
.gitignore	validate: initial constraints support. (#226 )	7 years ago
API_VERSIONING.md	xds: Cleanup udpa -> xds refs (#15513 )	4 years ago
BUILD	protos: Readd v2 legacy protos in v3 (#16338 )	4 years ago
CONTRIBUTING.md	docs: Improve style for inline literals and update contrib guidance (#16194 )	4 years ago
LICENSE	Add Apache 2.0 LICENSE file. (#21 )	8 years ago
README.md	Docs: replace broken link in api/README.md (#15423 )	4 years ago
STYLE.md	protos: Update style guide to try and prevent redundant imports (#16231 )	4 years ago
review_checklist.md	repo: Update references - master -> main (#15190 )	4 years ago

README.md

Data plane API

This tree hosts the configuration and APIs that drive Envoy. The APIs are also in some cases used by other proxy solutions that aim to interoperate with management systems and configuration generators that are built against this standard. Thus, we consider these a set of universal data plane APIs. See this blog post for more information on the universal data plane concept.

Repository structure

The API tree can be found at two locations:

https://github.com/envoyproxy/envoy/tree/main/api - canonical read/write home for the APIs.
https://github.com/envoyproxy/data-plane-api - read-only mirror of https://github.com/envoyproxy/envoy/tree/main/api, providing the ability to consume the data plane APIs without the Envoy implementation.

README.md

Data plane API

Repository structure

Further API reading