From 8c31287805462cb6769b4b267bf03f59e8403ef5 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Mon, 28 Sep 2009 09:50:31 +0200 Subject: docs: document Allow and Deny in tinyproxy.conf(5) --- docs/man5/tinyproxy.conf.txt.in | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'docs') diff --git a/docs/man5/tinyproxy.conf.txt.in b/docs/man5/tinyproxy.conf.txt.in index faa9d83..68ab02c 100644 --- a/docs/man5/tinyproxy.conf.txt.in +++ b/docs/man5/tinyproxy.conf.txt.in @@ -197,6 +197,22 @@ The possible keywords and their descriptions are as follows: In that case, setting `MaxRequestsPerChild` to a value of e.g. 1000, or 10000 can be useful. +*Allow*:: +*Deny*:: + + The `Allow` and `Deny` options provide a means to customize + which clients are allowed to access Tinyproxy. `Allow` and `Deny` + lines can be specified multiple times to build the access control + list for Tinyproxy. The order in the config file is important. + If there are no `Access` or `Deny` lines, then all clients are + allowed. Otherwise, the default action is to deny access. + The argument to `Access` or `Deny` can ba a single IP address + of a client host, like `127.0.0.1`, an IP address range, like + `192.168.0.1/24` or a string that will be matched against the + end of the client host name, i.e, this can be a full host name + like `host.example.com` or a domain name like `.example.com` or + even a top level domain name like `.com`. + BUGS ---- -- cgit v1.2.3