Configuration Book

Practical Use Case Configurations

This is a sketchbook for all useful configuration you may need.

Backend Mapping

To proxy a defined Listener to a specified Backend you need to setup the configuration as follow:

1. Add the Backend.
2. Add a Director that points to the backend.
3. Add an Action of type proxy or cache, depending on whether you want to cache static resources or not, and pointing to the director created above.
4. Add a Route to map each request that matches the matching condition specified to the defined action.

1. Backend setup

backend.1.id=localhost:8086 id to use in the Director definition
backend.1.enabled=true
backend.1.host=localhost
backend.1.port=8086
backend.1.probePath=/tomcatstatus/up path where the proxy looks up to check the backend reachability

2. Director setup

director.1.id=director1 id to use in the Action definition
director.1.backends=localhost:8086 set of comma-separated backends ids to direct to
director.1.enabled=true

3. Action setup

action.1.id=action1 id to use in the Route definition
action.1.type=cache type of the action (for all the available action types see here)
action.1.director=director1 id of the director to use
action.1.enabled=true

4. Route setup

route.1.id=route1
route.1.enabled=true
route.1.action=action1 id of the Action to perform
route.1.match= ~ ".*test.*" RegEx used for the request mapping (whether not specified the route will be match to every request. For a deeply understending of matchers see Matching Expression Language section)