ARM
| Configuration Variable | Data Type | Description |
|---|---|---|
| proxy.config.arm.enabled | INT |
Default: 1 Specifies that the ARM is enabled or disabled. Warning: Do not disable the ARM. In all deployments, it must be running to support proper proxy function. |
| proxy.config.arm.ignore_ifp | INT |
Default: 1 When redirection rules are applied, configures Content Gateway to use any available interface when sending packets back to the client, rather than the one that triggered the redirection rule. |
| proxy.config.arm.always_ query_dest | INT |
Default: 0 When enabled (1), Content Gateway always asks the ARM for the original destination IP address of incoming requests. This is done instead of doing a DNS lookup on the hostname of the request. When enabled, domain names are logged, instead of IP addresses, unless proxy. config.arm.use_hostname_for_ wisp_and_ reporting (see below) is disabled. When disabled, domain names are logged. See Reducing DNS lookups for additional information. It is recommended that you do not enable this variable if Content Gateway is running in both explicit proxy and transparent proxy modes. In explicit proxy mode, the client does not perform a DNS lookup on the hostname of the origin server, so Content Gateway must do it. |
| proxy.config.arm.use_ hostname_for_wisp_and_ reporting | INT |
Default: 1 Enables (1) or disables (0) the ability to capture hostname (instead of IP address) when Always Query Destination is enabled for transparent proxy deployments. See preceding entry. Note: This variable must be manually added to the config file. |
| proxy.config.http.outgoing_ip_ spoofing_enabled | INT |
Default: 0 Enables (1) or disables (0) the IP spoofing option that allows Content Gateway to establish connections to origin servers with the client IP address instead of the Content Gateway IP address. See Content Gateway IP spoofing. |
| proxy.config.arm.bypass_ dynamic_enabled | INT |
Default: 0 Enables (1) or disables (0) the adaptive bypass option to bypass the proxy and go directly to the origin server when clients or servers cause problems. See Dynamicbypass rules. |
| proxy.config.arm.bypass_use_ and_rules_bad_client_request | INT |
Default: 0 Enables (1) or disables (0) dynamic source/destination bypass in the event of non-HTTP traffic on port 80. Note: The variable proxy.config.arm. bypass_on_
Note: bad_client_request must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_400 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 400 error. Note: The variable proxy.config.arm. bypass_on_400 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_401 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 401 error. Note: The variable proxy.config.arm. bypass_on_401 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_403 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 403 error. Note: The variable proxy.config.arm. bypass_on_403 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_405 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 405 error. Note: The variable proxy.config.arm. bypass_on_405 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_406 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 406 error. Note: The variable proxy.config.arm. bypass_on_406 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_408 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 408 error. Note: The variable proxy.config.arm. bypass_on_408 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_use_ and_rules_500 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of source/destination bypass rules when an origin server returns a 500 error. Note: The variable proxy.config.arm. bypass_on_500 must also be enabled for this option to work.
|
| proxy.config.arm.bypass_on_ bad_client_request | INT |
Default: 0 Enables (1) or disables (0) dynamic destination bypass in the event of non- HTTP traffic on port 80. |
| proxy.config.arm.bypass_on_ 400 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 400 error. |
| proxy.config.arm.bypass_on_ 401 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 401 error. |
| proxy.config.arm.bypass_on_ 403 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 403 error. |
| proxy.config.arm.bypass_on_ 405 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 405 error. |
| proxy.config.arm.bypass_on_ 406 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 406 error. |
| proxy.config.arm.bypass_on_ 408 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 408 error. |
| proxy.config.arm.bypass_on_ 500 | INT |
Default: 0 Enables (1) or disables (0) dynamic generation of destination bypass rules when an origin server returns a 500 error. |
| proxy.config.arm.forward_ unwanted_traffic | INT |
Default: 0 Enables (1) or disables (0) the forwarding of traffic that is neither HTTP, HTTPS, nor FTP. |