A rewrite profile defines client caching settings for a virtual server. You can configure a rewrite
profile and select the rewrite profile when you configure the virtual server for a portal access policy.
Alternatively, you can use the default rewrite profile, rewrite.
A rewrite profile provides four options for client caching. When a portal access resource item's
Client Cache setting is set to Default, the system uses the
caching option configured in the rewrite profile. If the Client Cache option is
configured for any other setting, the portal access resource item configuration overwrites the setting in
the rewrite profile. These options are available in the rewrite profile.
|Client Cache setting
||Caches CSS and
performance but is slightly less secure because of cached images in the client browser cache.
||Caches nothing. This provides the slowest client performance and is the most secure.
||Uses the unmodified cache headers from the backend server.
Creating a rewrite profile
You can create a rewrite profile to specify the rewriting and bypass lists, and define client
caching in the virtual server definition.
The Rewrite Profile List screen opens.
The New Profile screen opens.
In the Name field, type a name for the rewrite profile.
(Optional) From the Parent Profile list, select a parent
The new rewrite profile inherits the Client Caching Type setting
from the parent profile.
(Optional) Above the Settings area, select the Custom check box to
change the Client Caching Type or Split
From the Client Caching Type list, select the caching
To enable split tunneling for portal access connections, select Split
Tunneling from the list.
Split tunneling provides two options to access your web page:
Rewrite and Bypass. If you enable split
tunneling, Access Policy Manager® presents only web pages that
satisfy one of these filters. Others are blocked (although a blocked public site may still
be available outside the webtop). If you do not use split tunneling, Access Policy Manager
processes all portal access URLs through the rewriting engine. You can specify a URL
pattern using the following syntax: scheme: //host[:port]/path. You
can also use wildcards such as the asterisk ( * ) to denote any sequence of characters and
the question mark ( ? ) for any single character. Access Policy Manager rewrites links in
all pages specified for Rewrite.
Rewrite - Rewrites URLs. When you use this option, Access
Policy Manager controls the redirection of the URL. Use this option to access URLs
inside the network. Type a URL match pattern for the sites where you need to create
the reverse-proxy and click the Add to Rewrite List
Bypass - Directly accesses the URL and leaves the URL
unmodified. Use this option to speed up serving public sites. Type a URL match pattern
for URLs to be accessed directly, bypassing the rewrite engine, and click the
Add to Bypass List button.
If Java Patching is enabled for the portal access resource,
configure the Java Patcher options for verification and re-signing of signed applets.
To configure the Trusted Certificate Authorities, first select the
check box to the right of this setting, and then from the list select a CA against which
to verify signed applets signatures.
To configure a Signer, first select the check box to the right of
this setting, and then from the list select a certificate to use for re-signing.
To configure a Signing Key, first select the check box to the
right of this setting, and then from the list select a corresponding private key for
To set a Sign Key Pass Phrase, first check the box to the right of
this setting, and then type a passphrase for the private key to be encrypted with.
The rewrite profile appears in the Rewrite Profiles list.
To use portal access rewriting, you must next assign the rewrite profile to the virtual
server that is also assigned the access profile for portal access.