ronutz

Kolejność zdarzeń iRule

Wybierz stos profili wirtualnego serwera BIG-IP — Client-SSL, HTTP, Server-SSL, pula — i zobacz kolejność, w jakiej wyzwalają się typowe zdarzenia iRule, od CLIENT_ACCEPTED do CLIENT_CLOSED, jako oś czasu i listę. Wszystko w przeglądarce.

Sieci
Documentation

Stos profili wirtualnego serwera

Ustawienia wstępne:

Obliczone w przeglądarce. Nic nie jest nigdzie wysyłane.

Model udokumentowanego zachowania F5 dla wirtualnego serwera Standard. Nigdy nie kontaktuje się z BIG-IP.

Sekwencja zdarzeń

strona klientastrona serweraglobalne
1CLIENT_ACCEPTEDConnection setup · strona klienta2CLIENTSSL_CLIENTHELLOClient-side TLS · strona klienta3CLIENTSSL_HANDSHAKEClient-side TLS · strona klienta4HTTP_REQUESTRequest · strona klienta5LB_SELECTEDLoad balancing · globalne6SERVER_CONNECTEDServer-side setup · strona serwera7SERVERSSL_HANDSHAKEServer-side TLS · strona serwera8HTTP_REQUEST_SENDSend to server · strona serwera9HTTP_RESPONSEResponse · strona klienta10SERVER_CLOSEDTeardown · strona serwera11CLIENT_CLOSEDTeardown · strona klienta

Zdarzenia w kolejności

  1. CLIENT_ACCEPTEDstrona klienta

    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_CLIENTHELLOstrona klienta

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

  3. CLIENTSSL_HANDSHAKEstrona klienta

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTstrona klienta

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

  5. LB_SELECTEDglobalne

    The system has selected a pool member for the connection.

  6. SERVER_CONNECTEDstrona serwera

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

  7. SERVERSSL_HANDSHAKEstrona serwera

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDstrona serwera

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

  9. HTTP_RESPONSEstrona klienta

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

  10. SERVER_CLOSEDstrona serwera

    The server-side connection has been closed.

  11. CLIENT_CLOSEDstrona klienta

    The client-side connection has been closed.

Zdarzenia warunkowe

Wyzwalają się tylko w określonych warunkach: TCP::collect lub HTTP::collect, niepowodzenie równoważenia, albo odpowiedź 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.

Źródła