ronutz

Ordine degli eventi iRule

Scegli lo stack di profili di un virtual server BIG-IP — Client-SSL, HTTP, Server-SSL, pool — e guarda l'ordine in cui scattano gli eventi iRule comuni, da CLIENT_ACCEPTED a CLIENT_CLOSED, come timeline ed elenco. Tutto nel tuo browser.

Reti
Documentation

Stack di profili del virtual server

Preset:

Calcolato nel tuo browser. Niente viene inviato.

Un modello del comportamento documentato di F5 per un virtual server Standard. Non contatta mai un BIG-IP.

Sequenza degli eventi

lato clientlato serverglobale
1CLIENT_ACCEPTEDConnection setup · lato client2CLIENTSSL_CLIENTHELLOClient-side TLS · lato client3CLIENTSSL_HANDSHAKEClient-side TLS · lato client4HTTP_REQUESTRequest · lato client5LB_SELECTEDLoad balancing · globale6SERVER_CONNECTEDServer-side setup · lato server7SERVERSSL_HANDSHAKEServer-side TLS · lato server8HTTP_REQUEST_SENDSend to server · lato server9HTTP_RESPONSEResponse · lato client10SERVER_CLOSEDTeardown · lato server11CLIENT_CLOSEDTeardown · lato client

Eventi in ordine

  1. CLIENT_ACCEPTEDlato 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_CLIENTHELLOlato client

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

  3. CLIENTSSL_HANDSHAKElato client

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTlato client

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

  5. LB_SELECTEDglobale

    The system has selected a pool member for the connection.

  6. SERVER_CONNECTEDlato server

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

  7. SERVERSSL_HANDSHAKElato server

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDlato server

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

  9. HTTP_RESPONSElato client

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

  10. SERVER_CLOSEDlato server

    The server-side connection has been closed.

  11. CLIENT_CLOSEDlato client

    The client-side connection has been closed.

Eventi condizionali

Questi scattano solo a condizioni specifiche: un TCP::collect o HTTP::collect, un fallimento del bilanciamento, o una risposta 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.

Riferimenti