The following sections describe corrections and updates to Proxy Server 4.0.14 manuals:
Information About the Date and Time Parameters of the <Client> Tag
Information About the disable-javascript-rewrite Parameter of the um-define-junction SAF
Information About the forward-unread-request-body Parameter of the http-client-config SAF
Information About the lookup-ipv6-first Parameter of the dns-config SAF
Information About the regexp-redirect Function of the NameTrans Directive
Information About the status-code and status-desc Parameters of the send-error SAF
The admin.conf file, located in the install-dir/proxyadmserv/config directory, is an internal configuration file that Proxy Server maintains. Do not modify this file.
Proxy Server 4.0.15 supports several new parameters for the <Client> tag, as described in the following table.
Parameter |
Description |
---|---|
date-start and date-end |
These two parameters specify the start date and end date, respectively, for a time interval. They take values of the format of the UNIX date command, excluding the time zone specification. Additionally, the weekday portion of the date command format is optional. |
day-start and day-end |
These two parameters specify the start day number and end day number, respectively, for a day interval in a month. They take values in the range 1 through 31. |
month-start and month-end |
These two parameters specify the start month and end month, respectively, for a month interval in a year. They take the values Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov and Dec. |
time-start and time-end |
These two parameters specify the start time and end time, respectively, for a time interval in a day. They take values of the form hour:minute:second on a 24–hour clock. |
weekday-start and weekday-end |
These two parameters specify the start day and end day, respectively, for a day interval in a week. They take the values Sun, Mon, Tue, Wed, Thu, Fri and Sat. |
Examples
This example specifies a time interval of every Tuesday through Friday from 9:00 AM through 5:00 PM:
<Client weekday-start="Tue" weekday-end="Fri" time-start="09:00:00" time-end="17:00:00">
This example specifies a time interval of the first through the fifteenth of every month from 12:00 AM through 4:00 AM:
<Client day-start="1" day-end="15" time-start="00:00:00" time-end="04:00:00">
Proxy Server 4.0.15 supports a new parameter, disable-javascript-rewrite, for the um-define-junction SAF of the Init directive. The following table provides information about this new parameter.
Parameter |
Description |
---|---|
disable-javascript-rewrite |
(Optional) A regular expression matched against the names of JavaScript variables when the has-javascript parameter is set to yes. Variables whose names match the regular expression are not rewritten (as they normally would be with has-javascript set to yes). There is no default value for this parameter. |
The section http-client-config in Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference does not include information about the forward-unread-request-body parameter, which became available in Proxy Server 4.0.14. The following table provides information about this parameter.
Parameter |
Description |
---|---|
forward-unread-request-body |
(Optional) Boolean that indicates whether a request body that arrives in a TCP packet separate from the request header should be forwarded to the origin server. The default value is false, meaning that request bodies arriving in TCP packets separate from their request headers are not forwarded to the origin server. |
Proxy Server 4.0.15 supports a new tag in the obj.conf file. This tag, <Include>, includes the content of another file in the obj.conf file, effectively enabling you to divide the content of obj.conf across several files to make management of your configuration easier.
The syntax of the <Include> tag is:
<Include> filename </Include>
where filename is the name of the file to be included in obj.conf where the <Include> tag occurs.
When using the <Include> tag, keep these points in mind:
The <Include> tag can be used outside the context of <Object>. For example, you could put all the Init directives in a file and then include that file at the start of obj.conf.
An included file can contain other included files; that is, an included file can itself contain an <Include> tag.
An included file cannot cross <Object> boundaries; that is, and included file cannot end one object and start another.
Proxy Server 4.0.15 supports a new parameter, lookup-ipv6-first, for the dns-config SAF of the DNS directive. The following table provides information about this new parameter.
Parameter |
Description |
---|---|
lookup-ipv6–first |
(Optional) Boolean that specifies whether to look up IPv6 or IPv4 addresses first. The default value is false, meaning that IPv4 addresses are looked up first. |
The section NameTrans in Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference does not include information about the regexp-redirect function. Information about this function follows.
Applicable in NameTrans-class directives.
The regexp-redirect function enables you to change URLs and send the updated URL to the client. When a client accesses your server with an old path, the server treats the request as a request for the new URL.
Parameters
The following table describes parameters for the regexp-redirect function.
Parameter |
Description |
---|---|
from |
A regular expression for the prefix of the requested URI to match. |
url specifies a complete URL to return to the client. url-prefix specifies the new URL prefix to return to the client. The from prefix is simply replaced by this URL prefix. You cannot use these parameters together. |
|
(Optional) Flag that tells the server to util_uri_escape the URL before sending it. It should be yes or no. The default is yes. For more information about util_uri_escape, see Oracle iPlanet Web Proxy Server 4.0.14 NSAPI Developer’s Guide. |
|
bucket |
(Optional) Common to all obj.conf functions. |
Proxy Server 4.0.15 supports two new parameters for the send-error SAF of the Service and Error directives. The following table provides information about these new parameters.
Parameter |
Description |
---|---|
status-code |
(Optional) Specifies a status code to be set in the HTTP response. It differs from the code parameter in that code specifies which error code triggers execution of the send-error SAF, while status-code specifies a status code to be set in the response generated by the send-error SAF. |
status-desc |
(Optional) Specifies a reason string for the status code. |
This section lists directives added to the magnus.conf file. Note that these directives are not documented in Chapter 3, Syntax and Use of the magnus.conf File, in Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference.
Table 3 magnus.conf Directives
Parameters |
Valid Values |
Description |
---|---|---|
ChannelPoolMonitorInterval |
Any number of seconds |
(Added in 4.0.14 release.) Specify how frequently (in seconds) Proxy Server checks the channel pool for stale or closed connections. This value is used when ChannelPoolValidate is set to true. The default value is 30. |
ChannelPoolValidate |
true, false |
(Added in 4.0.14 release.) Cause Proxy Server to actively check the channel pool for stale or closed connections every ChannelPoolMonitorInterval seconds. The default value is false. |
ChannelReuseValidate |
true, false |
(Added in 4.0.14 release.) Cause Proxy Server to validate channels in the channel pool before reusing them. The default value is false |
FtpPoolSize |
1 – 65536 |
(Added in 4.0.12 release.) Specify the size of the FTP connection pool. The default value is 256. |
FtpPoolLife |
1 – 65536 |
(Added in 4.0.12 release.) Specify the life of the connection in seconds, that the FTP connection remain unused in the pool before the monitor thread closes it. The default value is 3600. |
FtpPoolMonitorThread |
OFF |
(Added in 4.0.12 release.) Specify the boolean value to monitor the FTP thread functionality. The default is ON. |
FtpPoolMonitorLevel |
0 |
(Added in 4.0.12 release.) Specify an integer value. If set to 0 the pool monitor thread checks whether the connection is dead or alive. If set to 1, the NOOP command is sent to the connection and awaits for the reply. Failure to get a response will cause the connection to be removed from the pool. The default level is 1. |
FtpPoolMonitorInterval |
30 – 65536 |
(Added in 4.0.12 release.) Specify an integer value in seconds, after which the pool connections are monitored. The default value is 30 |
LDAPPoolMonitorThread |
Takes a boolean value. |
(Added in 4.0.12 release.) If set to TRUE, a ldap pool monitor thread would be created which monitors the ldap connection pool at regular intervals. The default value is FALSE. |
LDAPPoolMonitorInterval |
Takes an integer argument. |
(Added in 4.0.12 release.) Specifies the interval at which the ldap pool monitor thread inspects the ldap connection pool. The default value is 30. |
LDAPPoolRevalidate |
Takes a boolean value. |
(Added in 4.0.12 release.) If set to TRUE, every connection that is picked off the connection pool will be "revalidated" before being passed on to the caller. The default value is FALSE. |
RouteOfflineCheckInterval |
Takes an integer value. |
(Added in 4.0.15 release.) Specifies the interval, in seconds, at which Proxy Server performs a health check on gateways marked as offine by the routing subsystem. The default value is 30. |