Enabling logging for the Client Site Proxy (Standalone)

Products

• Web Security.cloud

Issue/Introduction

Newer versions of the CSP have logging turned off by default, but you can turn logging on if you need it for testing purposes. After you have finished testing, you should disable logging to prevent any issues with busy servers.

The original client site proxy (CSP) based on squid 2.5 produced cache, store, and access logs by default; however, this caused some issues with busy servers, as the amount of logging caused the CSP to fail. 

Resolution

Default Settings (Logging Disabled)

# LOGFILE PATHNAMES AND CACHE DIRECTORIES
# -----------------------------------------------------------------------------

#  TAG: emulate_httpd_log    on|off
emulate_httpd_log on

#  TAG: debug_options
debug_options ALL,1
#debug_options ALL,9

#  By default, the store and access log is disabled to avoid large size log files
cache_store_log none
access_log none
useragent_log none
#cache_log c:/ClientSiteProxy/var/logs/cache.log
#access_log C:/ClientSiteProxy/var/logs/access.log
#useragent_log c:/ClientSiteProxy/var/logs/useragent.log

To enable logging:

1. Add the comment "#" at the beginning of each line that ends with "none". e.g "#cache_store_log none"
2. Remove the comment "#" at the beginning of each log file line. e.g "cache_log c:/ClientSiteProxy/var/logs/cache.log"
3. Once the changes have been completed, restart the Client Site Proxy service.

Example:

# LOGFILE PATHNAMES AND CACHE DIRECTORIES
# -----------------------------------------------------------------------------

#  TAG: emulate_httpd_log    on|off
emulate_httpd_log on

#  TAG: debug_options
debug_options ALL,1
#debug_options ALL,9

#  By default, the store and access log is disabled to avoid large size log files
#cache_store_log none
#access_log none
#useragent_log none
cache_log c:/ClientSiteProxy/var/logs/cache.log
access_log C:/ClientSiteProxy/var/logs/access.log
useragent_log c:/ClientSiteProxy/var/logs/useragent.log

After testing has been completed, change the settings back to the default and restart the Client Site Proxy service for the changes to take effect.