Get desktop application:
View/edit binary Protocol Buffers messages
Describes how to match a header by name and value.
Used in: ,
Describes how to match an `:authority` or `host` header.
Used in: , , ,
Match an exact hostname, e.g. www.example.com.
Match a hostname as a wildcard suffix, e.g. *.example.com.
A match like `*.example.com` is encoded as [com, example].
Used in:
Configures a route to respond with a fixed response.
Used in: ,
The status code to use in the HTTP response. Must be specified.
An error message to log and include in the `l5d-proxy-err` header.
If specified, the rate of requests that should be failed. If not specified, ALL requests are failed.
Describes a set of matches, ALL of which must apply.
Used in: ,
Matches requests by path.
A set of header value matches that must be satisified. This match is not comprehensive, so requests may include headers that are not covered by this match.
A set of query parmaeter value matches that must be satisified. This match is not comprehensive, so requests may include query parameters that are not covered by this match.
If specified, restricts the match to a single HTTP method.
Describes how to match a path.
Used in:
Describes how a path value may be rewritten in a route.
Used in:
Indicates that the path should be replaced with the given value.
Indicates that the path prefix should be replaced with the given value. When used, the route MUST match the request with PathMatch prefix match. Server implementations SHOULD prevent the useof prefix modifiers on routes that do use a PathMatch prefix match. Proxyies MUST not process requests for routes where this condition is not satisfied.
Describes how to match a query parameter by name and value.
Used in:
A ratio (i.e., of requests) to which an filter should be applied. Represents fractional values on [0, 1].
Used in: ,
MUST not be zero.
Configures a route to modify a request's headers. Modifications are to be applied in the order they are described here: additions apply first, then sets, and then removals.
Used in: , , ,
A list of headers name-value pairs to set on requests, augmenting any existing values for the header.
A list of headers name-value pairs to set on requests, replacing any existing values for the header.
A list of headers names to be removed from requests.
Configures a route to respond with a redirect response. The `location` header is set with the given URL parameters.
Used in: ,
The scheme value to be used in the `location` header. If not specified, the original request's scheme is used.
The host value to be used in the `location` header. If not specified, the original request's host is used.
If set, configures how the request's path should be modified for use in the `location` header. If not specified, the original request's path is used.
If set, specifies the port to use in the `location` header.
The status code to use in the HTTP response. If not specified, 301 is used.
Configures a route to modify a response's headers. Modifications are to be applied in the order they are described here: additions apply first, then sets, and then removals.
Used in:
A list of headers name-value pairs to set on responses, augmenting any existing values for the header.
A list of headers name-value pairs to set on responses, replacing any existing values for the header.
A list of headers names to be removed from responses.
Used in: ,
Limits the the time a stream may be active after all request frames have been processed.
Limits the total duration of the stream from the request being initiated until all frames have been processed.
Limits the amount of time a stream may be idle (i.e. with no frames being processed).