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

isspwk_39034's avatar
isspwk_39034
Icon for Nimbostratus rankNimbostratus
Aug 12, 2009

http_request and lb-selected event

I was experimenting F5 LTM using http_request and lb_selected events.   I noticed that lb_selected event may not occur for each http_request event.   Can you clarify what lb_selected event d...
application delivery
dev
devops
iRules
L4L7_53191's avatar
L4L7_53191
Icon for Nimbostratus rankNimbostratus
Aug 12, 2009
You should be able to fire LB_SELECTED each time an HTTP request comes in. This rule: 

 
  
 when HTTP_REQUEST { 
  
 log local0. "caught http request!" 
  
 } 
  
 when LB_SELECTED { 
  
 log local0. "caught LB_SELECTED!" 
  
 }

Produces:

Jul 28 02:12:17 local/tmm info tmm[2160]: Rule event-test : caught http request!

Jul 28 02:12:17 local/tmm info tmm[2160]: Rule event-test : caught LB_SELECTED!

Jul 28 02:12:18 local/tmm info tmm[2160]: Rule event-test : caught http request!

Jul 28 02:12:18 local/tmm info tmm[2160]: Rule event-test : caught LB_SELECTED!

Jul 28 02:12:18 local/tmm info tmm[2160]: Rule event-test : caught http request!

For each request. I had an old setup and browser session established that caused me some confusing results initially, so chances are good you've got something similar going on.

-Matt