ronutz

iRule-händelseordning

Välj profilstacken på en BIG-IP-virtuell server — Client-SSL, HTTP, Server-SSL, pool — och se ordningen som de vanliga iRule-händelserna utlöses i, från CLIENT_ACCEPTED till CLIENT_CLOSED, som tidslinje och lista. Allt i din webbläsare.

Nätverk
Documentation

Den virtuella serverns profilstack

Förinställningar:

Beräknat i din webbläsare. Inget skickas någonstans.

En modell av dokumenterat F5-beteende för en Standard-virtuell server. Den kontaktar aldrig en BIG-IP.

Händelsesekvens

klientsidanserversidanglobalt
1CLIENT_ACCEPTEDConnection setup · klientsidan2CLIENTSSL_CLIENTHELLOClient-side TLS · klientsidan3CLIENTSSL_HANDSHAKEClient-side TLS · klientsidan4HTTP_REQUESTRequest · klientsidan5LB_SELECTEDLoad balancing · globalt6SERVER_CONNECTEDServer-side setup · serversidan7SERVERSSL_HANDSHAKEServer-side TLS · serversidan8HTTP_REQUEST_SENDSend to server · serversidan9HTTP_RESPONSEResponse · klientsidan10SERVER_CLOSEDTeardown · serversidan11CLIENT_CLOSEDTeardown · klientsidan

Händelser i ordning

  1. CLIENT_ACCEPTEDklientsidan

    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_CLIENTHELLOklientsidan

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

  3. CLIENTSSL_HANDSHAKEklientsidan

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTklientsidan

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

  5. LB_SELECTEDglobalt

    The system has selected a pool member for the connection.

  6. SERVER_CONNECTEDserversidan

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

  7. SERVERSSL_HANDSHAKEserversidan

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDserversidan

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

  9. HTTP_RESPONSEklientsidan

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

  10. SERVER_CLOSEDserversidan

    The server-side connection has been closed.

  11. CLIENT_CLOSEDklientsidan

    The client-side connection has been closed.

Villkorliga händelser

Dessa utlöses bara under särskilda villkor: en TCP::collect eller HTTP::collect, ett lastbalanseringsfel, eller ett 100 Continue-svar.

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

Referenser