Oracle Application Server Web Cache Administrator's Guide 10g (9.0.4) Part Number B10401-01 |
|
This chapter explains how to use OracleAS Web Cache event and access logs.
This chapter contains these topics:
OracleAS Web Cache events and errors are stored in an event log. The event log can help you determine which documents or objects have been inserted into the cache. It can also identify listening port conflicts or startup and shutdown issues. By default, the event log has a file name of event_log
and is stored in $ORACLE_HOME/webcache/logs
on UNIX and ORACLE_HOME
\webcache\logs
on Windows.
This section contains the following topics:
Chapter 16 for descriptions of the event log messages
See Also:
Event messages are written using either of the following formats:
Oracle-ECID
request header so that you can easily find the matching request detail line.
[Timestamp
][severity
message_id
][ecid:request_id
,serial_number
]Event_Log_ Message
[detail]
indicates that the event is for a request. This format is logged the first time an event is logged for a request. In addition to the IP address, site name, and URL of the request, the ID and sequence number of the Oracle-ECID
request header is logged. The Oracle-ECID
request header is used to track requests.
[Timestamp][module_name][detail][ecid: request_id, hop_number] [client: IP_ address] [host: site] [url: URL]
Table 12-1 describes the fields for the default event log format.
Table 12-2 describes the fields for the request detail format.
See Also:
|
To configure the event log settings:
The Event Logs page appears.
The Edit Cache-Specific Event Log Configuration dialog box appears.
The default is $ORACLE_HOME/webcache/logs
on UNIX and ORACLE_HOME
\webcache\logs
on Windows.
With buffered logging, OracleAS Web Cache writes to the event log after the buffer is full. The buffer size is set 2048 bytes. When the limit is reached, OracleAS Web Cache writes buffered events to the event log file.
Oracle Corporation recommends disabling buffering when you need to see the event log results immediately, such as when you are debugging OracleAS Web Cache.
The default is 10 seconds. When the interval is reached, OracleAS Web Cache writes buffered events to the event log file. Even if the buffer is not full, the event log is updated at least every 10 seconds. Oracle Corporation recommends not changing the default unless you need to lower the interval to see results more frequently.
The Edit Global Event Log Configuration dialog box appears.
The default file name is event_log
.
Oracle Corporation recommends selecting No if either of the following conditions apply:
See Also:
event_log_file
.
yyyymmdd
and write new log information to the current event log file.
Table 12-4 describes additional configuration instructions for Weekly, Daily, and Hourly.
Policy | To configure: |
---|---|
Weekly |
|
Daily |
|
Hourly |
If you have a high-volume site, create a daily or hourly policy.
See Also:
"Rolling Over Event and Access Logs" for instructions on immediately rolling over log files |
This section contains the following event log examples:
The following shows an event log excerpt with successful startup entries:
[25/Jun/2003:19:08:52 +0000] [notification 9612] [ecid: -] OracleAS Web Cache version number: 9.0.4 [25/Jun/2003:19:08:52 +0000] [notification 9403] [ecid: -] Maximum number of file/socket descriptors set to 950. [25/Jun/2003:19:08:52 +0000] [notification 13002] [ecid: -] Maximum allowed incoming connections are 700 [25/Jun/2003:20:44:37 +0000] [notification 12209] [ecid: -] A 1 node cluster successfully initialized [25/Jun/2003:19:08:52 +0000] [notification 9608] [ecid: -] The cache server process started successfully.
The following shows an event log excerpt with unsuccessful startup events. OracleAS Web Cache is unable to listen on port 7777, because it is already in use. This can occur if OracleAS Web Cache is already running and listening on that port or another application is using that port.
[25/Jun/2003:19:12:40 +0000] [notification 9612] [ecid: -] OracleAS Web Cache version number: 9.0.4 [25/Jun/2003:19:12:40 +0000] [notification 9403] [ecid: -] Maximum number of file/socket descriptors set to 950. [25/Jun/2003:19:12:40 +0000] [notification 13002] [ecid: -] Maximum allowed incoming connections are 700 [25/Jun/2003:19:12:40 +0000] [alert 13305] [ecid: -] failed to assign port 7777, bind() error = Address already in use [25/Jun/2003:19:12:40 +0000] [alert 9707] [ecid: -] Failed to start the server. [25/Jun/2003:19:12:40 +0000] [alert 9609] [ecid: -] The server process could not initialize. [25/Jun/2003:19:12:40 +0000] [notification 9610] [ecid: -] The server is exiting.
The following shows an event log excerpt with typical shutdown entries:
[25/Jun/2003:19:09:49 +0000] [notification 9703] [ecid: -] Stop Issued. The program will shut down after all accepted requests are served, or a timeout occurs. [25/Jun/2003:19:09:49 +0000] [notification 9610] [ecid: -] The server is exiting.
The following shows an event log excerpt containing events for a cache-miss request:
[25/Jun/2003:19:46:26 +0000] [detail] [ecid: 20910180667,0] [client: 130.35.44.78] [host: www.company.com:80] [url: /index.html] [25/Jun/2003:19:46:26 +0000] [trace 11331] [ecid: 20910180667,0] The host request header matches configured site www.company.com:80. [25/Jun/2003:19:46:26 +0000] [trace 11351] [ecid: 20910180667,0] The complete site name is: www.company.com:80 [25/Jun/2003:19:46:26 +0000] [trace 11414] [ecid: 20910180667,0] The initial cache key is composed: /www.company.com:80/index.html . [25/Jun/2003:19:46:26 +0000] [trace 11304] [ecid: 20910180667,0] Cache miss request. [25/Jun/2003:19:46:26 +0000] [trace 11224] [ecid: 20910180667,0] Site www.company.com:80 matches site-to-server mapping www.company.com:80. [25/Jun/2003:19:46:26 +0000] [trace 11227] [ecid: 20910180667,0] Request is routed to origin server hhayashi-sun:7778 (id=0) using load balancing for site www.company.com:80. [25/Jun/2003:19:46:27 +0000] [trace 11403] [ecid: 20910180667,0] begin cacheability decision for following URL www.company.com:80/index.html [25/Jun/2003:19:46:27 +0000] [trace 11407] [ecid: 20910180667,0] URL matches caching rule \.html?$. [25/Jun/2003:19:46:27 +0000] [trace 11446] [ecid: 20910180667,0] URL which will be cached is: www.company.com:80/index.html [25/Jun/2003:19:46:27 +0000] [trace 11415] [ecid: 20910180667,0] Final cache key is composed: /www.company.com:80/index.html . [25/Jun/2003:19:46:27 +0000] [trace 11088] [ecid: 20910180667,0] The following URL is now in the cache: www.company.com:80/index.html
The following shows an event log excerpt containing events for a subsequent cache-hit request:
[25/Jun/2003:19:46:58 +0000] [detail] [ecid: 20910213770,0] [client: 130.35.44.78] [host: www.company.com:80] [url: /index.html] [25/Jun/2003:19:46:58 +0000] [trace 11331] [ecid: 20910213770,0] Host request header matches configured site www.company.com:80. [25/Jun/2003:19:46:58 +0000] [trace 11351] [ecid: 20910213770,0] The completed site name is: www.company.com:80 [25/Jun/2003:19:46:58 +0000] [trace 11414] [ecid: 20910213770,0] Initial cache key is composed: /www.company.com:80/index.html . [25/Jun/2003:19:46:58 +0000] [trace 11415] [ecid: 20910213770,0] Final cache key is composed: /www.company.com:80/index.html . [25/Jun/2003:19:46:58 +0000] [trace 11338] [ecid: 20910213770,0] URL is in the cache. [25/Jun/2003:19:46:58 +0000] [trace 11344] [ecid: 20910213770,0] Returning a freshly cached document.
The following shows an event log excerpt with an event associated with an invalidation request for the removal of document cache.htm
.
[13/Dec/2002:19:26:46 +0000] [notification 11706][ecid: 21085932167,0] 10 objects (s) matching prefix '/cache/' are invalidated. [13/Dec/2002:19:26:46 +0000] [notification 11748] [ecid: 21085932167,0] Invalidation with INFO 'removing 15k document' has returned with status ' SUCCESS'; number of documents invalidated: '10'.
The following shows an event log excerpt with an XML invalidation request error. In this example, OracleAS Web Cache is unable to parse the request.
[13/Dec/2002:19:37:36 +0000] [alert 13109] [ecid: 21086599201,0] XML parsing error in N/A. Error code 210: LPX-00210: expected '=' instead of 'H' [13/Dec/2002:19:37:36 +0000] [error 13112] [ecid: 21086599201,0] XML parsing failed. Error Code: 210 [13/Dec/2002:19:37:36 +0000] [error 11716] [ecid: 21086599201,0] Invalidation XML message cannot be parsed.
The following shows an event log excerpt with ESI parsing errors that indicate a problem with the src
attribute and variable syntax:
[16/Jan/2003:01:59:48 +0000] [detail] [ecid: 19734744942,0] [client: 127.0.0.1] [host: www.company.com:80] [url: /cgi-bin/esi-headers.sh?err1.htm] [16/Jan/2003:01:59:48 +0000] [error 12086] [ecid: 19734744942,0] ESI syntax error. Unrecognized keyword src is at line 3. [16/Jan/2003:01:59:48 +0000] [warning 11064] [ecid: 19734744942,0] ESI document www.company.com:80/cgi-bin/esi-headers.sh?err1.htm parsing error ... [16/Jan/2003:02:11:57 +0000] [detail] [ecid: 19735486051,0] [client: 127.0.0.1] [host: www.company.com] [url: /cgi-bin/esi-headers.sh?err1.htm] [16/Jan/2003:02:11:57 +0000] [error 12095] [ecid: 19735486051,0] ESI syntax error. A variable requires a key at line 3. [16/Jan/2003:02:11:57 +0000] [warning 11064] [ecid: 19735486051,0] ESI document www.company.com:80/cgi-bin/esi-headers.sh?err1.htm parsing error
The following shows an event log excerpt with ESI processing errors that indicate an error fetching an ESI fragment named a.html
and an unknown fragment for an undefined site:
[16/Jan/2003:02:02:37 +0000] [detail] [ecid: 19734914560,0] [client: 127.0.0.1] [host: www.company.com:80] [url: /cgi-bin/esi-headers.sh?err1.htm] [16/Jan/2003:02:02:37 +0000] [warning 12005] [ecid: 19734914560,0] HTTP Client Error 4xx exception in ESI template www.company.com:80/cgi-bin/esi-headers.sh?err1.htm, fragment www.company.com:80/cgi-bin/a.html .... [16/Jan/2003:02:03:38 +0000] [detail] [ecid: 19734980113,0] [client: 127.0.0.1] [host: -] [url: /cgi-bin/esi-headers.sh?err1.htm] [16/Jan/2003:02:03:38 +0000] [warning 11295] [ecid: 19734980113,0] OracleAS Web Cache failed in DNS lookup for host www.company2.com:80. [16/Jan/2003:02:03:38 +0000] [warning 12003] [ecid: 19734980113,0] No connection exception in ESI template www.company.com:80/cgi-bin/esi-headers.sh?err1.htm, fragment www.company2.com:80/a.html
By default, OracleAS Web Cache adds diagnostics information to the Server
-response header field:
Server: OracleAS/version Server_header_from_origin_server OracleAS-Web-Cache/version (diagnostic_information)
For diagnostics purposes, it can be useful to also display this information in the HTML response body of a document. Once enabled, you simply append a string to the URL of the document into the browser to see the diagnostic information string embedded in the response body. In addition to diagnostics information, you can optionally display event log information, with a verbosity level of TRACE, in the HTML response.
See Also:
Table 2-4 for a detailed description of the diagnostic information displayed |
To configure where to display diagnostic information:
The Diagnostics page appears.
The Edit Global Page Body Diagnostics Configuration dialog box displays.
By default, the string is set to +wcdebug
.
Server
response header, from the Global Server Header Diagnostics table, click Enable or Disable.
OracleAS Web Cache generates an access log that contains information about the HTTP requests sent to OracleAS Web Cache. By default, the access log has a file name of access_log
and is stored in $ORACLE_HOME/webcache/logs
on UNIX and ORACLE_HOME
\webcache\logs
on Windows.
This section contains the following topics:
Oracle Application Server 10g Administrator's Guide for further information about managing log files with Oracle Enterprise Manager
See Also:
You can configure the content of the access log files by defining the fields to appear for each HTTP request event. These fields are based on the Extended LogFile Format (XLF). By default, OracleAS Web Cache provides support the following log formats:
This format is the default format applied to access logs. This format is appropriate for most configurations.
The CLF format provides support for the following fields:
The combined format provides support for the CLF fields and the following additional fields:
Select this format when you need to determine what kind of browser is sending the request, and where the browser was visiting before the request was forwarded to OracleAS Web Cache.
This format provides support for the following fields intended for end-user performance monitoring features:
x-req-type
x-date-start
x-time-start
c-ip
s-ip
x-auth-id
cs(Host)
cs-method
cs-uri
x-protocol
sc-status
bytes
cs-bytes
x-cache
time-taken
r-time-taken
x-time-delay
x-os-timeout
x-ecid
x-cookie(ORACLE_SMP_CHRONOS_ST)
x-cookie(ORACLE_SMP_CHRONOS_LT)
x-cookie(ORACLE_SMP_CHRONOS_GL)
cs(Referer)
cs(User-Agent)
x-esi-info
If the default formats are not suitable for your configuration, you can specify the fields that you require. Table 12-5 describes the supported fields. Fields prefixed with x
or r
are proprietary to OracleAS Web Cache.
Field | Description |
---|---|
|
Content length of the request |
|
IP address of the browser |
|
Integer that specifies cache status. Cache status is reported as one of the following: |
|
HTTP request header sent from the browser See Also: "cs(header_name) and sc(header_name) Access Log Fields" |
|
Bytes received from the browser |
|
Browser-to-OracleAS Web Cache HTTP request method |
|
Browser-to-OracleAS Web Cache URI |
|
Browser-to-OracleAS Web Cache query portion of URI, omitting the stem |
|
Browser-to-OracleAS Web Cache stem portion of URI, omitting the query |
|
Date the transaction completed, in the following format:
|
|
IP address and port number of origin server. For a cache cluster, this field displays the IP and port number of a peer cache in the cache cluster. The information is displayed in the following format:
|
|
Time, in seconds (including microseconds), that OracleAS Web Cache spent communicating with the origin server or peer cache. The time is the duration between the following two points of time:
This field is particularly helpful in providing time information for End-User Performance Monitoring. |
|
IP address of OracleAS Web Cache computer |
|
HTTP response header sent from OracleAS Web Cache to the browser See Also: "cs(header_name) and sc(header_name) Access Log Fields" |
|
OracleAS Web Cache-to-browser HTTP status code:
See Also: |
|
Time at which the response from OracleAS Web Cache completed. The time is displayed in the following format:
|
|
Amount of time taken, in seconds (including microseconds), for the transaction to complete |
|
User name of a basic HTTP authentication request |
|
Cache status. Cache status is reported as one of the following: |
x-cache-detail |
Diagnostic information, in the following format:
{
Example:
|
|
Cache key value, in the following format:
" |
|
Date that the response from OracleAS Web Cache completed, in the following format:
|
|
Single character that specifies the status of a cache cluster. The character is reported as one of the following: |
|
Cookie value from browser request. |
|
Date before OracleAS Web Cache received the first byte of the request, in the following format:
|
|
Date when OracleAS Web Cache sent the last byte of the response, in the following format:
|
|
ID of the specified in
See Also: "Oracle-ECID Request-Header Field" for further information about the |
|
ESI fragment log message from the
The log message only displays for requested ESI fragments in the |
|
Login user name of the client. OracleAS Web Cache is unable to obtain the value for this field. Therefore, OracleAS Web Cache displays a hyphen ( |
|
Origin server or cache cluster member that OracleAS Web Cache is forwarding the request, in the following format:
|
|
Single character that specifies if the origin server timed out on a request. The character is reported as one of the following:
An output of |
|
Protocol and version from browser request, in the following format:
|
|
Request line, in the following format:
Example: |
|
Request type. Request type is reported as one of the following:
|
|
Time, in seconds (including microseconds), that OracleAS Web Cache spent communicating with the origin server or peer cache. The time is the duration between the following two points of time:
This field is particularly helpful in providing time information for End-User Performance Monitoring. |
|
Time that OracleAS Web Cache sent the last byte of the response, in the following format:
|
|
The difference between the time the browser initiates a new connection and the time at which OracleAS Web Cache receives the first byte of the HTTP request. Note: Select this field only if instructed by Oracle Support Services. |
|
The difference between the time at which OracleAS Web Cache receives the first and last byte of the HTTP request. This field indicates the time in reading the browser requests. Note: Select this field only if instructed by Oracle Support Services. |
|
The difference between the time at which OracleAS Web Cache sends the first and last byte of the HTTP request to the origin server. This field indicates the time taken in sending the request to the origin server. Note: Select this field only if instructed by Oracle Support Services. |
|
The difference between the time at which OracleAS Web Cache receives the first and last byte of the HTTP response from the origin server. This field indicates the time taken in receiving the response from the origin server. Note: Select this field only if instructed by Oracle Support Services. |
|
The difference between the time at which OracleAS Web Cache sends the first and last byte of the HTTP response to the browser. This field indicates the time taken in sending the response to the client. Note: Select this field only if instructed by Oracle Support Services. |
|
The difference between when a request was blocked and unblocked because of garbage collection. If a request has already been sent to the origin server by OracleAS Web Cache to update an existing document, OracleAS Web Cache blocks all subsequent requests. Note: Select this field only if instructed by Oracle Support Services. |
|
The difference between when a request is queued and dequeued for the origin server. This field indicates the time a request spends in OracleAS Web Cache backend queue for an origin server (due to the maximum origin server capacity being reached) before the request is sent to the origin server for processing. Note: Select this field only if instructed by Oracle Support Services. |
|
Time before OracleAS Web Cache received the first byte of the request, in the following format:
|
Table 12-6 lists examples of HTTP/1.1 headers that can be used for the cs(
header_name
)
and sc(
header_name
)
fields. This table lists only some of the possible headers. It is not an exhaustive list.
Table 12-7 lists examples of cookie-related headers that can be used for the cs(
header_name
)
and sc(
header_name
)
fields.
cs(header_name) Field | sc(header_name) Field |
---|---|
|
|
Table 12-8 lists examples of OracleAS Web Cache headers that can be used for the cs(
header_name
)
and sc(
header_name
)
fields.
cs(header_name) Field | sc(header_name) Field |
---|---|
|
|
To establish access log configuration settings:
The Access Logs page appears.
The Edit Cache-Specific Access Log Configuration dialog box appears.
The default is $ORACLE_HOME/webcache/logs
on UNIX and ORACLE_HOME
\webcache\logs
on Windows.
With buffered logging, OracleAS Web Cache writes to the access log after the buffer is full. The buffer size is set 2048 bytes. When the limit is reached, OracleAS Web Cache writes buffered events to the access log file.
Oracle Corporation recommends disabling buffering when you need to see the access log results immediately.
The default is 10 seconds. When the interval is reached, OracleAS Web Cache writes buffered information to the access log file. Even if the buffer is not full, the access log is updated at least every 10 seconds. Oracle Corporation recommends not changing the default, unless you need to lower the interval to see results more frequently.
The Edit/Add Site Specific Access Log Configuration dialog box appears.
The default file name is access_log
.
Site-specific logging only takes effect if logging is enabled for the cache. If you select Yes, ensure that Yes is also selected for the cache in Step 3c.
log
element of <esi:environment>
or <esi:include
> in the access_log_file
.fragment
file.
If the x-esi-info
field is selected, select Log to log the events to the access_log_file
.fragment
file. If the x-esi-info
field is not selected, select Don't Log. The x-esi-info
field is automatically selected if the Format Style is WCLF.
"Format of the Access Log Files" for a description of the CLF, Combined, and WCLF formats
See Also:
access_log_file
.
yyyymmdd
and writes new log information to the current access log file.
For high-volume sites, select a policy with a high frequency.
The Edit/Add User-Defined Access Log Format dialog box displays.
Directive information typically consists of version and date information. For example:
#Version: 1.0
#Date: 12-Dec-2002 00:00:00
#Fields: c-ip x-auth-id x-clf-date cs(Host x-req-line sc-status bytes
Table 12-5 for a listing of the supported access logs fields
See Also:
cs(
header_name
)
, sc(
header_name
)
, or x-cookie(
cookie_name
)
, then enter the header or cookie name in the Header/Cookie name field.
Table 12-6, Table 12-7, and Table 12-8 for a description of the headers allowed for
See Also:
cs(
header_name
)
and sc(
header_name
)
The Edit/Add Access Log Rollover Policy dialog box appears.
access_log_file
.
yyyymmdd
and write new log information to the current access log file.
Table 12-9 describes additional configuration instructions for Weekly, Daily, and Hourly.
Policy | To configure: |
---|---|
Weekly |
|
Daily |
|
Hourly |
If you have a high-volume site, create a daily or hourly policy.
See Also:
"Rolling Over Event and Access Logs" for instructions on immediately rolling over log files |
The following code shows an excerpt of an access log file:
10.10.150.35 - - [19/Jul/2003:10:27:42 -0500] "GET /~user/personal.htm HTTP/1.1" 200 2438 10.10.150.35 - - [19/Jul/2003:10:27:54 -0500] "GET /~user/personal.htm?UserName=Bob HTTP/1.1" 200 2438 10.10.150.35 - - [19/Jul/2003:10:47:30 -0500] "GET /~user/count.sh HTTP/1.1" 403 289 10.10.150.35 - - [19/Jul/2003:10:47:34 -0500] "GET /~user/sbin/count.sh HTTP/1.1" 200 321
In the first line of the output, the fields have the following meaning:
10.10.150.35
is the browser's IP address (c-ip
)
[19/Jul/2003:10:27:42 -0500]
is the date ([x-clf-date]
)
"GET /~user/personal.htm HTTP/1.1
" is the request line ("x-req-line"
)
200
is the HTTP status code (sc-status
)
2438
is the size of the document sent (bytes
)
This section contains the following access log examples:
Except where noted otherwise, the access log examples use the CLF format:
c-ip x-log-id x-auth-id x-clf-date x-req-line sc-status bytes
The following shows an access log excerpt in which there are two Web browser reloads, followed by two shift reloads, and two more reloads:
10.10.150.35 - - [19/Nov/2002:11:04:24 -0500] "GET /cache.htm HTTP/1.1" 200 250 10.10.150.35 - - [19/Nov/2002:11:04:26 -0500] "GET /cache.htm HTTP/1.1" 200 250 10.10.150.35 - - [19/Nov/2002:11:29:24 -0500] "GET /cache.htm HTTP/1.1" 304 0 10.10.150.35 - - [19/Nov/2002:11:29:25 -0500] "GET /cache.htm HTTP/1.1" 304 0 10.10.150.35 - - [19/Nov/2002:11:29:30 -0500] "GET /cache.htm HTTP/1.1" 200 250 10.10.150.35 - - [19/Nov/2002:11:29:35 -0500] "GET /cache.htm HTTP/1.1" 200 250
The third and forth entries return an HTTP status code of 304, indicating that document has not been modified and does not need to be returned again.
The following shows an access log excerpt in which OracleAS Web Cache cannot find any objects matching the requested URL /ows-img/chalk.jpg
. This error is indicated by HTTP status code 404.
10.10.150.35 - - [19/Nov/2002:10:49:44 -0500] "GET /pls/coe/find_via_post HTTP/1.1" 200 1119 10.10.150.35 - - [19/Nov/2002:10:49:44 -0500] "GET /ows-img/chalk.jpg HTTP/1.1" 404 284
The following shows an access log excerpt in which the combined format is specified:
c-ip x-log-id x-auth-id x-clf-date x-req-line sc-status bytes cs(Referer)
cs(User-Agent)
148.87.1.180 - - [25/Jun/2003:20:09:47 +0000] "GET /manual/sections.html HTTP/1.1" 200 -1 "http://www.company.com:80/manual/mod/directive-dict.html#Syntax" "Mozilla/4.78 [ja] (Win98; U)" 148.87.1.180 - - [25/Jun/2003:20:09:50 +0000] "GET /manual/mod/core.html HTTP/1.1" 200 -1 "http://www.company.com:80/manual/sections.html" "Mozilla/4.78 [ja] (Win98; U)" 148.87.1.180 - - [25/Jun/2003:20:10:06 +0000] "GET / HTTP/1.1" 200 -1 - "Mozilla/4.78 [ja] (Win98; U)" 148.87.1.180 - - [25/Jun/2003:20:10:14 +0000] "GET /manual/LICENSE HTTP/1.1" 200 -1 "http://www.company.com:80/manual/index.html" "Mozilla/4.78 [ja] (Win98; U)"
The following shows an access log excerpt in which the following fields are specified:
c-ip x-auth-id x-clf-date
cs(Host)x-req-line sc-status bytes
cs(Host)
displays the output of Host
request-header field, which specifies the site information. In this example, requests are sent to OracleAS Web Cache for site www.company.com:80
.
148.87.1.180 - [25/Jun/2003:20:05:51 +0000] "www.company.com:80" "GET / HTTP/1.1" 200 -1 148.87.1.180 - [25/Jun/2003:20:05:56 +0000] "www.company.com:80" "GET /manual/index.html HTTP/1.1" 200 -1 148.87.1.180 - [25/Jun/2003:20:05:59 +0000] "www.company.com:80" "GET /manual/upgrading_to_1_3.html HTTP/1.1" 200 -1 148.87.1.180 - [25/Jun/2003:20:06:02 +0000] "www.company2.com:80" "GET /manual/mod/mod_dir.html HTTP/1.1" 200 -1 148.87.1.180 - [25/Jun/2003:20:06:05 +0000] "www.company2.com:80" "GET /manual/mod/directive-dict.html HTTP/1.1" 200 -1
The following shows an access log excerpt in which the following fields are specified:
c-ip x-clf-date x-req-line sc-status bytes
x-cache-detail
x-cache-detail
displays diagnostic information. In the following example:
T
means that this request is for an ESI template
H
means that this request resulted in cache hit
max-age=10+15
means that the document is to expire in 10 seconds from population and to be removed from the cache 15 seconds from the expiration. This provides a total of 25 seconds from population.
age=0
means that 0 seconds have passed since population of the cache, meaning there is 10 seconds to expiration and 15 seconds to removal
[16/Jan/2003:02:35:37 +0000] "GET /cgi-bin/esi-headers.sh?err1.htm HTTP/1.0" 200 42 TM;max-age=10+15;age=0
The following shows an access log excerpt in which the following fields are specified:
c-ip x-clf-date x-req-line sc-status bytes
x-esi-info
x-esi-info
displays log information from the log
element of <esi:environment>
or <esi:include
> tags.
[16/Jan/2003:03:03:35 +0000] "GET /b.html HTTP/1.0" 200 4 "This is a sample fragment."
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|