ronutz

iRule event order

Piliin ang profile stack ng isang BIG-IP virtual server — Client-SSL, HTTP, Server-SSL, pool — at tingnan ang pagkakasunod-sunod ng pag-trigger ng karaniwang iRule events, mula CLIENT_ACCEPTED hanggang CLIENT_CLOSED, bilang timeline at listahan. Lahat sa iyong browser.

Networking
Documentation

Profile stack ng virtual server

Mga preset:

Kinakalkula sa iyong browser. Walang ipinapadala kahit saan.

Isang modelo ng dokumentadong gawi ng F5 para sa isang Standard virtual server. Hindi ito kailanman kumokonekta sa isang BIG-IP.

Pagkakasunod-sunod ng event

client sideserver sideglobal
1CLIENT_ACCEPTEDConnection setup · client side2CLIENTSSL_CLIENTHELLOClient-side TLS · client side3CLIENTSSL_HANDSHAKEClient-side TLS · client side4HTTP_REQUESTRequest · client side5LB_SELECTEDLoad balancing · global6SERVER_CONNECTEDServer-side setup · server side7SERVERSSL_HANDSHAKEServer-side TLS · server side8HTTP_REQUEST_SENDSend to server · server side9HTTP_RESPONSEResponse · client side10SERVER_CLOSEDTeardown · server side11CLIENT_CLOSEDTeardown · client side

Mga event ayon sa pagkakasunod

  1. CLIENT_ACCEPTEDclient side

    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 side

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

  3. CLIENTSSL_HANDSHAKEclient side

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTclient side

    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 side

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

  7. SERVERSSL_HANDSHAKEserver side

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDserver side

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

  9. HTTP_RESPONSEclient side

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

  10. SERVER_CLOSEDserver side

    The server-side connection has been closed.

  11. CLIENT_CLOSEDclient side

    The client-side connection has been closed.

Mga conditional event

Nagti-trigger lang ang mga ito sa ilang partikular na kondisyon: isang TCP::collect o HTTP::collect, isang load-balancing failure, o isang 100 Continue na tugon.

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

Mga reperensya