Order of operations

Hi Nando,

 

 

HTTP_REQUEST will always be followed by either HTTP_CLASS_SELECTED or HTTP_CLASS_FAILED if you have at least one HTTP class configured on the virtual server:

 

 

CLIENT_ACCEPTED

 

CLIENTSSL_HANDSHAKE

 

CLIENTSSL_CLIENTCERT

 

HTTP_REQUEST / CACHE_REQUEST / RTSP_REQUEST / SIP_REQUEST /

 

HTTP_CLASS_FAILED / HTTP_CLASS_SELECTED

 

STREAM_MATCHED

 

CACHE_UPDATE

 

CLIENT_DATA / RTSP_REQUEST_DATA / HTTP_REQUEST_DATA – Only occur when collected data arrives

 

AUTH_RESULT / AUTH_WANTCREDENTIAL – Only occur when authentication commands return

 

LB_SELECTED / LB_FAILED / PERSIST_DOWN

 

 

 

...ASM HTTPClass is matching the uri "/abc" and I have an irule with the event "HTTP_REQUEST" matching the uri "/abc"... how would the LTM process this?

 

 

 

If you're selecting a pool in the HTTP_REQUEST iRule event and selecting a pool with an HTTP class, the HTTP class pool selection will override any prior pool selection.

 

 

If that's not what you're referring to, can you clarify the scenario you're thinking of?

 

 

Thanks, Aaron