1
<?xml version="1.0" encoding="ISO-8859-1"?>
2
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
4
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5
This file is generated from xml source: DO NOT EDIT
6
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8
<title>Configuration Sections - Apache HTTP Server</title>
9
<link href="./style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10
<link href="./style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11
<link href="./style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
12
<link href="./images/favicon.ico" rel="shortcut icon" /></head>
13
<body id="manual-page"><div id="page-header">
14
<p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/directives.html">Directives</a> | <a href="./faq/">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p>
15
<p class="apache">Apache HTTP Server Version 2.2</p>
16
<img alt="" src="./images/feather.gif" /></div>
17
<div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div>
19
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="./">Version 2.2</a></div><div id="page-content"><div id="preamble"><h1>Configuration Sections</h1>
21
<p><span>Available Languages: </span><a href="./en/sections.html" title="English"> en </a> |
22
<a href="./ja/sections.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
23
<a href="./ko/sections.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
25
<p>Directives in the <a href="configuring.html">configuration files</a> may apply to the
26
entire server, or they may be restricted to apply only to particular
27
directories, files, hosts, or URLs. This document describes how to
28
use configuration section containers or <code>.htaccess</code> files
29
to change the scope of other configuration directives.</p>
31
<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#types">Types of Configuration Section Containers</a></li>
32
<li><img alt="" src="./images/down.gif" /> <a href="#file-and-web">Filesystem and Webspace</a></li>
33
<li><img alt="" src="./images/down.gif" /> <a href="#virtualhost">Virtual Hosts</a></li>
34
<li><img alt="" src="./images/down.gif" /> <a href="#proxy">Proxy</a></li>
35
<li><img alt="" src="./images/down.gif" /> <a href="#whatwhere">What Directives are Allowed?</a></li>
36
<li><img alt="" src="./images/down.gif" /> <a href="#mergin">How the sections are merged</a></li>
38
<div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
40
<h2><a name="types" id="types">Types of Configuration Section Containers</a></h2>
42
<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/core.html">core</a></code></li><li><code class="module"><a href="./mod/mod_version.html">mod_version</a></code></li><li><code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/core.html#directory"><Directory></a></code></li><li><code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code></li><li><code class="directive"><a href="./mod/core.html#files"><Files></a></code></li><li><code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code></li><li><code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code></li><li><code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code></li><li><code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code></li><li><code class="directive"><a href="./mod/core.html#location"><Location></a></code></li><li><code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code></li><li><code class="directive"><a href="./mod/mod_proxy.html#proxy"><Proxy></a></code></li><li><code class="directive"><a href="./mod/mod_proxy.html#proxymatch"><ProxyMatch></a></code></li><li><code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table>
44
<p>There are two basic types of containers. Most containers are
45
evaluated for each request. The enclosed directives are applied only
46
for those requests that match the containers. The <code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code>, <code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>, and
47
<code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code>
48
containers, on the other hand, are evaluated only at server startup
49
and restart. If their conditions are true at startup, then the
50
enclosed directives will apply to all requests. If the conditions are
51
not true, the enclosed directives will be ignored.</p>
53
<p>The <code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code> directive
54
encloses directives that will only be applied if an appropriate
55
parameter is defined on the <code class="program"><a href="./programs/httpd.html">httpd</a></code> command line. For example,
56
with the following configuration, all requests will be redirected
57
to another site only if the server is started using
58
<code>httpd -DClosedForNow</code>:</p>
60
<div class="example"><p><code>
61
<IfDefine ClosedForNow><br />
62
Redirect / http://otherserver.example.com/<br />
66
<p>The <code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>
67
directive is very similar, except it encloses directives that will
68
only be applied if a particular module is available in the server.
69
The module must either be statically compiled in the server, or it
70
must be dynamically compiled and its <code class="directive"><a href="./mod/mod_so.html#loadmodule">LoadModule</a></code> line must be earlier in the
71
configuration file. This directive should only be used if you need
72
your configuration file to work whether or not certain modules are
73
installed. It should not be used to enclose directives that you want
74
to work all the time, because it can suppress useful error messages
75
about missing modules.</p>
77
<p>In the following example, the <code class="directive"><a href="./mod/mod_mime_magic.html#mimemagicfiles">MimeMagicFiles</a></code> directive will be
78
applied only if <code class="module"><a href="./mod/mod_mime_magic.html">mod_mime_magic</a></code> is available.</p>
80
<div class="example"><p><code>
81
<IfModule mod_mime_magic.c><br />
82
MimeMagicFile conf/magic<br />
86
<p>The <code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code>
87
directive is very similar to <code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code> and <code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>, except it encloses directives that will
88
only be applied if a particular version of the server is executing. This
89
module is designed for the use in test suites and large networks which have to
90
deal with different httpd versions and different configurations.</p>
92
<div class="example"><p><code>
93
<IfVersion >= 2.1><br />
95
# this happens only in versions greater or<br />
101
<p><code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code>,
102
<code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>, and the
103
<code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code>
104
can apply negative conditions by preceding their test with "!".
105
Also, these sections can be nested to achieve more complex
107
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
108
<div class="section">
109
<h2><a name="file-and-web" id="file-and-web">Filesystem and Webspace</a></h2>
111
<p>The most commonly used configuration section containers are the
112
ones that change the configuration of particular places in the
113
filesystem or webspace. First, it is important to understand the
114
difference between the two. The filesystem is the view of your disks
115
as seen by your operating system. For example, in a default install,
116
Apache resides at <code>/usr/local/apache2</code> in the Unix
117
filesystem or <code>"c:/Program Files/Apache Group/Apache2"</code> in
118
the Windows filesystem. (Note that forward slashes should always be
119
used as the path separator in Apache, even for Windows.) In contrast,
120
the webspace is the view of your site as delivered by the web server
121
and seen by the client. So the path <code>/dir/</code> in the
122
webspace corresponds to the path
123
<code>/usr/local/apache2/htdocs/dir/</code> in the filesystem of a
124
default Apache install on Unix. The webspace need not map directly to
125
the filesystem, since webpages may be generated dynamically
126
from databases or other locations.</p>
128
<h3><a name="filesystem" id="filesystem">Filesystem Containers</a></h3>
130
<p>The <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>
131
and <code class="directive"><a href="./mod/core.html#files"><Files></a></code>
132
directives, along with their <a class="glossarylink" href="./glossary.html#regex" title="see glossary">regex</a>
133
counterparts, apply directives to
134
parts of the filesystem. Directives enclosed in a <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> section apply to
135
the named filesystem directory and all subdirectories of that
136
directory. The same effect can be obtained using <a href="howto/htaccess.html">.htaccess files</a>. For example, in the
137
following configuration, directory indexes will be enabled for the
138
<code>/var/web/dir1</code> directory and all subdirectories.</p>
140
<div class="example"><p><code>
141
<Directory /var/web/dir1><br />
142
Options +Indexes<br />
146
<p>Directives enclosed in a <code class="directive"><a href="./mod/core.html#files"><Files></a></code> section apply to any file with
147
the specified name, regardless of what directory it lies in.
148
So for example, the following configuration directives will,
149
when placed in the main section of the configuration file,
150
deny access to any file named <code>private.html</code> regardless
151
of where it is found.</p>
153
<div class="example"><p><code>
154
<Files private.html><br />
155
Order allow,deny<br />
160
<p>To address files found in a particular part of the filesystem, the
161
<code class="directive"><a href="./mod/core.html#files"><Files></a></code> and
162
<code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections
163
can be combined. For example, the following configuration will deny
164
access to <code>/var/web/dir1/private.html</code>,
165
<code>/var/web/dir1/subdir2/private.html</code>,
166
<code>/var/web/dir1/subdir3/private.html</code>, and any other instance
167
of <code>private.html</code> found under the <code>/var/web/dir1/</code>
170
<div class="example"><p><code>
171
<Directory /var/web/dir1><br />
172
<Files private.html><br />
173
Order allow,deny<br />
180
<h3><a name="webspace" id="webspace">Webspace Containers</a></h3>
182
<p>The <code class="directive"><a href="./mod/core.html#location"><Location></a></code>
183
directive and its <a class="glossarylink" href="./glossary.html#regex" title="see glossary">regex</a> counterpart, on the
184
other hand, change the
185
configuration for content in the webspace. For example, the following
186
configuration prevents access to any URL-path that begins in /private.
187
In particular, it will apply to requests for
188
<code>http://yoursite.example.com/private</code>,
189
<code>http://yoursite.example.com/private123</code>, and
190
<code>http://yoursite.example.com/private/dir/file.html</code> as well
191
as any other requests starting with the <code>/private</code> string.</p>
193
<div class="example"><p><code>
194
<Location /private><br />
195
Order Allow,Deny<br />
200
<p>The <code class="directive"><a href="./mod/core.html#location"><Location></a></code>
201
directive need not have anything to do with the filesystem.
202
For example, the following example shows how to map a particular
203
URL to an internal Apache handler provided by <code class="module"><a href="./mod/mod_status.html">mod_status</a></code>.
204
No file called <code>server-status</code> needs to exist in the
207
<div class="example"><p><code>
208
<Location /server-status><br />
209
SetHandler server-status<br />
214
<h3><a name="wildcards" id="wildcards">Wildcards and Regular Expressions</a></h3>
216
<p>The <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>,
217
<code class="directive"><a href="./mod/core.html#files"><Files></a></code>, and
218
<code class="directive"><a href="./mod/core.html#location"><Location></a></code>
219
directives can each use shell-style wildcard characters as in
220
<code>fnmatch</code> from the C standard library. The character "*"
221
matches any sequence of characters, "?" matches any single character,
222
and "[<em>seq</em>]" matches any character in <em>seq</em>. The "/"
223
character will not be matched by any wildcard; it must be specified
226
<p>If even more flexible matching is required, each
227
container has a regular expression (regex) counterpart <code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code>, <code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code>, and <code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code> that allow
229
<a class="glossarylink" href="./glossary.html#regex" title="see glossary">regular expressions</a>
230
to be used in choosing the matches. But see the section below on
231
configuration merging to find out how using regex sections will change
232
how directives are applied.</p>
234
<p>A non-regex wildcard section that changes the configuration of
235
all user directories could look as follows:</p>
237
<div class="example"><p><code>
238
<Directory /home/*/public_html><br />
239
Options Indexes<br />
243
<p>Using regex sections, we can deny access to many types of image files
245
<div class="example"><p><code>
246
<FilesMatch \.(?i:gif|jpe?g|png)$><br />
247
Order allow,deny<br />
254
<h3><a name="whichwhen" id="whichwhen">What to use When</a></h3>
256
<p>Choosing between filesystem containers and webspace containers is
257
actually quite easy. When applying directives to objects that reside
258
in the filesystem always use <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> or <code class="directive"><a href="./mod/core.html#files"><Files></a></code>. When applying directives to objects
259
that do not reside in the filesystem (such as a webpage generated from
260
a database), use <code class="directive"><a href="./mod/core.html#location"><Location></a></code>.</p>
262
<p>It is important to never use <code class="directive"><a href="./mod/core.html#location"><Location></a></code> when trying to restrict
263
access to objects in the filesystem. This is because many
264
different webspace locations (URLs) could map to the same filesystem
265
location, allowing your restrictions to be circumvented.
266
For example, consider the following configuration:</p>
268
<div class="example"><p><code>
269
<Location /dir/><br />
270
Order allow,deny<br />
275
<p>This works fine if the request is for
276
<code>http://yoursite.example.com/dir/</code>. But what if you are on
277
a case-insensitive filesystem? Then your restriction could be easily
278
circumvented by requesting
279
<code>http://yoursite.example.com/DIR/</code>. The <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> directive, in
280
contrast, will apply to any content served from that location,
281
regardless of how it is called. (An exception is filesystem links.
282
The same directory can be placed in more than one part of the
283
filesystem using symbolic links. The <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> directive will follow the symbolic
284
link without resetting the pathname. Therefore, for the highest level
285
of security, symbolic links should be disabled with the appropriate
286
<code class="directive"><a href="./mod/core.html#options">Options</a></code> directive.)</p>
288
<p>If you are, perhaps, thinking that none of this applies to you
289
because you use a case-sensitive filesystem, remember that there are
290
many other ways to map multiple webspace locations to the same
291
filesystem location. Therefore you should always use the filesystem
292
containers when you can. There is, however, one exception to this
293
rule. Putting configuration restrictions in a <code><Location
294
/></code> section is perfectly safe because this section will apply
295
to all requests regardless of the specific URL.</p>
298
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
299
<div class="section">
300
<h2><a name="virtualhost" id="virtualhost">Virtual Hosts</a></h2>
302
<p>The <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code>
303
container encloses directives that apply to specific hosts.
304
This is useful when serving multiple hosts from the same machine
305
with a different configuration for each. For more information,
306
see the <a href="vhosts/">Virtual Host Documentation</a>.</p>
307
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
308
<div class="section">
309
<h2><a name="proxy" id="proxy">Proxy</a></h2>
311
<p>The <code class="directive"><a href="./mod/mod_proxy.html#proxy"><Proxy></a></code>
312
and <code class="directive"><a href="./mod/mod_proxy.html#proxymatch"><ProxyMatch></a></code>
313
containers apply enclosed configuration directives only
314
to sites accessed through <code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code>'s proxy server
315
that match the specified URL. For example, the following configuration
316
will prevent the proxy server from being used to access the
317
<code>cnn.com</code> website.</p>
319
<div class="example"><p><code>
320
<Proxy http://cnn.com/*><br />
321
Order allow,deny<br />
325
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
326
<div class="section">
327
<h2><a name="whatwhere" id="whatwhere">What Directives are Allowed?</a></h2>
329
<p>To find out what directives are allowed in what types of
330
configuration sections, check the <a href="mod/directive-dict.html#Context">Context</a> of the directive.
331
Everything that is allowed in
332
<code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>
333
sections is also syntactically allowed in
334
<code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code>,
335
<code class="directive"><a href="./mod/core.html#files"><Files></a></code>,
336
<code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code>,
337
<code class="directive"><a href="./mod/core.html#location"><Location></a></code>,
338
<code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code>,
339
<code class="directive"><a href="./mod/mod_proxy.html#proxy"><Proxy></a></code>,
340
and <code class="directive"><a href="./mod/mod_proxy.html#proxymatch"><ProxyMatch></a></code>
341
sections. There are some exceptions, however:</p>
344
<li>The <code class="directive"><a href="./mod/core.html#allowoverride">AllowOverride</a></code> directive
345
works only in <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>
348
<li>The <code>FollowSymLinks</code> and
349
<code>SymLinksIfOwnerMatch</code> <code class="directive"><a href="./mod/core.html#options">Options</a></code> work only in <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections or
350
<code>.htaccess</code> files.</li>
352
<li>The <code class="directive"><a href="./mod/core.html#options">Options</a></code> directive cannot
353
be used in <code class="directive"><a href="./mod/core.html#files"><Files></a></code>
354
and <code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code>
357
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
358
<div class="section">
359
<h2><a name="mergin" id="mergin">How the sections are merged</a></h2>
361
<p>The configuration sections are applied in a very particular order.
362
Since this can have important effects on how configuration directives
363
are interpreted, it is important to understand how this works.</p>
365
<p>The order of merging is:</p>
368
<li> <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> (except regular expressions)
369
and <code>.htaccess</code> done simultaneously (with
370
<code>.htaccess</code>, if allowed, overriding
371
<code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>)</li>
373
<li><code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code>
374
(and <code><Directory ~></code>)</li>
376
<li><code class="directive"><a href="./mod/core.html#files"><Files></a></code> and <code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code> done
379
<li><code class="directive"><a href="./mod/core.html#location"><Location></a></code>
380
and <code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code> done simultaneously</li>
383
<p>Apart from <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>, each group is processed in
384
the order that they appear in the configuration files. <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> (group 1 above)
385
is processed in the order shortest directory component to longest.
386
So for example, <code><Directory /var/web/dir></code> will
387
be processed before <code><Directory
388
/var/web/dir/subdir></code>. If multiple <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections apply
389
to the same directory they are processed in the configuration file
390
order. Configurations included via the <code class="directive"><a href="./mod/core.html#include">Include</a></code> directive will be treated as if
391
they were inside the including file at the location of the
392
<code class="directive"><a href="./mod/core.html#include">Include</a></code> directive.</p>
394
<p>Sections inside <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code> sections
395
are applied <em>after</em> the corresponding sections outside
396
the virtual host definition. This allows virtual hosts to
397
override the main server configuration.</p>
399
<p>When the request is served by <code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code>, the
400
<code class="directive"><a href="./mod/mod_proxy.html#proxy"><Proxy></a></code>
401
container takes the place of the <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> container in the processing
404
<p>Later sections override earlier ones.</p>
406
<div class="note"><h3>Technical Note</h3>
408
<code><Location></code>/<code><LocationMatch></code>
409
sequence performed just before the name translation phase
410
(where <code>Aliases</code> and <code>DocumentRoots</code>
411
are used to map URLs to filenames). The results of this
412
sequence are completely thrown away after the translation has
416
<h3><a name="merge-examples" id="merge-examples">Some Examples</a></h3>
418
<p>Below is an artificial example to show the order of
419
merging. Assuming they all apply to the request, the directives in
420
this example will be applied in the order A > B > C > D >
423
<div class="example"><p><code>
424
<Location /><br />
426
</Location><br />
428
<Files f.html><br />
432
<VirtualHost *><br />
433
<Directory /a/b><br />
435
</Directory><br />
436
</VirtualHost><br />
438
<DirectoryMatch "^.*b$"><br />
440
</DirectoryMatch><br />
442
<Directory /a/b><br />
444
</Directory><br />
448
<p>For a more concrete example, consider the following. Regardless of
449
any access restrictions placed in <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections, the <code class="directive"><a href="./mod/core.html#location"><Location></a></code> section will be
450
evaluated last and will allow unrestricted access to the server. In
451
other words, order of merging is important, so be careful!</p>
453
<div class="example"><p><code>
454
<Location /><br />
455
Order deny,allow<br />
457
</Location><br />
459
# Woops! This <Directory> section will have no effect<br />
460
<Directory /><br />
461
Order allow,deny<br />
463
Deny from badguy.example.com<br />
470
<div class="bottomlang">
471
<p><span>Available Languages: </span><a href="./en/sections.html" title="English"> en </a> |
472
<a href="./ja/sections.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
473
<a href="./ko/sections.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
474
</div><div id="footer">
475
<p class="apache">Copyright 2006 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
476
<p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/directives.html">Directives</a> | <a href="./faq/">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p></div>
b'\\ No newline at end of file'
added
removed
docs/manual/sections.html.en
