February 2011
Intermediate to advanced
332 pages
9h 3m
English
We learned in Chapter 3 that we should always test our configuration file for errors or warnings before deploying it on the production servers. Squid provides the command-line option -k parse using which the configuration file can be parsed quickly.
However, successful parsing of the configuration file doesn't guarantee that Squid will be able to allow or deny the requests or replies in the manner we are expecting. As the configuration files grows in size, the number ACL lists and corresponding rules keeps on increasing, which may sometimes lead to confusion. To test the access control in our new configuration file, we can use the squidclient program.
For this purpose, we'll either need a different test server ...
Read now
Unlock full access