Define mapping rules

Mapping rules are configuration directives that cause client requests to Caching Proxy to be processed in some way, for example, passed to an origin server (proxied), redirected, or rejected. Setting mapping rules correctly is important to the proper functioning of your Caching Proxy. Mapping rules affect the following:

Mapping rule directives use the following form:

rule template target [IP_address | host_name]:[port]

Only requests that match the given template and IP-port combination are subject to that rule. A template can contain wildcards, for example, https://**/*.asp.

The order in which the rules appear in the configuration file is significant. Except for Map directives, as soon as the request is matched to a template, it is processed and subsequent rules are not evaluated. The Map directive replaces the URL in the request. This new request continues to be compared to the remaining mapping rules.

Mapping rules

The following mapping rules apply to client requests that match the given template:

The following mapping rule applies to the origin server response:

The following mapping rules apply to API applications:

Configure a surrogate server

To configure a standard surrogate:

This allows all HTTP traffic on port 80 to be proxied to the origin server. Traffic entering on the administration port does not match the initial wildcard proxy rule, and so it is unaffected. The remaining mapping rules are used to process the request.

Associated directives

The following directives define mapping rules:

For more information, refer to Manually editing the ibmproxy.conf file.

Configuration and Administration forms

The following Configuration and Administration form edits the values of the associated directives:

Note:
The Configuration and Administration forms do not support the port number argument.

For more information, refer to Using the Configuration and Administration forms.