Administration Guide › Configuring Proxy Rules › Proxy Rules DTD › nete:case › Forward and Redirect Syntax

Forward and Redirect Syntax

When forwarding or redirecting a request, the SPS uses a system for maintaining some part or all of the Universal Resource Indicator (URI) specified by a user. This URI points to a resource that lies on a destination server and must be interpreted by the SPS to fulfill a request.

Either of the following may be appended to a URL specified in a forward or redirect destination:

$0

Appends the entire URI string from a user’s request to the destination specified in the proxy rule.

For example, if a proxy rule forwards all user requests for www.company.com to proxy.company.com$0 and a user request for proxy.company.com/employees/hr/index.html, that request is forwarded to www.company.com/employees/hr/index.html.

$1

May only be used in nete:case elements where the parent nete:cond element specifies a URI substring match using the begins with comparison. $1 indicates that everything to the right of the matching text is appended to the forwarded or redirected request.

For example, consider a proxy rules configuration file that has a nete:cond element of:

<nete:cond type="uri" criteria="beginswith">

Assume this condition is the child of a condition that is evaluating URIs for a hostname of www.company.com and a nete:case element of:

<nete:case value="/hr">

<nete:forward>http://hr.company.com$1</nete:forward>
</nete:case>

If a user requests:

http://www.company.com/hr/employees/index.html

The request is forwarded to:

http://hr.company.com/employees/index.html

Note: Because this example specifies the $1 parameter, the /hr portion of the URI is omitted when the request is forwarded to hr.company.com.