diff options
Diffstat (limited to 'doc/1.6/radsecproxy.conf.html')
| -rw-r--r-- | doc/1.6/radsecproxy.conf.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/1.6/radsecproxy.conf.html b/doc/1.6/radsecproxy.conf.html index ac238ae..6e6b3ff 100644 --- a/doc/1.6/radsecproxy.conf.html +++ b/doc/1.6/radsecproxy.conf.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.2 --> -<!-- CreationDate: Mon Mar 14 15:43:26 2016 --> +<!-- CreationDate: Wed Sep 21 14:01:27 2016 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -152,7 +152,7 @@ Note that blocktypes and options inside blocks are discussed later. Note that none of these options are required, and indeed in many cases they are not needed. Note that you should specify each at most once. The behaviour with -multiple occurences is undefined. <br> +multiple occurrences is undefined. <br> PidFile</p> <p style="margin-left:22%;">The PidFile option specifies @@ -390,11 +390,11 @@ useful, and it will exit if not. The tls block is required if at least one TLS/DTLS client or server is configured. Note that there can be multiple blocks for each type. For each type, the block names should be unique. The behaviour -with multiple occurences of the same name for the same block -type is undefined. Also note that some block option values -may reference a block by name, in which case the block name -must be previously defined. Hence the order of the blocks -may be significant.</p> +with multiple occurrences of the same name for the same +block type is undefined. Also note that some block option +values may reference a block by name, in which case the +block name must be previously defined. Hence the order of +the blocks may be significant.</p> <h2>CLIENT BLOCK <a name="CLIENT BLOCK"></a> @@ -690,7 +690,7 @@ done using this regexp on the value of the entire Username attribute. Optionally you may also have a trailing / after the regexp. So as an example, if you want to use regexp matching the domain example.com you could have a realm block -named /@example\\.com$. Optinally this can also be written +named /@example\\.com$. Optionally this can also be written /@example\\.com$/. If you want to match all domains under the .com top domain, you could do /@.*\\.com$. Note that since the matching is done on the entire attribute value, |