Which policy setup should be used to forward requests to Service_1 when the HTTP Host header contains xenapp.citrix.com on a load balancing virtual server?

Which policy setup should be used to forward requests to Service_1 when the HTTP Host header contains xenapp.citrix.com on a load balancing virtual server?

• A. add filter action Redirect_Service_1_Act redirect Service_1 add filter policy Redirect_Service_1_Pol -rule REQ.HTTP.HEADER HOSTNAME CONTAINS xenapp.citrix.com reqAction Redirect_Service_1_Act
• B. add filter action Redirect_Service_1_Act forward Service_1 add filter policy Redirect_Service_1_Pol -rule REQ.HTTP.HEADER HOSTNAME CONTAINS xenapp.citrix.com reqAction Redirect_Service_1_Act
• C. add filter action Redirect_Service_1_Act forward Service_1 add filter policy Redirect_Service_1_Pol -rule REQ.HTTP.HEADER HOSTNAME CONTAINS xenapp.citrix.com
• D. add filter act

Answer: (B)

Forwarding behavior is achieved by pairing a forward action with a policy rule that triggers on the Host header value. Here, you want internal routing to Service_1 whenever the HTTP Host header contains xenapp.citrix.com. The best setup uses a filter action that forwards to Service_1, and a filter policy that fires when REQ.HTTP.HEADER HOSTNAME CONTAINS xenapp.citrix.com, applying that forward action. This ensures the request is routed to Service_1 inside the appliance without changing the URL seen by the client (no redirect). The other approaches would either redirect the client (changing the URL), or omit the necessary association between the condition and the forward action, or be incomplete in syntax, so they wouldn’t achieve the desired internal forwarding behavior.

Forwarding behavior is achieved by pairing a forward action with a policy rule that triggers on the Host header value. Here, you want internal routing to Service_1 whenever the HTTP Host header contains xenapp.citrix.com. The best setup uses a filter action that forwards to Service_1, and a filter policy that fires when REQ.HTTP.HEADER HOSTNAME CONTAINS xenapp.citrix.com, applying that forward action. This ensures the request is routed to Service_1 inside the appliance without changing the URL seen by the client (no redirect).

The other approaches would either redirect the client (changing the URL), or omit the necessary association between the condition and the forward action, or be incomplete in syntax, so they wouldn’t achieve the desired internal forwarding behavior.