Re: [squid-users] "log_fqdn on" and "logformat" aren't included in the conf. file ?

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Wed, 04 Jun 2014 20:57:38 +1200

On 4/06/2014 11:51 a.m., Nidal Shater wrote:
>
> I have install squid on my centos 6.5 using yum, the following is the content of the squid.conf
>
> #
> # Recommended minimum configuration:
> #
> acl manager proto cache_object
> acl localhost src 127.0.0.1/32 ::1
> acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
>
> # Example rule allowing access from your local networks.
> # Adapt to list your (internal) IP networks from where browsing
> # should be allowed
> acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
> acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
> acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
> acl localnet src fc00::/7 # RFC 4193 local private network range
> acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
>
> acl SSL_ports port 443
> acl Safe_ports port 80 # http
> acl Safe_ports port 21 # ftp
> acl Safe_ports port 443 # https
> acl Safe_ports port 70 # gopher
> acl Safe_ports port 210 # wais
> acl Safe_ports port 1025-65535 # unregistered ports
> acl Safe_ports port 280 # http-mgmt
> acl Safe_ports port 488 # gss-http
> acl Safe_ports port 591 # filemaker
> acl Safe_ports port 777 # multiling http
> acl CONNECT method CONNECT
>
> #
> # Recommended minimum Access Permission configuration:
> #
> # Only allow cachemgr access from localhost
> http_access allow manager localhost
> http_access deny manager
>
> # Deny requests to certain unsafe ports
> http_access deny !Safe_ports
>
> # Deny CONNECT to other than secure SSL ports
> http_access deny CONNECT !SSL_ports
>
> # We strongly recommend the following be uncommented to protect innocent
> # web applications running on the proxy server who think the only
> # one who can access services on "localhost" is a local user
> #http_access deny to_localhost
>
> #
> # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
> #
>
> # Example rule allowing access from your local networks.
> # Adapt localnet in the ACL section to list your (internal) IP networks
> # from where browsing should be allowed
> http_access allow localnet
> http_access allow localhost
>
> # And finally deny all other access to this proxy
> http_access deny all
>
> # Squid normally listens to port 3128
> http_port 3128
>
> # We recommend you to use at least the following line.
> hierarchy_stoplist cgi-bin ?
>
> # Uncomment and adjust the following to add a disk cache directory.
> #cache_dir ufs /var/spool/squid 100 16 256
>
> # Leave coredumps in the first cache dir
> coredump_dir /var/spool/squid
>
> # Add any of your own refresh_pattern entries above these.
> refresh_pattern ^ftp: 1440 20% 10080
> refresh_pattern ^gopher: 1440 0% 1440
> refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
> refresh_pattern . 0 20% 4320
>
>
> My questions are :
> 1 - why there isn'any "log_fqdn on" option

There are hundreds of configuration directives, most of which are able
to be given sensible** defaults. There is no need for them to be in the
config file and confusing you.
 You can visit http://www.squid-cache.org/Doc/config/ for the full list
at any time you want to find something. There should also be a
squid.conf.documented file installed somewhere on your machine with the
full list and documentation of each directive.

** Relative to when they were last updated anyway.

> 2- why there isn't "logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt" option

It is abuilt-in definition and does not need re-defiing. Also, the above
is provided as documentation to explain what the native fields order and
content it. The actual native log syntax has a few differences in some
value ranges from the above format.

> 3- I have tried to add it to the conf. file above but when I did it the squid failed to restart

Please run the command "squid -k check" after changing the config file
and before reconfiguring the running Squid instance. That verifies the
config and displays helpful hints about any problems found.

Amos
Received on Wed Jun 04 2014 - 08:58:06 MDT

This archive was generated by hypermail 2.2.0 : Thu Jun 05 2014 - 12:00:05 MDT