Proxy server actions are used in association with proxy rule expressions. If a proxy rule expression evaluates to true, then all the proxy actions associated with the rule expression are performed. Some examples of proxy server actions include caching actions, rewriting actions, compression actions, header modification actions, and routing actions.
Caching actions are set to determine whether a response is cached. A caching action specifies the last modified factor and the default expiration to define how a response is cached.
HTTP Compression actions are set to compress the request message body to the server or response message body to the client. The supported compression type standards for these proxy actions are Deflate and Gzip.
Application server routing actions allow you to specify time of day mappings for your application servers. These mappings include or exclude an application server for the routing of requests during a specified time of day. If multiple time of day mappings are configured, the matching order is the same as it is displayed in the application server route configuration.
Generic server cluster routing actions work similar to application server routes but apply to generic server clusters instead of application servers.
Fail routing actions are used to return a failure status code to an inbound request. The value of the failure status code is specified in the fail routing action configuration.
Redirect routing actions are used to redirect an inbound request to a different URL. The URL that the request is being redirected to is specified in the redirection routing action configuration.
Local routing actions are used to pass an inbound request to be served by the local Web applications deployed for the cell.