Showing results for 
Search instead for 
Did you mean: 

Catch date BEFORE it is sent to the server but after server TCP connection is opened

Historic F5 Account



I'm looking to do the following:


In USER_REQUEST event, i identify the TCP connection (SRC PORT+DEST IP) and combine this with information gathered in the CLIENT_DATA event to make a decision whether to send the packet to the server or not.


This methodology works to the point where i can at least identify the condition, but by then it is too late as the USER_REQUEST event fires AFTER the data is sent to the server.


I cant use the CLIENT_DATA event on its own, because at that stage the server-side connection information is not yet available.


Has anyone succeeded in modifiying or preventing data to be sent to the server once the TCP connection is initiated, but before the data is sent?




F5 Employee
F5 Employee
does TCP::respond in SERVER_CONNECTED event not usable?



this is an example by Richard.



TCP Data Payload split CodeShare

F5 Employee
F5 Employee
this is another example. TCP::collect is initially called in LB_SELECTED which will trigger CLIENT_DATA.



Oracle RAC Connection String Rewrite by Jason