With a content switching configuration binding a policy that forwards specific hostnames to a backend, which outcome is expected for requests to http://server.citrix.lab?

With a content switching configuration binding a policy that forwards specific hostnames to a backend, which outcome is expected for requests to http://server.citrix.lab?

• A. The users will be connected to Vserver Vserver-CS-1
• B. The users will be connected to the Vserver MYVPN_http
• C. The users will be blocked from accessing the site
• D. The users will be connected to CS Vserver Vserver-CS-1

Answer: (B)

Content switching routes requests based on the HTTP Host header using a bound policy. If the policy is set to forward specific hostnames to a backend vServer, a request for a hostname that matches will be sent to that backend. In this scenario, the Host header from http://server.citrix.lab matches the hostname configured in the policy, so the request is forwarded to the backend VServer named MYVPN_http. The user, therefore, connects to MYVPN_http. This is the expected behavior because the action of the policy is forwarding to the specified backend, not presenting traffic to the front-end CS vServer or blocking access.

Content switching routes requests based on the HTTP Host header using a bound policy. If the policy is set to forward specific hostnames to a backend vServer, a request for a hostname that matches will be sent to that backend. In this scenario, the Host header from http://server.citrix.lab matches the hostname configured in the policy, so the request is forwarded to the backend VServer named MYVPN_http. The user, therefore, connects to MYVPN_http. This is the expected behavior because the action of the policy is forwarding to the specified backend, not presenting traffic to the front-end CS vServer or blocking access.