Top level element for defining a power proxy system model Defines a single service cluster in the system model. A service cluster is a collection of nodes that provide equivalent functionality. If a service cluster represents a repose cluster, then it will contain a filter list and a destination list. Defines the service cluster's id which may be referenced elsewhere in various configuration files Defines a single service cluster in the system model. A service cluster is a collection of nodes that provide equivalent functionality. If a service cluster represents a repose cluster, then it will contain a filter list and a destination list. Determines whether or not repose nodes in this cluster rewrite the HOST header to contain the host and port of the origin service. If true, repose will rewrite the HOST header. If false, repose will pass whatever value is received on as the value for the HOST header. If present, enables the phone home service which will collect Repose usage data and send it to a centralized data collection service. If not present, will have no effect. Allows you to configure the tracing header. If not present, feature will be enabled by default. Determines whether or not you'd like the uuid contained within the tracing header to be written out in plain text in the additional header x-request-id. Defines a list of nodes within a cluster Defines a single host in the system model Defines the proxy's id which will be referenced elsewhere in different configs Hostname of the node this proxy model defines. This will be used for personality matching when the proxy is started Port number of the http service of the host. If the port is 0, then Repose will not listen to the HTTP port at all. Port number of the https service of the host. If port is 0, then Repose will not listen to HTTPs port at all. List of filters that the proxy will then execute in order of definition A regex that will be used to determine what requests will bypass the filter chain. Useful for doing health checks on the underlying origin service. Defines a filter that can be used to process and route requests Defines the filters id The system context specific name of the filter module to be loaded The system context specific name of the filter's configuration Regex of what uri is allowed access. List of services that the proxy will then execute in order of definition Defines a service that can be used to assist filters The system context specific name of the service to be used Defines a list of target destinations reachable from a cluster Defines the endpoint's id which will be referenced elsewhere in different configs Defines the endpoint's protocol. Current protocols permitted are http and https. If the protocol is not specified then internal dispatch is assumed. Defines the endpoint's base path element. This will be used in building the URI/path for connecting to the service. Any additional URI info will be appended to this. Defines a single node that is a target destination reachable from a cluster Defines the endpoint's host name. Optional. If not specified, localhost is assumed. Defines the endpoint's port. Optional. If not specified (or 0), internal dispatch is assumed. Defines a single node that is a target destination reachable from a cluster Defines the destination cluster. Repose will choose a host from this cluster to handle a request.