ronutz

Explicador da ordem de eventos de iRules

Escolha o conjunto de perfis de um virtual server do BIG-IP — Client-SSL, HTTP, Server-SSL, pool — e veja a ordem em que os eventos de iRule comuns disparam, de CLIENT_ACCEPTED a CLIENT_CLOSED, como linha do tempo e lista. Tudo no seu navegador.

Documentação (Markdown)

Redes

Conjunto de perfis do virtual server

Predefinições:

Computado no seu navegador. Nada é enviado a lugar algum.

Um modelo do comportamento documentado do F5 para um virtual server Standard. Nunca contata um BIG-IP.

Sequência de eventos

lado clientelado servidorglobal
1CLIENT_ACCEPTEDConnection setup · lado cliente2CLIENTSSL_CLIENTHELLOClient-side TLS · lado cliente3CLIENTSSL_HANDSHAKEClient-side TLS · lado cliente4HTTP_REQUESTRequest · lado cliente5LB_SELECTEDLoad balancing · global6SERVER_CONNECTEDServer-side setup · lado servidor7SERVERSSL_HANDSHAKEServer-side TLS · lado servidor8HTTP_REQUEST_SENDSend to server · lado servidor9HTTP_RESPONSEResponse · lado cliente10SERVER_CLOSEDTeardown · lado servidor11CLIENT_CLOSEDTeardown · lado cliente

Eventos em ordem

  1. CLIENT_ACCEPTEDlado cliente

    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_CLIENTHELLOlado cliente

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

  3. CLIENTSSL_HANDSHAKElado cliente

    The client-side TLS handshake has completed successfully.

  4. HTTP_REQUESTlado cliente

    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_CONNECTEDlado servidor

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

  7. SERVERSSL_HANDSHAKElado servidor

    The server-side TLS handshake has completed successfully.

  8. HTTP_REQUEST_SENDlado servidor

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

  9. HTTP_RESPONSElado cliente

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

  10. SERVER_CLOSEDlado servidor

    The server-side connection has been closed.

  11. CLIENT_CLOSEDlado cliente

    The client-side connection has been closed.

Eventos condicionais

Estes disparam apenas sob condições específicas: um TCP::collect ou HTTP::collect, uma falha de balanceamento, ou uma resposta 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.
Endpoint da APIGEThttps://ronutz.com/api/v1/f5-irules-event-orderDocumentado, não servido. Abre a especificação.

Referências