WELCOME TO SQUID 2.6.STABLE21

#    WELCOME TO SQUID 2.6.STABLE21
#    ----------------------------
#
#    This is the default Squid configuration file. You may wish
#    to look at the Squid home page (http://www.squid-cache.org/)
#    for the FAQ and other documentation.
#
#    The default Squid config file shows what the defaults for
#    various options happen to be.  If you don't need to change the
#    default, you shouldn't uncomment the line.  Doing so may cause
#    run-time problems.  In some cases "none" refers to no default
#    setting at all, while in other cases it refers to a valid
#    option - the comments for that keyword indicate if this is the
#    case.
#


# OPTIONS FOR AUTHENTICATION
# -----------------------------------------------------------------------------

#  TAG: auth_param
#    This is used to define parameters for the various authentication
#    schemes supported by Squid.
#
#    format: auth_param scheme parameter [setting]
#
#    The order in which authentication schemes are presented to the client is
#    dependent on the order the scheme first appears in config file. IE
#    has a bug (it's not RFC 2617 compliant) in that it will use the basic
#    scheme if basic is the first entry presented, even if more secure
#    schemes are presented. For now use the order in the recommended
#    settings section below. If other browsers have difficulties (don't
#    recognize the schemes offered even if you are using basic) either
#    put basic first, or disable the other schemes (by commenting out their
#    program entry).
#
#    Once an authentication scheme is fully configured, it can only be
#    shutdown by shutting squid down and restarting. Changes can be made on
#    the fly and activated with a reconfigure. I.E. You can change to a
#    different helper, but not unconfigure the helper completely.
#
#    Please note that while this directive defines how Squid processes
#    authentication it does not automatically activate authentication.
#    To use authentication you must in addition make use of ACLs based
#    on login name in http_access (proxy_auth, proxy_auth_regex or
#    external with %LOGIN used in the format tag). The browser will be
#    challenged for authentication on the first such acl encountered
#    in http_access processing and will also be re-challenged for new
#    login credentials if the request is being denied by a proxy_auth
#    type acl.
#
#    WARNING: authentication can't be used in a transparently intercepting
#    proxy as the client then thinks it is talking to an origin server and
#    not the proxy. This is a limitation of bending the TCP/IP protocol to
#    transparently intercepting port 80, not a limitation in Squid.
#
#    === Parameters for the basic scheme follow. ===