[deployment-guide/comm-rel: 524/727] Moved the Location directive description.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 13:08:59 UTC 2010
commit afb945ca10db46b87bc24008ca025e5b02722123
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Aug 31 12:39:30 2010 +0200
Moved the Location directive description.
en-US/The_Apache_HTTP_Server.xml | 64 +++++++++++++++++++-------------------
1 files changed, 32 insertions(+), 32 deletions(-)
---
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index e2fb81f..987bdce 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -1251,38 +1251,6 @@ ErrorDocument 404 /404-not_found.html</screen>
<para>
<command>IndexOptions</command> has a number of other parameters which can be set to control the appearance of server generated directories. The <command>IconHeight</command> and <command>IconWidth</command> parameters require the server to include HTML <command>HEIGHT</command> and <command>WIDTH</command> tags for the icons in server generated webpages. The <command>IconsAreLinks</command> parameter combines the graphical icon with the HTML link anchor, which contains the URL link target.
</para>
- <formalpara id="s2-apache-location">
- <title>Location</title>
- <indexterm>
- <primary><command>Location</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>Location</command></secondary>
- </indexterm>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>server status reports</secondary>
- </indexterm>
- <para>
- The <command><Location></command> and <command></Location></command> tags create a container in which access control based on URL can be specified.
- </para>
- </formalpara>
- <para>
- For instance, to allow people connecting from within the server's domain to see status reports, use the following directives:
- </para>
- <screen><command><Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from <replaceable><.example.com></replaceable> </Location></command></screen>
- <para>
- Replace <replaceable><.example.com></replaceable> with the second-level domain name for the Web server.
- </para>
- <para>
- To provide server configuration reports (including installed modules and configuration directives) to requests from inside the domain, use the following directives:
- </para>
- <screen><command><Location /server-info> SetHandler server-info Order deny,allow Deny from all Allow from <replaceable><.example.com></replaceable> </Location></command></screen>
- <para>
- Again, replace <replaceable><.example.com></replaceable> with the second-level domain name for the Web server.
- </para>
<formalpara id="s2-apache-logformat">
<title>LogFormat</title>
<indexterm>
@@ -1903,6 +1871,38 @@ ErrorDocument 404 /404-not_found.html</screen>
<para>
For more information about Apache HTTP Server modules, refer to <xref linkend="s1-apache-addmods" />.
</para>
+ <formalpara id="s2-apache-location">
+ <title>Location</title>
+ <indexterm>
+ <primary><command>Location</command></primary>
+ <secondary>Apache configuration directive</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>configuration directives, Apache</primary>
+ <secondary><command>Location</command></secondary>
+ </indexterm>
+ <indexterm>
+ <primary>Apache HTTP Server</primary>
+ <secondary>server status reports</secondary>
+ </indexterm>
+ <para>
+ The <command><Location></command> and <command></Location></command> tags create a container in which access control based on URL can be specified.
+ </para>
+ </formalpara>
+ <para>
+ For instance, to allow people connecting from within the server's domain to see status reports, use the following directives:
+ </para>
+ <screen><command><Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from <replaceable><.example.com></replaceable> </Location></command></screen>
+ <para>
+ Replace <replaceable><.example.com></replaceable> with the second-level domain name for the Web server.
+ </para>
+ <para>
+ To provide server configuration reports (including installed modules and configuration directives) to requests from inside the domain, use the following directives:
+ </para>
+ <screen><command><Location /server-info> SetHandler server-info Order deny,allow Deny from all Allow from <replaceable><.example.com></replaceable> </Location></command></screen>
+ <para>
+ Again, replace <replaceable><.example.com></replaceable> with the second-level domain name for the Web server.
+ </para>
</section>
<section id="s2-apache-sslcommands">
<title>Configuration Directives for SSL</title>
More information about the docs-commits
mailing list