ADC

Rewrite for Citrix Gateway and authentication server generated responses

Rewrite refers to the rewriting of some information in the requests or responses handled by the Citrix ADC appliance. Rewriting can help in providing access to the requested content without exposing unnecessary details about the website’s actual configuration. For a detailed information on rewrite concept, see Rewrite

Starting from Citrix ADC release build 13.0-76.29, the support for rewrite policies has been extended to Citrix Gateway virtual server and authentication virtual server generated responses.

Note

A bind type AAA_RESPONSE is introduced to support rewrite policies for the Citrix Gateway virtual server and authentication virtual server generated responses. Configure the AAA_RESPONSE bind type if the response generated by the authentication virtual server or the Citrix Gateway virtual server is from the packet engine.

An example to use Rewrite

You can use Rewrite to share the resources available on on-premises Citrix ADC with Citrix Cloud deployment. This can be achieved securely by implementing CORS origin resource sharing. Rewrite can be used as follows to implement CORS header.

Sample configuration

add rewrite action cors_header_action insert_http_header access-control-allow-credentials \"true\"

add rewrite policy cors_header_pol true cors_header_action

add rewrite action non_cors_header_action insert_http_header X-Frame-Options \'\"DENY\"\'

add rewrite policy non_cors_header_pol true non_cors_header_action

bind authentication vserver av_cors -policy cors_header_pol -priority 100 -type AAA_RESPONSE

bind vpn vserver av_cors -policy cors_header_pol -priority 100 -type AAA_RESPONSE

Note:

For instructions on how to configure a rewrite action and policy using the GUI, see Rewrite.

Rewrite for Citrix Gateway and authentication server generated responses