Imagine, or recall, a scenario. You integrate three applications, two client HTTP ones and the third is a backend one (no matter the technology).

All is well except client1 tends to send requests in bursts for no good reason and its developers just cannot tame it.

The backend app can’t deal with it, they prefer a steady inflow of messages, and you’re tasked with containing the issue.

In that situation you can take advantage of the fact that Zato uses an embedded instance of HAProxy as its load-balancer through which HTTP apps connect so you can fire up the GUI in config’s source code view and add these lines to ‘frontend front_http_plain’

{% gist 5872245 %}

so the whole of if reads now:

{% gist 5872259 %}

The GUI can be now used to validate and save the config:


There’s a couple of assumptions

  • Instead of HAProxy 1.4, you use 1.5 (or later, but this is the latest version as of the time of this writing)
  • Each client accesses URLs beginning with a client-specific prefix - but this is a good idea anyway