Outbound HTTP connection configuration script settings

Outbound HTTP connection configuration script settings

The configuration settings of an outbound HTTP connection configuration script are described here.
The proxy-rules setting is the root of a configuration profile. The configuration profile for which the script is applied is specified in the configuration task that is run against this script.
The proxy-rules setting can contain the following subsettings:

variables Endpoint variables or dynamic policy variables. Variables are used in the URL attribute of the policy setting, or they are used in a variable value.
mapping Map incoming requests to a target URL, based on their context path. Therefore, each mapping must specify a contextpath attribute and optionally a url attribute. Optionally, mappings can declare policy settings that represent mapping specific access policies. Mappings contain a name attribute that gives an administrative name for this mapping. This attribute is used by administrative tasks to identify the mapping for update tasks or delete tasks.
policy Access policy for a specific URL pattern. A proxy configuration can contain multiple policy definitions. If no policy is specified at all, the portal denies all incoming requests.
ipfilter One or more IP filter patterns used to grant or deny a particular IP address, or a set of addresses access to the Ajax proxy.
meta-data Set general configuration properties of the proxy, for example HTTP-related parameters. Each meta-data setting must have a name and a value.

See also

Variables

Context path mapping

Policies

IP filtering

Configuration metadata for outbound HTTP connections

Cookie rule

Parent XML format for outbound HTTP connection configuration settings
Related concepts:

The programming model for the outbound HTTP connection service

variables	Endpoint variables or dynamic policy variables. Variables are used in the URL attribute of the policy setting, or they are used in a variable value.
mapping	Map incoming requests to a target URL, based on their context path. Therefore, each mapping must specify a contextpath attribute and optionally a url attribute. Optionally, mappings can declare policy settings that represent mapping specific access policies. Mappings contain a name attribute that gives an administrative name for this mapping. This attribute is used by administrative tasks to identify the mapping for update tasks or delete tasks.
policy	Access policy for a specific URL pattern. A proxy configuration can contain multiple policy definitions. If no policy is specified at all, the portal denies all incoming requests.
ipfilter	One or more IP filter patterns used to grant or deny a particular IP address, or a set of addresses access to the Ajax proxy.
meta-data	Set general configuration properties of the proxy, for example HTTP-related parameters. Each meta-data setting must have a name and a value.