package envoy.extensions.http.custom_response.redirect_policy.v3

Get desktop application:
View/edit binary Protocol Buffers messages

Custom response policy to internally redirect the original response to a different upstream. [#next-free-field: 7]

• oneof redirect_action_specifier

  • string uri = 1

    The Http URI to redirect the original request to, to get the custom response. It should be a full FQDN with protocol, host and path. Example: .. code-block:: yaml uri: https://www.mydomain.com/path/to/404.txt

  • config.route.v3.RedirectAction redirect_action = 2

    Specify elements of the redirect url individually. Note: Do not specify the ``response_code`` field in ``redirect_action``, use ``status_code`` instead. The following fields in ``redirect_action`` are currently not supported, and specifying them will cause the config to be rejected: - ``prefix_rewrite`` - ``regex_rewrite``

• optional google.protobuf.UInt32Value status_code = 3

  The new response status code if specified. This is used to override the status code of the response from the new upstream if it is not an error status.

• repeated config.core.v3.HeaderValueOption response_headers_to_add = 4

  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. Note that these are not applied if the redirected response is an error response.

• repeated config.core.v3.HeaderValueOption request_headers_to_add = 5

  HTTP headers to add to the request before it is internally redirected.

• optional config.core.v3.TypedExtensionConfig modify_request_headers_action = 6

  Custom action to modify request headers before selection of the redirected route. [#comment: TODO(pradeepcrao) add an extension category.]