ronutz

iRule-Ereignisreihenfolge

Wählen Sie den Profil-Stack eines BIG-IP-Virtual-Servers — Client-SSL, HTTP, Server-SSL, Pool — und sehen Sie die Reihenfolge, in der die gängigen iRule-Ereignisse auslösen, von CLIENT_ACCEPTED bis CLIENT_CLOSED, als Zeitachse und Liste. Alles im Browser.

Netzwerk
Documentation

Profil-Stack des Virtual Servers

Vorlagen:

Im Browser berechnet. Es wird nichts gesendet.

Ein Modell des dokumentierten F5-Verhaltens für einen Standard-Virtual-Server. Es kontaktiert nie ein BIG-IP.

Ereignisablauf

Client-SeiteServer-Seiteglobal
1CLIENT_ACCEPTEDConnection setup · Client-Seite2CLIENTSSL_CLIENTHELLOClient-side TLS · Client-Seite3CLIENTSSL_HANDSHAKEClient-side TLS · Client-Seite4HTTP_REQUESTRequest · Client-Seite5LB_SELECTEDLoad balancing · global6SERVER_CONNECTEDServer-side setup · Server-Seite7SERVERSSL_HANDSHAKEServer-side TLS · Server-Seite8HTTP_REQUEST_SENDSend to server · Server-Seite9HTTP_RESPONSEResponse · Client-Seite10SERVER_CLOSEDTeardown · Server-Seite11CLIENT_CLOSEDTeardown · Client-Seite

Ereignisse in Reihenfolge

  1. CLIENT_ACCEPTEDClient-Seite

    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_CLIENTHELLOClient-Seite

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

  3. CLIENTSSL_HANDSHAKEClient-Seite

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTClient-Seite

    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_CONNECTEDServer-Seite

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

  7. SERVERSSL_HANDSHAKEServer-Seite

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDServer-Seite

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

  9. HTTP_RESPONSEClient-Seite

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

  10. SERVER_CLOSEDServer-Seite

    The server-side connection has been closed.

  11. CLIENT_CLOSEDClient-Seite

    The client-side connection has been closed.

Bedingte Ereignisse

Diese lösen nur unter bestimmten Bedingungen aus: ein TCP::collect oder HTTP::collect, ein Fehler bei der Lastverteilung oder eine 100-Continue-Antwort.

  • 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.

Referenzen