ltm rule event CLIENT DATA

iRule(1)		      BIG-IP TMSH Manual		      iRule(1)



CLIENT_DATA
       Triggered each time new data is received from the client while the
       connection is in "collect" state.

DESCRIPTION
       For TCP, this event is triggered when new data is received from the
       target node after TCP::collect command has been issued. For UDP, this
       event fires on receipt of each segment from the client.

       NOTE: Per F5 Solution SOL14563 it is better to process UDP data in
       CLIENT_ACCEPTED than in this event.

Examples
	when CLIENT_DATA {
	  if { [UDP::payload 50] contains "XYZ" } {
	    pool xyz_servers
	    persist uie "[IP::client_addr]:[UDP::client_port]" 300
	  }
	}

HINTS
       For UDP, the load-balancing decision cannot be changed in the
       CLIENT_DATA event. Commands that change the load-balancing decision
       will not have an effect. Instead the CLIENT_ACCEPTED event is
       recommended.

SEE ALSO
CHANGE LOG
       @BIGIP-9.0.0 --First introduced the event.



BIG-IP				  2017-01-31			      iRule(1)