[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: 32bdf0bffc

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '32bdf0bffc'

${ noResults }

data-plane-api/envoy/service/ext_proc/v3

History

data-plane-api(Azure Pipelines) b04bdcbb5b api docs: improve wording of ext_proc ImmediateResponse.Details field (#19813) ... I had been trying to figure out a good way to provide more internally-derived feedback from an *ext_proc* implementation to *envoy* (without needing to do things like set response headers or rely on a separate log file), and was led to the discovery that the `ImmediateResponse.Details` field actually populates `%RESPONSE_CODE_DETAILS%` for use in access logging. Due to how much better this discovery made my life, I am hoping it will make other people's lives better as well. Signed-off-by: Chet Nichols III <chet@apple.com> Mirrored from https://github.com/envoyproxy/envoy @ e00aa66429181e3973cc69ca57c26da730cc47af		3 years ago
..
BUILD	api: force migrate v3alpha -> v3 (#18392)	3 years ago
external_processor.proto	api docs: improve wording of ext_proc ImmediateResponse.Details field (#19813)	3 years ago