ronutz

Susunan acara iRule

Pilih timbunan profil pelayan maya BIG-IP — Client-SSL, HTTP, Server-SSL, pool — dan lihat susunan acara iRule biasa dicetuskan, dari CLIENT_ACCEPTED ke CLIENT_CLOSED, sebagai garis masa dan senarai. Semuanya dalam pelayar anda.

Rangkaian
Documentation

Timbunan profil pelayan maya

Pratetap:

Dikira dalam pelayar anda. Tiada apa-apa dihantar ke mana-mana.

Model tingkah laku F5 yang didokumenkan untuk pelayan maya Standard. Ia tidak pernah menghubungi BIG-IP.

Urutan acara

sisi kliensisi pelayanglobal
1CLIENT_ACCEPTEDConnection setup · sisi klien2CLIENTSSL_CLIENTHELLOClient-side TLS · sisi klien3CLIENTSSL_HANDSHAKEClient-side TLS · sisi klien4HTTP_REQUESTRequest · sisi klien5LB_SELECTEDLoad balancing · global6SERVER_CONNECTEDServer-side setup · sisi pelayan7SERVERSSL_HANDSHAKEServer-side TLS · sisi pelayan8HTTP_REQUEST_SENDSend to server · sisi pelayan9HTTP_RESPONSEResponse · sisi klien10SERVER_CLOSEDTeardown · sisi pelayan11CLIENT_CLOSEDTeardown · sisi klien

Acara mengikut susunan

  1. CLIENT_ACCEPTEDsisi klien

    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_CLIENTHELLOsisi klien

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

  3. CLIENTSSL_HANDSHAKEsisi klien

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTsisi klien

    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_CONNECTEDsisi pelayan

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

  7. SERVERSSL_HANDSHAKEsisi pelayan

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDsisi pelayan

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

  9. HTTP_RESPONSEsisi klien

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

  10. SERVER_CLOSEDsisi pelayan

    The server-side connection has been closed.

  11. CLIENT_CLOSEDsisi klien

    The client-side connection has been closed.

Acara bersyarat

Ini dicetuskan hanya dalam keadaan tertentu: TCP::collect atau HTTP::collect, kegagalan pengimbangan beban, atau respons 100 Continue.

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

Rujukan