Which transform action configuration correctly rewrites host from vpn.citrix.com to server1.citrix.com and back?

Which transform action configuration correctly rewrites host from vpn.citrix.com to server1.citrix.com and back?

• A. set transform action host change -priority 10 -reqUrlFrom https://vpn.citrix.com/* -reqUrlInto https://server1.citrix.com/* -resUrlFrom https://server1.citrix.com/* -resUrlInto https://vpn.citrix.com/*
• B. set transform action host change -priority 10 -reqUrlFrom https://server1.citrix.com/* -reqUrlInto https://vpn.citrix.com/* -resUrlFrom https://server1.citrix.com/* -resUrlInto https://vpn.citrix.com/*
• C. set transform action host change -priority 10 -reqUrlFrom https://server1.citrix.com/* -reqUrlInto https://vpn.citrix.com/* -resUrlFrom https:// vpn.citrix.com/* -resUrlInto https://server1.citrix.com/*
• D. set transform action host change -priority 10 -reqUrlFrom https://vpn.citrix.com/* -reqUrlInto https://server1.citrix.com/* -resUrlFrom https://vpn.citrix.com/* -resUrlInto https://server1.citrix.com/*

Answer: (D)

Transform action host change works by translating the host part of URLs as traffic moves in and out, so the backend can use one hostname while the client continues to use another. To rewrite the host from vpn.citrix.com to server1.citrix.com and then map the response back so the client still interacts through vpn.citrix.com, you need a consistent mapping in both directions: take the external host and translate it to the internal backend host for the request, and apply the same kind of translation for the response so the client-facing host is preserved. The configuration shown uses vpn.citrix.com as the source in both the request path and the response path, translating to server1.citrix.com in both cases. This symmetric mapping ensures that the backend sees server1.citrix.com while the transformation logic present on the path back to the client maintains the correct host relationship, achieving the intended rewrite in both directions. The other options mix directions or use the incorrect source/target pairs for either the request or the response, which would lead to mismatches or incomplete rewrites.

Transform action host change works by translating the host part of URLs as traffic moves in and out, so the backend can use one hostname while the client continues to use another. To rewrite the host from vpn.citrix.com to server1.citrix.com and then map the response back so the client still interacts through vpn.citrix.com, you need a consistent mapping in both directions: take the external host and translate it to the internal backend host for the request, and apply the same kind of translation for the response so the client-facing host is preserved.

The configuration shown uses vpn.citrix.com as the source in both the request path and the response path, translating to server1.citrix.com in both cases. This symmetric mapping ensures that the backend sees server1.citrix.com while the transformation logic present on the path back to the client maintains the correct host relationship, achieving the intended rewrite in both directions. The other options mix directions or use the incorrect source/target pairs for either the request or the response, which would lead to mismatches or incomplete rewrites.