Forum Discussion
8 Replies
Sort By
- Frederic_Zelle2NimbostratusHi
- bl0ndie_127134Historic F5 AccountPlease also check this post. BTW, the problem mentioned on that thread has already been fixed and will be available on the release (v9.4) which should be coming out soon. Click here
- hooleylistCirrostratusIs there any reason to not just use the fallback host option in the HTTP profile?
- Siddharth_SezhiNimbostratusLB Failed option wil redirect to a new pool if the LB couldnt get to the pool. My requirement says that when the httpd daemon stops running the server or the servers in the pool are down due to outage the client accessing the webpage will get error 404 "webpage not found" instead of getting this page client wanted to redirect a direct webpage given by them. I finally figured a solution but have no idea whether it wil work awaiting for customer approval to implement and check.
- rick_masselle_1NimbostratusI am running 9.1.2 and I am trying to accomplish similiar redirect.
- rick_masselle_1NimbostratusIt seems when I used fallback host that it triigered when any node was unreachable ( not down)eg. server wa sbusy etc. I only want the redirection when all nodes in pool are down.
- Colin_Walker_12Historic F5 AccountGotcha. Thanks for following up.
- Eric_Grepps_264NimbostratusI am having the same issue, except I am redirecting many applications across many virtual servers.
when RULE_INIT { set down_response " } when HTTP_REQUEST { switch [getfield [string tolower [HTTP::uri]] "/" 2] { app1 { if { [active_members p1] < 1 } { HTTP::respond $down_response } else { pool p1 } app2 { if { [active_members p2] < 1 } { HTTP::respond $down_response } else { pool p2 } ... appN { if { [active_members pN] < 1 } { HTTP::respond $down_response } else { pool p1 } default { pool p_default } } }