> Thank you very much, Igor.
> Indeed, your suggestion solves most of the cases where I encounter
> the
> switch-over of the backend hosts.
> However, this does *not* help in all cases, as this works only if the
> backend is no more reachable and thus an error condition occurs.
> Sometimes
> I jus
>
> Would it be a viable option for you to not use the DNS method, and
> instead do something like:
>
>
> BalanceMember https://backend1.mydomain.com:8080/
> BalanceMember https://backend1.mydomain.com:8080/ status=+H
>
>
> ProxyPass / balancer://notsohotcluster
> ProxyPassReverse / balancer:
- "Slawomir R. Janotta" wrote:
> Hi everybody,
> I am facing a problem which I cannot solve in a satisfying way and
> after
> searching the known resources for a while I wonder if anyone has ever
> solved a similiar one.
>
> Let me first describe the situation I have here.
>
> I am using a
Hi everybody,
I am facing a problem which I cannot solve in a satisfying way and after
searching the known resources for a while I wonder if anyone has ever
solved a similiar one.
Let me first describe the situation I have here.
I am using a reverse proxy installation to access a backend server
t
