disable irule process for the request not for the whole tcp connection

So you are expecting the following:

• client 1 --> http request1 --> F5 --> http request1 --> server
• client 1 --> http request2 --> F5 --> http request2 --> server
• client 1 --> http request3 --> F5 --> http request3 --> server
• client 1 <-- http request1 <-- F5 <-- http response1 <-- server
• client 1 <-- http request2 <-- F5 <-- http response2 <-- server
• client 1 <-- http request3 <-- F5 <-- http response3 <-- server

And you want to set a variable for http request 1 to use in http response 1 and not have http request 2 mess the variable up?

When pipelining is use http responses must be sent int request order that is using the above response 3 can not be sent before response 1 and 2 are sent.

Since variables are per connection what I would suggest is you number the variables. Something along the lines: Please note I have NOT tested this. If iRules (or TCL) had a FIFO stack/queue function you could use that and it would be easier. The only time I know there would be an issue is if a HTTP request and HTTP response were being processed at almost the same exact time.

    when CLIENT_ACCEPTED {
        set seq = 0
        }

    when HTTP_REQUEST {
       set $seq = $seq + 1
       set var.$seq = "to something"
       }

    when HTTP_RESPONSE {
    if {$seq = 1 } then {
        "do something with $var.$seq"
        $seq = 0
        }
    else {
        set invseq = 1
        "do something with $var.$invseq"
        while {$seq > 1} {
        set $prev = $invseq + 1
        set $var.$invseq = $var.$prev
        set $seq = $seq - 1
        }
    }
}