You can create new proxy actions or you can administer
an existing proxy action. A proxy server action is an event that is
performed when an HTTP request or an HTTP response is received by
the a proxy virtual host. Some examples of proxy server actions include
caching actions, rewriting actions, compression actions, header modification
actions, and routing actions.
Before you begin
A proxy action cannot be performed unless it is associated
with a proxy rule expression. A proxy rule expression is only evaluated
when it is associated with a proxy virtual host. A proxy action can
be created or administered without a proxy rule expression or a proxy
virtual host, but it cannot be used without them.
About this task
Proxy actions are associated with proxy rule expressions.
If a proxy rule expression evaluates to true, then all of the proxy
actions specified in the proxy rule expression configuration are performed.
Complete
these steps to create a new proxy action or to administer an existing
proxy action for the proxy server.
Procedure
- From the administrative console, select proxy_server_name.
- Optional: Manage an existing proxy action configuration.
- Click proxy_action_name if you want
to view or modify the settings for an existing proxy action. If you
have made changes to the proxy action configuration, click OK to
save the changes.
- Click Delete to remove an existing
proxy action that has been selected.
- If you want to create a caching proxy action, then click New
Caching Action.
- Enter the name of the proxy action in the Action name
field. The Action name is used as the unique identifier
for this proxy action configuration. The Action name must be unique
with the cell and cannot include any of the following characters:
# \ / , : ; " * ? < > | = + & % '.
- Select the Enable caching check
box to enable caching.
- Enter the value, in seconds, for the Default
expiration field. The Default expiration field
specifies the amount of time, in seconds, before a cached response
expires.
- Enter the value, in seconds, for the Last
modified factor. The Last modified factor field
specifies the amount of time before a response is cached if the response
does not have explicit HTTP expiration headers.
- Click OK to save the proxy action
configuration.
- If you want to create a compression action, then click New
HTTP Request Compression Action to create an action for
requests, or click New HTTP Response Compression Action to
create an action for responses.
- Enter the name of the proxy action in the Action
name field. The Action name is used as the
unique identifier for this proxy action configuration. The Action
name must be unique with the cell and cannot include any of the following
characters: # \ / , : ; " * ? < > | = + & % '.
- Select the appropriate compression type from the Compression
type menu.
-
Select the content type for which compression
should occur. You can select multiple content types to
be compressed. Click New to add a new content
type to the list. If you want to remove a content type from the list,
then select the content type to be removed, and click Delete.
![[may2010]](../../deltaend.gif)
may2010
- Click OK to save the proxy action
configuration.
- If you want to create a header action, click New
HTTP Request Header Action to create an action for requests,
or click New HTTP Response Header Action to
create an action for responses.
- Enter the name of the proxy action in the Action
name field. The Action name is used as the
unique identifier for this proxy action configuration. The Action
name must be unique with the cell and cannot include any of the following
characters: # \ / , : ; " * ? < > | = + & % '.
- Enter the name of the HTTP header to be modified in
the Header name field.
- Select the appropriate action from the Header
modify action menu. The available header modify
actions include:
- Enter the value to be used for the Header modify action
in the Header value field.
- Enter an expression to be performed on the header value
in the Header value expression field. The
Header value expression is evaluated, and the modify action is performed
if the evaluation returned a match.
- If you are creating a HTTP Request Header action, then
select the appropriate methods for the Header modify action being
performed. You can select multiple methods. Click New to
add a new method to the list. If you want to remove a method from
the list, then select the method to be removed, and click Delete.
- If you are creating a HTTP Response Header action, then
select the appropriate status codes for the Header modify action being
performed. You can select multiple status codes to be included.
Click New to add a new status code to the list.
If you want to remove a status code from the list, select the status
code to be removed, and click Delete.
- Click OK to save the proxy action
configuration.
- If you want to create a rewriting action proxy action,
then click New Rewriting Action.
- Enter the name of the proxy action in the Action
name field. The Action name is used as the
unique identifier for this proxy action configuration. The Action
name must be unique with the cell and cannot include any of the following
characters: # \ / , : ; " * ? < > | = + & % '.
- Select the type of rewriting action to be performed
in the Rewriting action types menu. The following elements
can be rewritten using this type of proxy action:
- Absolute URL response
- Redirect location header
- Redirect status code
- Relative URL response
- Set cookie domain
- Set cookie path
- Enter the subject URL pattern to be rewritten in the From
pattern field.
- Enter the resulting URL pattern after the rewrite has
occurred in the To pattern field.
- Optional: Select Enable passive
rewrite to defer the rewriting of the URI until the subsequent
request for that URI is sent by the client.
- Optional: In the Cookie name field,
enter the name of the cookie for which the domain or the path are
to be rewritten. This field is only valid for the Set-Cookie
type of rewriting actions.
- Optional: In the Limit URL pattern field,
specify a constraint on the URL patterns to rewrite in the response
message. Limiting the URL pattern prevents the proxy server
from rewriting all URL patterns in the response message of a certain
page. This field is only valid for the absolute URL response action
type or the relative URL response action type.
- Optional: In the Limit Cookie
domain field, specify a constraint to limit the rewriting
of the cookie domain to only a set of specified domains. If
no domains are specified, then all domains are rewritten. This field
is only valid for the Set-Cookie type of rewriting action.
- Optional: In the Limit Cookie
path field, specify a constraint to limit the rewriting
of the cookie path to only a set of specified paths. If
no paths are specified, then all the paths are rewritten. This field
is only valid for the Set-Cookie type of rewriting action.
- Click OK to save the proxy action
configuration.
- If you want to create a routing proxy action, then click
one of the following options: New Application Server Route, New
Generic Server Cluster Route, New Fail Route, New
Redirect Route, or New Local Route.
- Enter the name of the proxy action in the Action
name field. The Action name is used as the
unique identifier for this proxy action configuration. The Action
name must be unique with the cell and cannot include any of the following
characters: # \ / , : ; " * ? < > | = + & % '.
- If you are creating a new application server route,
then follow these additional steps:
- Enter the time that this routing rule begins in the Start
time field. If the start time is specified using a 12-hour
clock, then click AM or PM.
If the start time is specified using a 24-hour clock, then click 24-hour.
- Enter the time that this routing rule completes in the End
time field. If the end time is specified using a 12-hour
clock, then click AM or PM.
If the end time is specified using a 24-hour clock, then click 24-hour.
- Select Include or Exclude from
the Action menu to specify the type of rule being configured.
- Select the applications servers that will follow this rule from
the Available application servers menu.
- Click >.
- If you want to remove an application server
from the Enabled application servers menu, then select that server
from the Enabled application servers menu, and click <.
- If you are creating a new generic server cluster route,
then follow these additional steps:
- Select the Generic server cluster that will follow this rule from
the Generic server cluster name menu.
- Select either Active Affinity or Passive
Affinity for the affinity type.
- If you selected Active Affinity, then in
the Default expiration field, enter the expiration
time in seconds.
- If you selected Passive Affinity, then in
the Cookie name field, enter the name of the
cookie to be used by the proxy server to manage affinity.
- If you selected Passive Affinity, then select
the generic server mappings for which this cookie is used to manage
affinity. If you need to create any additional mappings, click New.
If you need to remove existing cookie mappings, select the appropriate
mapping, and click Delete.
- Click New Time Mapping.
- Enter the time that this routing rule begins in the Start
time field. If this rule should be applied all the time,
then selected 24-hour.
- Enter the time that this routing rule completes in the End
time field. If this rule should be applied all the time,
then selected 24-hour.
- Select Include or Exclude from
the Action menu to specify the type of rule being configured.
- Select the cluster members that will follow this rule from the
Available generic server cluster members menu.
- Click >.
- If you want to remove a cluster member from
the Enabled generic server cluster members menu, then selected that
cluster member from the Enabled generic server cluster members menu
and click <.
- Click OK to return to set the time-of-day
rules and continue creating your generic server cluster route configuration.
- If you are creating a failure route, follow this additional
step. In the Fail status code field, enter
the status code that must be used to indicate a request was not successful.
- If you are creating a redirection route, follow this
additional step. In the Redirect URL field,
enter the URL that must be used to redirect the inbound request.
- If you are creating a local route, follow this additional
step. Confirm that the static file document root is correct. If the
existing value is not the document root that you want, click Edit.
See Administering proxy virtual hosts for more information
on changing the static file document root.
- Click OK to finish creating your
proxy action rule.