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

jiseruk_43901's avatar
jiseruk_43901
Icon for Nimbostratus rankNimbostratus
Nov 14, 2013

Disable pool member when using HTTP/1.1

Hi. We are using HTTP/1.1 from the client to the backends servers. When I disable a member from a pool, it`s still receive requests thru the active connections and there`s no way I can´t stop it unt...
devops
iControl
management
Andy_Litzinger's avatar
Andy_Litzinger
Nov 15, 2013

i'm not sure i totally understand your question. can you post your iRule? I think you should be using the HTTP_REQUEST method to trigger the LB::detach. check out this SOL article http://support.f5.com/kb/en-us/solutions/public/7000/900/sol7964.html . It is geared toward persistence, but i think it should apply in your case too. you want this behavior for all connections, not just persistent ones so i think your iRule would simple be:

when HTTP_REQUEST {
  LB::detach
}

By far the simpler route would be to use OneConnect though. is that something you are able to test?