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

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tag: Branch: Tree: 0ef64fe10a

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '0ef64fe10a'

${ noResults }

data-plane-api/envoy

History

data-plane-api(CircleCI) 0ef64fe10a docs: clarity around http filter ordering (#11057) ... I still had an arcane mental model (pre https://github.com/envoyproxy/envoy/pull/5955) where both decoder and encoder filters where invoked in the same order as the configuration order. My mind was so used to this I even failed to notice the code that prepends encoder filters into the encoder_filters_ list in the conn manager. These documentation additions are trying to make the behavior as explicit as possible so others are not confused. Risk Level: low - doc updates, no behavior change. Docs Changes: updated inline comments in the code I failed to notice, and in the project docs. Signed-off-by: Jose Nino <jnino@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 4abe685446316f79ba1627cf830f0c0d398abdaf		5 years ago
..
admin	api: GoogleRE2 max_program_size should be checked by server, not client. (#10971)	5 years ago
annotations	docs: force all API protos to have a title (#9744)	5 years ago
api/v2	http: max stream duration upstream support (#10531)	5 years ago
config	docs: clarity around http filter ordering (#11057)	5 years ago
data	http: max stream duration upstream support (#10531)	5 years ago
extensions	docs: clarity around http filter ordering (#11057)	5 years ago
service	api: GoogleRE2 max_program_size should be checked by server, not client. (#10971)	5 years ago
type	api: GoogleRE2 max_program_size should be checked by server, not client. (#10971)	5 years ago