ronutz

iRule olay sırası

Bir BIG-IP virtual server'ının profil yığınını seçin — Client-SSL, HTTP, Server-SSL, havuz — ve yaygın iRule olaylarının CLIENT_ACCEPTED'tan CLIENT_CLOSED'a hangi sırayla tetiklendiğini zaman çizelgesi ve liste olarak görün. Hepsi tarayıcınızda.

Ağ
Documentation

Virtual server profil yığını

Hazır ayarlar:

Tarayıcınızda hesaplanır. Hiçbir yere hiçbir şey gönderilmez.

Standard bir virtual server için belgelenmiş F5 davranışının bir modeli. Asla bir BIG-IP'ye bağlanmaz.

Olay dizisi

istemci tarafısunucu tarafıgenel
1CLIENT_ACCEPTEDConnection setup · istemci tarafı2CLIENTSSL_CLIENTHELLOClient-side TLS · istemci tarafı3CLIENTSSL_HANDSHAKEClient-side TLS · istemci tarafı4HTTP_REQUESTRequest · istemci tarafı5LB_SELECTEDLoad balancing · genel6SERVER_CONNECTEDServer-side setup · sunucu tarafı7SERVERSSL_HANDSHAKEServer-side TLS · sunucu tarafı8HTTP_REQUEST_SENDSend to server · sunucu tarafı9HTTP_RESPONSEResponse · istemci tarafı10SERVER_CLOSEDTeardown · sunucu tarafı11CLIENT_CLOSEDTeardown · istemci tarafı

Sırayla olaylar

  1. CLIENT_ACCEPTEDistemci tarafı

    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_CLIENTHELLOistemci tarafı

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

  3. CLIENTSSL_HANDSHAKEistemci tarafı

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTistemci tarafı

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

  5. LB_SELECTEDgenel

    The system has selected a pool member for the connection.

  6. SERVER_CONNECTEDsunucu tarafı

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

  7. SERVERSSL_HANDSHAKEsunucu tarafı

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDsunucu tarafı

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

  9. HTTP_RESPONSEistemci tarafı

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

  10. SERVER_CLOSEDsunucu tarafı

    The server-side connection has been closed.

  11. CLIENT_CLOSEDistemci tarafı

    The client-side connection has been closed.

Koşullu olaylar

Bunlar yalnızca belirli koşullarda tetiklenir: bir TCP::collect veya HTTP::collect, bir yük dengeleme hatası ya da bir 100 Continue yanıtı.

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

Kaynaklar