A content action enables you to use a single public IP address for external access to more than one web server. You can use a content action in an HTTP proxy policy or in an HTTPS-Server proxy action to redirect inbound requests to different web servers on your private networks. To use a content action in an HTTPS-Server proxy action, you must enable content inspection in the proxy action. If you do not enable content inspection, you can configure domain name rules to route connections to different internal servers.
Common scenarios include:
Content Action in an HTTP proxy policy
In an HTTP proxy policy, you can select an HTTP content action instead of an HTTP-Server proxy action. This enables the policy to route HTTP requests to different servers based on the domain and path in the HTTP request.
For a configuration example, go to Example — HTTP Proxy with an HTTP Content Action.
Content Action in an HTTPS-Server proxy action with content inspection enabled
In an HTTP-Server proxy action, when content inspection is enabled, you can specify an HTTP content action when you select the Inspect action. This enables the policy to route requests to different internal servers based on the domain and path in the decrypted HTTP request.
For a configuration example, go to Example: HTTPS Proxy Action with an HTTP Content Action.
Domain Name Rules in an HTTPS-Server proxy action without content inspection
If you do not enable content inspection in your HTTPS-Server proxy action, you cannot use a content action. But you can configure domain name actions to route inbound connections to different internal servers based on the server domain in the HTTPS SSL negotiation.
For a configuration example, go to Example: HTTPS Proxy Action with Domain Name Rules.
Configure HTTP Content Actions