Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
R
radsecproxy
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Iterations
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Code Review
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
eduroam
radsecproxy
Commits
cc68bc85
Commit
cc68bc85
authored
Mar 23, 2016
by
Linus Nordberg
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix spelling.
Pointed out by Faidon Liambotis.
parent
c1028899
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
radsecproxy.conf.5.xml
radsecproxy.conf.5.xml
+4
-4
No files found.
radsecproxy.conf.5.xml
View file @
cc68bc85
...
...
@@ -2,7 +2,7 @@
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<refentry>
<refentryinfo>
<date>
2016-03-
14
</date>
<date>
2016-03-
23
</date>
</refentryinfo>
<refmeta>
<refentrytitle>
...
...
@@ -122,7 +122,7 @@ blocktype name {
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.
multiple occur
r
ences is undefined.
</para>
<variablelist>
<varlistentry>
...
...
@@ -456,7 +456,7 @@ blocktype name {
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
behaviour with multiple occur
r
ences 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
...
...
@@ -798,7 +798,7 @@ blocktype name {
trailing
<literal>
/
</literal>
after the regexp. So as an
example, if you want to use regexp matching the domain
<literal>
example.com
</literal>
you could have a realm block
named
<literal>
/@example\\.com$
</literal>
. Optinally this can
named
<literal>
/@example\\.com$
</literal>
. Opti
o
nally this can
also be written
<literal>
/@example\\.com$/
</literal>
. If you
want to match all domains under the
<literal>
.com
</literal>
top domain, you could do
<literal>
/@.*\\.com$
</literal>
. Note
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment