101 · Question #50
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. CLIENT_ACCEPTED is a TCP-level event triggered on every new client connection regardless of the application profile assigned to the virtual server.
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
(39 responses)- B3% (1)
- C5% (2)
- D92% (36)
Why each option
CLIENT_ACCEPTED is a TCP-level event triggered on every new client connection regardless of the application profile assigned to the virtual server.
HTTP_DATA is not a valid standard iRule event in F5 BIG-IP; it does not exist in the iRules event model.
CLIENT_DATA fires only when the client sends data after the connection is established, so it is not triggered on the initial connection itself.
HTTP_REQUEST fires only after BIG-IP has received and parsed a complete HTTP request line and headers, which happens after CLIENT_ACCEPTED.
CLIENT_ACCEPTED fires at the TCP layer the moment a client completes the three-way handshake with the virtual server, which always occurs before any application-layer processing. Even when an HTTP profile is applied, the TCP connection event fires first, making CLIENT_ACCEPTED the guaranteed first event in every connection lifecycle.
Concept tested: TCP connection initiation iRule event order
Source: https://clouddocs.f5.com/api/irules/CLIENT_ACCEPTED.html
Topics
Community Discussion
No community discussion yet for this question.