201 · Question #311
Which event is always triggered when a client initially connects to a virtual server configured with an HTTP profile?
The correct answer is D. CLIENT_ACCEPTED. When a client initially connects to a virtual server, the most fundamental event that always triggers first is the acceptance of the TCP connection.
Question
Which event is always triggered when a client initially connects to a virtual server configured with an HTTP profile?
Options
- AHTTP_DATA
- BCLIENT_DATA
- CHTTP_REQUEST
- DCLIENT_ACCEPTED
How the community answered
(67 responses)- A3% (2)
- B1% (1)
- C1% (1)
- D94% (63)
Why each option
When a client initially connects to a virtual server, the most fundamental event that always triggers first is the acceptance of the TCP connection.
HTTP_DATA is not a standard iRule event.
CLIENT_DATA is triggered when payload data arrives from the client, which occurs after the connection is accepted and can fire multiple times, whereas CLIENT_ACCEPTED fires once for the connection establishment.
HTTP_REQUEST is triggered only after the entire HTTP request headers have been received and parsed by the HTTP profile, which happens significantly later than the initial TCP connection acceptance.
CLIENT_ACCEPTED is always triggered when a client's TCP connection is successfully established with the virtual server, serving as the first event in the connection flow, even before application-layer data is processed by an HTTP profile.
Concept tested: iRule connection lifecycle events
Source: https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-irules-reference/irule-events.html
Topics
Community Discussion
No community discussion yet for this question.