ronutz

Ordre des événements iRule

Choisissez la pile de profils d'un virtual server BIG-IP — Client-SSL, HTTP, Server-SSL, pool — et voyez l'ordre dans lequel les événements iRule courants se déclenchent, de CLIENT_ACCEPTED à CLIENT_CLOSED, sous forme de chronologie et de liste. Le tout dans votre navigateur.

Réseau
Documentation

Pile de profils du virtual server

Préréglages :

Calculé dans votre navigateur. Rien n'est envoyé.

Un modèle du comportement F5 documenté pour un virtual server Standard. Il ne contacte jamais de BIG-IP.

Séquence d'événements

côté clientcôté serveurglobal
1CLIENT_ACCEPTEDConnection setup · côté client2CLIENTSSL_CLIENTHELLOClient-side TLS · côté client3CLIENTSSL_HANDSHAKEClient-side TLS · côté client4HTTP_REQUESTRequest · côté client5LB_SELECTEDLoad balancing · global6SERVER_CONNECTEDServer-side setup · côté serveur7SERVERSSL_HANDSHAKEServer-side TLS · côté serveur8HTTP_REQUEST_SENDSend to server · côté serveur9HTTP_RESPONSEResponse · côté client10SERVER_CLOSEDTeardown · côté serveur11CLIENT_CLOSEDTeardown · côté client

Événements dans l'ordre

  1. CLIENT_ACCEPTEDcôté client

    A client connection is established. On a Standard virtual server this is when the TCP three-way handshake completes; on FastL4 it fires on the initial SYN.

  2. CLIENTSSL_CLIENTHELLOcôté client

    The client's TLS ClientHello has been received, before the handshake is processed. Useful for SNI-based decisions.

  3. CLIENTSSL_HANDSHAKEcôté client

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTcôté client

    The system has fully parsed the complete client HTTP request headers.

  5. LB_SELECTEDglobal

    The system has selected a pool member for the connection.

  6. SERVER_CONNECTEDcôté serveur

    The server-side connection to the selected pool member has been established.

  7. SERVERSSL_HANDSHAKEcôté serveur

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDcôté serveur

    Immediately before the HTTP request is sent to the server-side TCP stack. Runs in the server-side context.

  9. HTTP_RESPONSEcôté client

    The system has parsed all of the response status and header lines from the server response.

  10. SERVER_CLOSEDcôté serveur

    The server-side connection has been closed.

  11. CLIENT_CLOSEDcôté client

    The client-side connection has been closed.

Événements conditionnels

Ceux-ci ne se déclenchent que dans des conditions précises : un TCP::collect ou HTTP::collect, un échec de répartition, ou une réponse 100 Continue.

  • HTTP_REQUEST_DATA↪ HTTP_REQUEST

    After an HTTP::collect has gathered the specified amount of request payload.

  • LB_FAILED↪ LB_SELECTED

    Instead of LB_SELECTED, when the system fails to select a pool or member, or the selected resource is unreachable.

  • HTTP_RESPONSE_CONTINUE↪ HTTP_RESPONSE

    Before HTTP_RESPONSE, whenever the server sends a 100 Continue interim response.

  • HTTP_RESPONSE_DATA↪ HTTP_RESPONSE

    After an HTTP::collect has gathered the specified amount of response payload.

  • Within a single event, multiple iRules run by priority (default 500, lowest number first); the priority command overrides that. This ordering is across events, not within one.
  • Availability also depends on provisioning: module events (APM ACCESS_*, ASM/Advanced WAF, bot defense) only fire when that module is provisioned. And CLIENT_DATA, SERVER_DATA, HTTP_REQUEST_DATA, and HTTP_RESPONSE_DATA need an explicit TCP::collect or HTTP::collect first.
API endpointGEThttps://ronutz.com/api/v1/f5-irules-event-orderDocumented, not served. Opens the specification.

Références