Conventions Used in This Book

I use the following typesetting conventions in this book:


Used for new terms where they are defined, buttons, pages, configuration file directives, filenames, modules, ACLs, directories, and URI/URLs

Constant width

Used for configuration file examples, program output, HTTP header names and directives, scripts, options, environment variables, functions, methods, rules, keywords, libraries, and command names

Constant width italic

Used for replaceable text within examples and code pieces

Constant width bold

Used to indicate commands to be typed verbatim

When displaying a Unix command, I'll include a shell prompt, like this:

% ls -l

If the command is specific to the Bourne shell (sh) or C shell (csh), the prompt will indicate which you should use:

sh$ ulimit -a

csh% limits

If the command requires super-user privileges, the shell prompt is a hash mark:

# make install

Occasionally, I provide configuration file examples with long lines. If the line is too wide to fit on the page, it's wrapped around and indented. Squid doesn't accept this sort of syntax, so you must make sure to place everything on one line.

This icon signifies a tip, suggestion, or general note.

This icon indicates a warning or caution.

    Appendix A. Config File Reference