Local Response Policy for Custom Response (proto)
This extension has the qualified name envoy.http.custom_response.local_response_policy
Note
This extension is work-in-progress. Functionality is incomplete and it is not intended for production use.
This extension has an unknown security posture and should only be used in deployments where both the downstream and upstream are trusted.
Tip
This extension extends and can be used with the following extension category:
This extension must be configured with one of the following type URLs:
Warning
This API feature is currently work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
extensions.http.custom_response.local_response_policy.v3.LocalResponsePolicy
[extensions.http.custom_response.local_response_policy.v3.LocalResponsePolicy proto]
Custom response policy to serve a locally stored response to the downstream.
{
"body": {...},
"body_format": {...},
"status_code": {...},
"response_headers_to_add": []
}
- body
(config.core.v3.DataSource) Optional new local reply body text. It will be used in the %LOCAL_REPLY_BODY% command operator in the body_format.
- body_format
(config.core.v3.SubstitutionFormatString) Optional body format to be used for this response. If body_format is not provided, and body is, the contents of body will be used to populate the body of the local reply without formatting.
- status_code
(UInt32Value) The new response status code if specified.
- response_headers_to_add
(repeated config.core.v3.HeaderValueOption) HTTP headers to add to the response. This allows the response policy to append, to add or to override headers of the original response for local body, or the custom response from the remote body, before it is sent to a downstream client.