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

James_Wrubel_48's avatar
James_Wrubel_48
Icon for Nimbostratus rankNimbostratus
Jun 27, 2009

forware only http payload to pool

Hi all,     I've got a requirement to tunnel a TCP-based application over HTTP. We control the data the client sends, so I had intended to put the node and port in custom http headers and t...
application delivery
dev
devops
iRules
James_Wrubel_48's avatar
James_Wrubel_48
Icon for Nimbostratus rankNimbostratus
Jul 02, 2009
I got stuck along the way - I couldn't get variables set in HTTP_REQUEST to show up in CLIENT_DATA. I assume that's either because doing the equivalent of a 'wait' statement is not possible or a bad idea, or because the F5 processes the TCP stream before the higher order HTTP. I have put that on the shelf for a while and am doing my own HTTP parsing (sigh) in CLIENT_DATA: 

 Only get the info before the HTTP headers 
 set myURI [getfield $cdata "HTTP" 1] 
  
  now trim off everything before the ? so we just have the querystring parameters 
 set myQS [getfield $myURI "?" 2] 
  
     log local0.info "uri = $myURI" 
 log local0.info "qs = $myQS"

There's probably a way to optimize these two queries to run this in one command - I figure I'll get to this later. Now that I have the QS I'm able to parse out on the "=" and use a switch statement to dig in to the individual parameters. Seems to be working so far but I need to put it all together.

Jim