# TIMEOUTS
#-----------------------------------------------------------------------------

#  TAG: connect_timeout (in seconds)
#   Some systems (notably Linux) can not be relied upon to properly
#   time out connect(2) requests.  Therefore the squid process
#   enforces its own timeout on server connections.  This parameter
#   specifies how long to wait for the connect to complete.  The
#   default is two minutes (120 seconds).
#
#connect_timeout 120

#  TAG: read_timeout (in minutes)
#   An active connection will be aborted after read_timeout minutes
#   of no activity on that connection (i.e., assume the remote server
#   or network connection died after the connection was established).
#   The default is 15 minutes.
#
#read_timeout 15

#  TAG: client_lifetime (in minutes)
#   The maximum amount of time that a client (browser) is allowed to
#   remain connected to the cache process.  This protects the Cache
#   from having alot of sockets (and hence file descriptors) tied up
#   in a CLOSE_WAIT state from remote clients that go away without
#   properly shutting down (either because of a network failure or
#   because of a poor client implementation).  The default is three
#   hours, 20 minutes.
#
#   NOTE:  The default value is designed with low-speed client
#   connections in mind.  200 minutes should be plenty of time to
#   transfer a 10M file at 1k/sec.  If you have high-speed client
#   connectivity, or occasionally run out of file descriptors,
#   we suggest you lower this value appropriately.
#
#client_lifetime 200

#  TAG: shutdown_lifetime (in seconds)
#
#   When SIGTERM or SIGHUP is received, the cache is put into
#   "shutdown pending" mode until all active sockets are closed.
#   This value is the lifetime to set for all open descriptors
#   during shutdown mode.  Any active clients after this many
#   seconds will receive a 'lifetime expire' message
#
#  TAG: shutdown_lifetime (in seconds)
#
#   Bei den Signalen SIGTERM oder SIGHUP, geht der Cache in den
#   "shutdown pending" Modus nachdem alle aktiven Sockets geschlossen wurden.
#   Dieser Wert ist die noch verbleibende Zeit fuer alle Descriptoren waehrend
#   des "Runterfahrens". Jeder aktive Client erhaelt nach dem Ablauf dieser
#   Zeit die Nachricht 'lifetime expire'.
#
#shutdown_lifetime 30