Re: Question about timeout

Hi,

You need to split your configuration in frontend/backend. Then you can do content swithing based on header or prefix, depending on how you can detect a user has a session.

So let us know how you check whether a user has a session or not, then we can help you with the configuration.

cheers

On Mon, Nov 7, 2011 at 9:46 AM, Christophe Rahier <christophe#qualifio.com> wrote:
> Hi,
> Here's a part of my config file :
> --> CUT <--
> global
> log 192.168.0.2 local0
> log 127.0.0.1 local1 notice
> maxconn     10240
> defaults
> log    global
> option dontlognull
> retries    2
> timeout client 35s
> timeout server 90s
> timeout connect 5s
> timeout http-keep-alive 10s
> listen WebPlayer-Farm 192.168.0.2:80
> mode http
> option httplog
> balance source
> #balance leastconn
> option forwardfor
> stats enable
> option http-server-close
> server Player4 192.168.0.13:80 check
> server Player3 192.168.0.12:80 check
> server Player1 192.168.0.10:80 check
> server Player2 192.168.0.11:80 check
> server Player5 192.168.0.14:80 check
> option httpchk HEAD /cfadmin/ping.cfm HTTP/1.0
> --> CUT <--
> I've put 5 web servers.
> I want users who have a session to be redirected to another server.
>
> For now, it does not work, they receive an error message.
>
> What should I adjust?
> Thanks for your help.
> Regards,
> Christophe
Received on 2011/11/07 10:32