| Oracle® iPlanet Web Proxy Server Release Notes Release 4.0.16 Part Number E18782-01 |
|
|
View PDF |
| Oracle® iPlanet Web Proxy Server Release Notes Release 4.0.16 Part Number E18782-01 |
|
|
View PDF |
The Proxy Server 4.0 documentation is provided in a number of ways:
Manuals - You can view the Oracle iPlanet Web Proxy Server 4.0 manuals and release notes in HTML and in printable PDF formats.
Online help - Click the Help button in the graphical interface to search a context-sensitive help window.
Oracle iPlanet Web Proxy Server 4.0.14 is the last release for which the entire documentation set for Oracle iPlanet Web Proxy Server 4.0 was updated. Subsequent to the 4.0.14 release, updates and corrections to Oracle iPlanet Web Proxy Server 4.0 documentation are provided in this Release Notes document; see Section 3.2, "Corrections and Updates to 4.0.14 Manuals."
This chapter includes the following sections:
The Oracle iPlanet Web Proxy Server 4.0.14 documentation is available at:
http://download.oracle.com/docs/cd/E19438-01/
For an introduction to Oracle iPlanet Web Proxy Server, read the books in the order in which they are listed in Table 3-1.
Table 3-1 Proxy Server 4.0.14 Documentation Set
The following sections describe corrections and updates to Oracle iPlanet Web Proxy Server 4.0.14 manuals:
clf-request-leading-whitespace Parameter of the flex-log SAF
Clarification About Unit of Time Used for the %duration% Log Option
forward-unread-request-body Parameter of the http-client-config SAF
status-code and status-desc Parameters of the send-error SAF
The "Setting Cache Capacity" section of the Oracle iPlanet Web Proxy Server 4.0.13 Administration Guide mentions that the cache capacity can be up to a maximum of 32 GB.
Starting from the 4.0.10 release, the maximum cache capacity that can be configured through the administration interface is 128 GB.
Note:
You can manually configure the cache capacity to any value higher than 128 GB (no upper limit) by editing the
server.xml configuration file. But if you opt for the manual configuration route and want to set the cache capacity to a value that is less than 128 GB, then only the following values are allowed: 125, 250, 500, 1000, 2000, 4000, 8000, 16000, 32000, 64000, 128000.In the "Log Format" section of the Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference, Table 5-4 lists the available flexible logging options. The %Req->vars.xfer-time% option is missing from the list.
The %Req->vars.xfer-time% option can be used to log the transfer time (in seconds).
Proxy Server 4.0.16 supports a new parameter, clf-request-leading-whitespace, for the flex-log SAF of the AddLog directive. The following table provides information about the new parameter.
| Parameter | Description |
|---|---|
clf-request-leading-whitespace |
(Optional) A boolean value indicating whether leading newlines in request lines should be removed before printing to the server access log.
The default value is Example: AddLog fn="flex-log" name="access" clf-request-leading-whitespace="no" |
For information about the other parameters of the flex-log SAF, see the "flex-log" section of the Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference.
Table 3-2 lists new parameters added for the um-define-junction SAF of the Init directive since the 4.0.14 release. Note that these parameters are not documented in the Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference.
Table 3-2 New Parameters of the um-define-junction SAF
| Parameter | Added in Release | Description |
|---|---|---|
|
|
4.0.16 |
(Optional) These parameters can be used to specify the target and destination values for rewriting the |
|
|
4.0.16 |
(Optional) If this parameter is set to The default value is |
|
|
4.0.16 |
(Optional) This parameter can be used to insert a |
|
|
4.0.16 |
(Optional) These parameters can be used to specify the target and destination values for rewriting the |
|
|
4.0.15 |
(Optional) A regular expression matched against the names of JavaScript variables when the |
According to the "Log Format" section of the Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference, the %duration% option indicates the time the server spent handling the request in microseconds.
Note the following clarification:
On Solaris and AIX, the server calculates and records the time in microseconds.
However, on Windows, HP-UX, and Linux, the server calculates the time in milliseconds and records it in microseconds.
The "Configuring Directory Services" section of the Oracle iPlanet Web Proxy Server 4.0.14 Administration Guide describes how to create a directory service. Note that if you want to use the new directory service with a specific proxy server instance, you must select it as described in the "Selecting Directory Services" section.
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.
Oracle iPlanet Web 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">
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) A Boolean operator that indicates whether a request body that arrives in a TCP packet separate from the request header should be forwarded to the server of origin. The default value is false, meaning that request bodies arriving in TCP packets separate from their request headers are not forwarded to the server of origin. |
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>
filename is the name of the file to be included in the obj.conf file 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 the obj.conf. file.
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, 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) A Boolean operator 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.
The regexp-redirect function is 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.
The following table describes parameters for the regexp-redirect function.
| Parameter | Description |
|---|---|
from |
A regular expression for the prefix of the requested URL to match. |
url/url-prefix |
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. |
escape |
(Optional) A Flag that tells the server to use the util_uri_escape action on the URL before sending it. It should be yes or no. The default is yes.
For more information about |
bucket |
(Optional) This is 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. |
Table 3-3 lists directives added to the magnus.conf file. Note that these directives are not documented in "Syntax and Use of the magnus.conf File" in Oracle iPlanet Web Proxy Server 4.0.14 Configuration File Reference.
Table 3-3 magnus.conf Directives
| Parameters | Valid Values | Description |
|---|---|---|
|
|
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 |
|
|
|
(Added in 4.0.14 release.) Cause Proxy Server to actively check the channel pool for stale or closed connections every |
|
|
|
(Added in 4.0.14 release.) Cause Proxy Server to validate channels in the channel pool before reusing them. The default value is |
|
|
|
(Added in 4.0.12 release.) Specify the size of the FTP connection pool. The default value is 256. |
|
|
|
(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 |
|
|
|
(Added in 4.0.12 release.) Specify the boolean value to monitor the FTP thread functionality. The default is |
|
|
|
(Added in 4.0.12 release.) Specify an integer value. If set to If set to |
|
|
|
(Added in 4.0.12 release.) Specify an integer value in seconds, after which the pool connections are monitored. The default value is |
|
|
Takes a Boolean value. |
(Added in 4.0.12 release.) If set to |
|
|
Takes an integer argument. |
(Added in 4.0.12 release.) Specify the interval at which the |
|
|
Takes a boolean value. |
(Added in 4.0.12 release.) Revalidate the connection if set to |
|
|
Takes an integer value. |
(Added in 4.0.15 release.) Specify the interval, in seconds, at which Proxy Server checks performance of the gateways marked as offine by the routing subsystem. The default value is |
The Oracle web site provides information about the following additional resources:
|
 Copyright © 2001, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|