ronutz

iRule-hændelsesrækkefølge

Vælg profilstakken på en BIG-IP-virtuel server — Client-SSL, HTTP, Server-SSL, pool — og se rækkefølgen, som de almindelige iRule-hændelser udløses i, fra CLIENT_ACCEPTED til CLIENT_CLOSED, som tidslinje og liste. Alt sammen i din browser.

Netværk
Documentation

Den virtuelle servers profilstak

Forudindstillinger:

Beregnet i din browser. Intet sendes nogen steder.

En model af dokumenteret F5-adfærd for en Standard-virtuel server. Den kontakter aldrig en BIG-IP.

Hændelsessekvens

klientsidenserversidenglobalt
1CLIENT_ACCEPTEDConnection setup · klientsiden2CLIENTSSL_CLIENTHELLOClient-side TLS · klientsiden3CLIENTSSL_HANDSHAKEClient-side TLS · klientsiden4HTTP_REQUESTRequest · klientsiden5LB_SELECTEDLoad balancing · globalt6SERVER_CONNECTEDServer-side setup · serversiden7SERVERSSL_HANDSHAKEServer-side TLS · serversiden8HTTP_REQUEST_SENDSend to server · serversiden9HTTP_RESPONSEResponse · klientsiden10SERVER_CLOSEDTeardown · serversiden11CLIENT_CLOSEDTeardown · klientsiden

Hændelser i rækkefølge

  1. CLIENT_ACCEPTEDklientsiden

    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_CLIENTHELLOklientsiden

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

  3. CLIENTSSL_HANDSHAKEklientsiden

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTklientsiden

    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_CONNECTEDserversiden

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

  7. SERVERSSL_HANDSHAKEserversiden

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDserversiden

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

  9. HTTP_RESPONSEklientsiden

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

  10. SERVER_CLOSEDserversiden

    The server-side connection has been closed.

  11. CLIENT_CLOSEDklientsiden

    The client-side connection has been closed.

Betingede hændelser

Disse udløses kun under særlige betingelser: en TCP::collect eller HTTP::collect, en load balancing-fejl, eller et 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.

Referencer