ronutz

iRule-gebeurtenisvolgorde

Kies de profielstack van een BIG-IP-virtual-server — Client-SSL, HTTP, Server-SSL, pool — en zie de volgorde waarin de gangbare iRule-gebeurtenissen afgaan, van CLIENT_ACCEPTED tot CLIENT_CLOSED, als tijdlijn en lijst. Allemaal in je browser.

Netwerken
Documentation

Profielstack van de virtual server

Voorinstellingen:

Berekend in je browser. Er wordt niets verzonden.

Een model van gedocumenteerd F5-gedrag voor een Standard-virtual-server. Het contacteert nooit een BIG-IP.

Gebeurtenisvolgorde

clientzijdeserverzijdeglobaal
1CLIENT_ACCEPTEDConnection setup · clientzijde2CLIENTSSL_CLIENTHELLOClient-side TLS · clientzijde3CLIENTSSL_HANDSHAKEClient-side TLS · clientzijde4HTTP_REQUESTRequest · clientzijde5LB_SELECTEDLoad balancing · globaal6SERVER_CONNECTEDServer-side setup · serverzijde7SERVERSSL_HANDSHAKEServer-side TLS · serverzijde8HTTP_REQUEST_SENDSend to server · serverzijde9HTTP_RESPONSEResponse · clientzijde10SERVER_CLOSEDTeardown · serverzijde11CLIENT_CLOSEDTeardown · clientzijde

Gebeurtenissen op volgorde

  1. CLIENT_ACCEPTEDclientzijde

    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_CLIENTHELLOclientzijde

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

  3. CLIENTSSL_HANDSHAKEclientzijde

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTclientzijde

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

  5. LB_SELECTEDglobaal

    The system has selected a pool member for the connection.

  6. SERVER_CONNECTEDserverzijde

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

  7. SERVERSSL_HANDSHAKEserverzijde

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDserverzijde

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

  9. HTTP_RESPONSEclientzijde

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

  10. SERVER_CLOSEDserverzijde

    The server-side connection has been closed.

  11. CLIENT_CLOSEDclientzijde

    The client-side connection has been closed.

Voorwaardelijke gebeurtenissen

Deze gaan alleen af onder specifieke voorwaarden: een TCP::collect of HTTP::collect, een load-balancingfout, of een 100 Continue-antwoord.

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

Referenties