For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

IheartF5_45022's avatar
IheartF5_45022
Icon for Nacreous rankNacreous
Oct 29, 2015

If you want to issue a clientside redirect try this (I use HTTP::respond as I like to use 301, and also like to use 'noserver' to hid the Server:BigIP header).

HTTP_REQUEST { 
    Check the requested path with wildcard matching  
   switch -glob [HTTP::path] { 
      "site1/online/index.html"{ 
          301 Redirect 
         HTTP::respond 301 noserver Location "/online" 
         return
      } 
      "online/"{ 
         pool 1.1.1.1 
      } 
   }
}
johtte_168100's avatar
johtte_168100
Icon for Nimbostratus rankNimbostratus
Oct 29, 2015
Hi, thanks for this another idea. but if we check later the same url but redirect to another pool for example First request -> site1/online/index.html, after that change the path to /online/ redirect to pool 1.1.1.1 Second request -> site1/online/authenticate.html ->change the path to /online redirect to pool 2.2.2.2 when HTTP_REQUEST { Check the requested path with wildcard matching switch -glob [HTTP::path] { "/site1/online" { HTTP::respond 302 noserver Location "/online" return } "/online" { pool 1.1.1.1 } } switch -glob [HTTP::uri] { "/site1/online/authenticate.html" { HTTP::respond 302 noserver Location "/online" return } "/online"{ pool 2.2.2.2 } } } Something like this? Thanks for your help