How to disable iRule processing on keep-alive per request when using HTTP::respond

I have an open case already.

 

C498394

 

The support guy is fantastic!

 

He hinted I try over here for a possible solution first.

 

Now I am back at the case trying to write out a feature request.

 

 

 

Can someone tell me how the iRule events are execute during a connection? Yes, I thought about what spark is suggesting, but I did not know if there was an event fired in between each HTTP_REQUEST event on the same connection.

 

 

So what is the firing order of events?

 

 

CLIENT_CONNECT

 

HTTP_REQUEST

 

HTTP_RESPONSE (ONLY if the response comes from a node)

 

HTTP_REQUEST

 

HTTP_REQUEST

 

... etc..

 

 

Is there an event in between successive HTTP_REQUEST events?

 

 

If there is, then my problem is easily solvable by disabling the event in HTTP_REQUEST, and reenabling the HTTP_REQUEST event inside the execution of another in between event.

 

 

I would not have a problem right now if using HTTP::respond also caused the execution of HTTP_RESPONSE event - because I could then just reenable the HTTP_REQUEST event inside the HTTP_RESPONSE event when sending the response back to the client.

 

 

-RG