101 · Question #513
in which scenario is a full proxy TCP connection required?
The correct answer is A. when compression is actuated. HTTP compression requires a full proxy TCP connection because the BIG-IP must buffer and process the full server response payload before it can compress and forward it to the client. Pass-through or half-proxy modes cannot support this.
Question
in which scenario is a full proxy TCP connection required?
Options
- Awhen compression is actuated
- BWhen Source NAT configured
- Cwhen a virtual server is configured
- DWhen Source IP persistence is required
How the community answered
(32 responses)- A72% (23)
- B9% (3)
- C16% (5)
- D3% (1)
Why each option
HTTP compression requires a full proxy TCP connection because the BIG-IP must buffer and process the full server response payload before it can compress and forward it to the client. Pass-through or half-proxy modes cannot support this.
Compression is a content-transformation feature that requires the BIG-IP to act as a full proxy - it must terminate the server-side TCP connection, receive the complete response body, apply compression, and then send the transformed data to the client over a separate TCP connection. Without full proxy, the device cannot inspect or modify the payload.
Source NAT only translates the source IP address in the IP header and can be performed without a full proxy TCP connection.
Configuring a virtual server alone does not mandate a full proxy - basic load balancing can use a forwarding (half-proxy) model.
Source IP persistence tracks client connections by IP for session stickiness and does not require full proxy termination of TCP.
Concept tested: F5 full proxy requirement for HTTP compression
Source: https://support.f5.com/csp/article/K8082
Topics
Community Discussion
No community discussion yet for this question.