3com Webcache 1000 (3C16115) User Manual

Page of 176
What is Access Logging?
79
preventing you from using the Web interface.You can regain access by 
either:
Changing the client machine’s browser settings to remove the use of 
the Webcache as a proxy or
Using a browser on a client machine whose IP address is not blocked 
by Web Client Blocking to access the Web Interface.
CAUTION: If you are using Browser Auto-Configuration Files to configure 
your client machine Web browser settings, and you are using Web Client 
Blocking to control access to the Internet, you should ensure that 
Go 
Direct if no Webcache Available is not checked in the Browser 
Auto-Configuration screen. If this box is checked, the Web browser will 
bypass the Webcache entirely after reading the Browser 
Auto-Configuration file, and will never be blocked. For more information, 
see “Proxy Auto Configuration (PAC) File Scripts” on page 50
.
What is Access 
Logging?
Access Logging allows you to track which client machines have accessed 
which Web sites through the Webcache. By default Access Logging is 
disabled. If you enable Access Logging you must specify a FTP server that 
you want to periodically save the log to. The log is saved to the FTP server 
whenever the log is approaching full, or every 6 hours, whichever comes 
first. You can see a complete history of every web request made through 
the Webcache by combining all the FTPed logs; the saved logs are based 
on the standard Squid access log format and can be analyzed using 
off-the-shelf log analysis tools.
An SNMP trap is automatically generated if the Webcache fails to save 
the access log to the FTP server.
The access logs contain the following fields:
Table 10   Access Log Fields 
Field
Description
Time
A timestamp expressed as Coordinated Universal Time (UTC) with a 
millisecond resolution.
Elapsed
The amount of time in milliseconds that the Webcache took to serve 
the request.
Client
The IP address of the requesting client machine.
(continued)