Thanks a lot Thierry, that was it, changing to http-request solved my
issue.
I am now able to leverage a fully dynamic backend :)
Thanks
Sachin
On 7/21/16, 10:52 PM, "thierry.fourn...@arpalert.org"
wrote:
>On Tue, 19 Jul 2016 15:28:25 +0530
>Sachin Shetty
On Tue, 19 Jul 2016 15:28:25 +0530
Sachin Shetty wrote:
> Hi,
>
> We always had a unique requirement of picking a backend based on response
> from a external http service. In the past we have got this working by
> routing requests via a modified apache and caching the
uot;haproxy@formilux.org" <haproxy@formilux.org>
Subject: Dynamic backends decided by an external service
Hi,
We always had a unique requirement of picking a backend based on response
from a external http service. In the past we have got this working by
routing requests via a modif
Hi,
We always had a unique requirement of picking a backend based on response
from a external http service. In the past we have got this working by
routing requests via a modified apache and caching the headers in maps for
further request, but now I am trying to simplify our topology and trying
4 matches
Mail list logo