Technical data
Corrections and Updates to 4.0 Documentation
3-10 Oracle iPlanet Web Proxy Server Release Notes
3.2.16 Description for Cache Finish Status in the Access Log File
You can configure the
Cache Finish Status
option by turning it
ON
to record
information about each status in the
Access Log
file. Table 3–5 lists each of the Cache
Finish Status and its description.
3.2.17 maxrequestsperconnection parameter is supported for the LS Element
Oracle iPlanet Web Proxy Server 4.0.18 supports a new parameter called
maxrequestsperconnection
for the LS element in the
server.xml
file. The following
table provides information about this new parameter.
For more information about configuring the listener, see:
http://docs.oracle.com/cd/E19438-01/821-1883/aebbt/index.html
3.2.18 Description of virt-map SAF
The
virt-map
SAF is used to implement Virtual Multihosting. The
virt-map
SAF uses
the request's
Host:
header to map a URI to a server URL. The corresponding reverse
mapping is automatically inserted by
virt-map
SAF.
RouteOfflineCheckInter
val
Takes an integer value. (Added in 4.0.15) Specify the interval,
in seconds, at which Oracle iPlanet
Web Proxy Server checks performance
of the gateways marked as offline by
the routing subsystem. The default
value is
30
.
Table 3–5 Cache Finish Status
Status Description
WRITTEN A new cache file is created
ABORTED The response could not be cached because of invalid
Last-modified:header
or invalid
Expires:header
. For more
information, switch the log status to
fine
.
UP-TO-DATE The proxy receives a confirmation from the remote server that
the proxy cache entry is updated and it may not be refreshed.
NO-CHECK The remote server was not contacted for the request from the
cache.
REFRESHED The existing cache file was refreshed by the new contents from
the origin server.
MUST-NOT-CACHE The remote server response indicates that the response must not
be cached.
DO-NOT-CACHE The document received from the remote server is not cached by
the proxy.
Parameter Description
maxrequestsperconnection
(optional) the number of requests allowed through
a single connection. The default value is "0", which
indicates that there is no limit.
Table 3–4 (Cont.)
magnus.conf
Directives
Parameters Valid Values Description