Proxy server actions

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

Caching actions are set to determine whether or not a response will be cached. A caching action specifies the last modified factor and the default expiration to define how a response is cached.

 

Rewriting actions

Rewriting actions define how the proxy server rewrites uniform resource locators (URL). A rewriting action is used to rewrite elements of a response message. This is often done to mask the back-end server identity with that of the proxy server. The follow elements can be rewritten using this type of proxy action:

• Absolute URL response

• Redirect location header

• Redirect status code

• Relative URL response

• Set-Cookie

 

Compression actions

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.

 

Header modification actions

Header modification actions are implemented to perform a header modify action on a specified HTTP header. The available header modify actions include:

• Set

• Append

• Edit

• Remove

The header modify action is performed only if the expression matches when the specified value is applied. For HTTP requests, the header modify action is performed on the HTTP methods you specify. For HTTP responses, the header modify action is performed on the HTTP status codes you specify.

 

Routing actions

Routing actions are used to route requests when a given rule expression is matched.

The following types of routing actions are available:

• Application Server routes

  Application Server routing actions allow us to specify time of day mappings for the appservers. These mappings include or exclude an appserver for the routing of requests during a specified time of day. If multiple time of day mappings are configured, the order they are matched is the same as they appear in the appserver route configuration.

• Generic server cluster routes

  Generic server cluster routing actions work similar to appserver routes but apply to generic server clusters instead of appservers.

• Fail routes

  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 routes

  Redirect routing actions are used to redirect an inbound request to a different URL. The URL the request is being redirected to is specified in the redirection routing action configuration.

• Local routes

  Local routing actions are used to pass an inbound request to be served by the local web applications deployed for the cell.

.

---

 

Related tasks

Administer proxy rule expressions
Administer proxy actions

 

Related

Proxy actions collection