<p>The usage of these directives is:</p>
<pre class="prettyprint lang-config">
- Require host <var>address</var>
- Require ip <var>ip.address</var>
+Require host <var>address</var>
+Require ip <var>ip.address</var>
</pre>
board, and you want to keep them out, you could do the
following:</p>
- <div class="example"><p><code>
- Require not ip 10.252.46.165
- </code></p></div>
+ <pre class="prettyprint lang-config">Require not ip 10.252.46.165</pre>
+
<p>Visitors coming from that address will not be able to see
the content covered by this directive. If, instead, you have a
machine name, rather than an IP address, you can use that.</p>
- <div class="example"><p><code>
- Require not host <var>host.example.com</var>
- </code></p></div>
+ <pre class="prettyprint lang-config">Require not host <var>host.example.com</var></pre>
+
<p>And, if you'd like to block access from an entire domain,
you can specify just part of an address or domain name:</p>
<pre class="prettyprint lang-config">
- Require not ip <var>192.168.205</var>
- Require not host <var>phishers.example.com</var> <var>moreidiots.example</var>
- Require not gov
+Require not ip <var>192.168.205</var>
+Require not host <var>phishers.example.com</var> <var>moreidiots.example</var>
+Require not gov
</pre>
following:</p>
<pre class="prettyprint lang-config">
- <If "%{HTTP_USER_AGENT} = 'BadBot'">
- Require All Denied
- </If>
+<If "%{HTTP_USER_AGENT} = 'BadBot'">
+ Require All Denied
+</If>
</pre>
and 6am, you can do this using <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
<pre class="prettyprint lang-config">
- RewriteEngine On
- RewriteCond %{TIME_HOUR} >20 [OR]
- RewriteCond %{TIME_HOUR} <07
- RewriteRule ^/fridge - [F]
+RewriteEngine On
+RewriteCond %{TIME_HOUR} >20 [OR]
+RewriteCond %{TIME_HOUR} <07
+RewriteRule ^/fridge - [F]
</pre>
<p>The usage of these directives is:</p>
<highlight language="config">
- Require host <var>address</var>
- Require ip <var>ip.address</var>
+Require host <var>address</var>
+Require ip <var>ip.address</var>
</highlight>
<p>In the first form, <var>address</var> is a fully qualified
board, and you want to keep them out, you could do the
following:</p>
- <example>
- Require not ip 10.252.46.165
- </example>
+ <highlight language="config">Require not ip 10.252.46.165</highlight>
<p>Visitors coming from that address will not be able to see
the content covered by this directive. If, instead, you have a
machine name, rather than an IP address, you can use that.</p>
- <example>
- Require not host <var>host.example.com</var>
- </example>
+ <highlight language="config">Require not host <var>host.example.com</var></highlight>
<p>And, if you'd like to block access from an entire domain,
you can specify just part of an address or domain name:</p>
<highlight language="config">
- Require not ip <var>192.168.205</var>
- Require not host <var>phishers.example.com</var> <var>moreidiots.example</var>
- Require not gov
+Require not ip <var>192.168.205</var>
+Require not host <var>phishers.example.com</var> <var>moreidiots.example</var>
+Require not gov
</highlight>
<p>Use of the <directive
following:</p>
<highlight language="config">
- <If "%{HTTP_USER_AGENT} = 'BadBot'">
- Require All Denied
- </If>
+<If "%{HTTP_USER_AGENT} = 'BadBot'">
+ Require All Denied
+</If>
</highlight>
<note><title>Warning:</title>
and 6am, you can do this using <module>mod_rewrite</module>.</p>
<highlight language="config">
- RewriteEngine On
- RewriteCond %{TIME_HOUR} >20 [OR]
- RewriteCond %{TIME_HOUR} <07
- RewriteRule ^/fridge - [F]
+RewriteEngine On
+RewriteCond %{TIME_HOUR} >20 [OR]
+RewriteCond %{TIME_HOUR} <07
+RewriteRule ^/fridge - [F]
</highlight>
<p>This will return a 403 Forbidden response for any request after 8pm
an <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive like the
following:</p>
- <pre class="prettyprint lang-config">
- AllowOverride AuthConfig
- </pre>
+ <pre class="prettyprint lang-config">AllowOverride AuthConfig</pre>
<p>Or, if you are just going to put the directives directly in
/usr/local/apache/htdocs/secret> section.</p>
<pre class="prettyprint lang-config">
- AuthType Basic
- AuthName "Restricted Files"
- # (Following line optional)
- AuthBasicProvider file
- AuthUserFile /usr/local/apache/passwd/passwords
- Require user rbowen
+AuthType Basic
+AuthName "Restricted Files"
+# (Following line optional)
+AuthBasicProvider file
+AuthUserFile /usr/local/apache/passwd/passwords
+Require user rbowen
</pre>
look like the following:</p>
<pre class="prettyprint lang-config">
- AuthType Basic
- AuthName "By Invitation Only"
- # Optional line:
- AuthBasicProvider file
- AuthUserFile /usr/local/apache/passwd/passwords
- AuthGroupFile /usr/local/apache/passwd/groups
- Require group GroupName
+AuthType Basic
+AuthName "By Invitation Only"
+# Optional line:
+AuthBasicProvider file
+AuthUserFile /usr/local/apache/passwd/passwords
+AuthGroupFile /usr/local/apache/passwd/groups
+Require group GroupName
</pre>
specific. Rather than creating a group file, you can just use
the following directive:</p>
- <div class="example"><p><code>
- Require valid-user
- </code></p></div>
+ <pre class="prettyprint lang-config">Require valid-user</pre>
+
<p>Using that rather than the <code>Require user rbowen</code>
line will allow anyone in that is listed in the password file,
<p>To select a dbd file rather than a text file, for example:</p>
<pre class="prettyprint lang-config">
- <Directory /www/docs/private>
- AuthName "Private"
- AuthType Basic
- AuthBasicProvider dbm
- AuthDBMUserFile /www/passwords/passwd.dbm
- Require valid-user
- </Directory>
+<Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile /www/passwords/passwd.dbm
+ Require valid-user
+</Directory>
</pre>
file and LDAP based authentication providers are being used.</p>
<pre class="prettyprint lang-config">
- <Directory /www/docs/private>
- AuthName "Private"
- AuthType Basic
- AuthBasicProvider file ldap
- AuthUserFile /usr/local/apache/passwd/passwords
- AuthLDAPURL ldap://ldaphost/o=yourorg
- Require valid-user
- </Directory>
+<Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file ldap
+ AuthUserFile /usr/local/apache/passwd/passwords
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ Require valid-user
+</Directory>
</pre>
authorization as well as LDAP group authorization is being used.</p>
<pre class="prettyprint lang-config">
- <Directory /www/docs/private>
- AuthName "Private"
- AuthType Basic
- AuthBasicProvider file
- AuthUserFile /usr/local/apache/passwd/passwords
- AuthLDAPURL ldap://ldaphost/o=yourorg
- AuthGroupFile /usr/local/apache/passwd/groups
- Require group GroupName
- Require ldap-group cn=mygroup,o=yourorg
- </Directory>
+<Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file
+ AuthUserFile /usr/local/apache/passwd/passwords
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile /usr/local/apache/passwd/groups
+ Require group GroupName
+ Require ldap-group cn=mygroup,o=yourorg
+</Directory>
</pre>
that will be called during the authorization stage of the request
processing. For example:</p>
- <pre class="prettyprint lang-config">
- Require ip <var>address</var>
- </pre>
+ <pre class="prettyprint lang-config">Require ip <var>address</var></pre>
<p>where <var>address</var> is an IP address (or a partial IP
address) or:</p>
- <pre class="prettyprint lang-config">
- Require host <var>domain_name</var>
- </pre>
+ <pre class="prettyprint lang-config">Require host <var>domain_name</var></pre>
<p>where <var>domain_name</var> is a fully qualified domain name
following:</p>
<pre class="prettyprint lang-config">
- <RequireAll>
- Require all granted
- Require not ip 10.252.46.165
- </RequireAll>
+<RequireAll>
+ Require all granted
+ Require not ip 10.252.46.165
+</RequireAll>
</pre>
machine name, rather than an IP address, you can use that.</p>
<pre class="prettyprint lang-config">
- <RequireAll>
- Require all granted
- Require not host <var>host.example.com</var>
- </RequireAll>
+<RequireAll>
+ Require all granted
+ Require not host <var>host.example.com</var>
+</RequireAll>
</pre>
you can specify just part of an address or domain name:</p>
<pre class="prettyprint lang-config">
- <RequireAll>
+<RequireAll>
Require all granted
<RequireNone>
- Require ip 192.168.205
- Require host phishers.example.com moreidiots.example
- Require host ke
+ Require ip 192.168.205
+ Require host phishers.example.com moreidiots.example
+ Require host ke
</RequireNone>
- </RequireAll>
+</RequireAll>
</pre>
an <directive module="core">AllowOverride</directive> directive like the
following:</p>
- <highlight language="config">
- AllowOverride AuthConfig
- </highlight>
+ <highlight language="config">AllowOverride AuthConfig</highlight>
<p>Or, if you are just going to put the directives directly in
your main server configuration file, you will of course need to
/usr/local/apache/htdocs/secret> section.</p>
<highlight language="config">
- AuthType Basic
- AuthName "Restricted Files"
- # (Following line optional)
- AuthBasicProvider file
- AuthUserFile /usr/local/apache/passwd/passwords
- Require user rbowen
+AuthType Basic
+AuthName "Restricted Files"
+# (Following line optional)
+AuthBasicProvider file
+AuthUserFile /usr/local/apache/passwd/passwords
+Require user rbowen
</highlight>
<p>Let's examine each of those directives individually. The <directive
look like the following:</p>
<highlight language="config">
- AuthType Basic
- AuthName "By Invitation Only"
- # Optional line:
- AuthBasicProvider file
- AuthUserFile /usr/local/apache/passwd/passwords
- AuthGroupFile /usr/local/apache/passwd/groups
- Require group GroupName
+AuthType Basic
+AuthName "By Invitation Only"
+# Optional line:
+AuthBasicProvider file
+AuthUserFile /usr/local/apache/passwd/passwords
+AuthGroupFile /usr/local/apache/passwd/groups
+Require group GroupName
</highlight>
<p>Now, anyone that is listed in the group <code>GroupName</code>,
specific. Rather than creating a group file, you can just use
the following directive:</p>
- <example>
- Require valid-user
- </example>
+ <highlight language="config">Require valid-user</highlight>
<p>Using that rather than the <code>Require user rbowen</code>
line will allow anyone in that is listed in the password file,
<p>To select a dbd file rather than a text file, for example:</p>
<highlight language="config">
- <Directory /www/docs/private>
- AuthName "Private"
- AuthType Basic
- AuthBasicProvider dbm
- AuthDBMUserFile /www/passwords/passwd.dbm
- Require valid-user
- </Directory>
+<Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile /www/passwords/passwd.dbm
+ Require valid-user
+</Directory>
</highlight>
<p>Other options are available. Consult the
file and LDAP based authentication providers are being used.</p>
<highlight language="config">
- <Directory /www/docs/private>
- AuthName "Private"
- AuthType Basic
- AuthBasicProvider file ldap
- AuthUserFile /usr/local/apache/passwd/passwords
- AuthLDAPURL ldap://ldaphost/o=yourorg
- Require valid-user
- </Directory>
+<Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file ldap
+ AuthUserFile /usr/local/apache/passwd/passwords
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ Require valid-user
+</Directory>
</highlight>
<p>In this example the file provider will attempt to authenticate
authorization as well as LDAP group authorization is being used.</p>
<highlight language="config">
- <Directory /www/docs/private>
- AuthName "Private"
- AuthType Basic
- AuthBasicProvider file
- AuthUserFile /usr/local/apache/passwd/passwords
- AuthLDAPURL ldap://ldaphost/o=yourorg
- AuthGroupFile /usr/local/apache/passwd/groups
- Require group GroupName
- Require ldap-group cn=mygroup,o=yourorg
- </Directory>
+<Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file
+ AuthUserFile /usr/local/apache/passwd/passwords
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile /usr/local/apache/passwd/groups
+ Require group GroupName
+ Require ldap-group cn=mygroup,o=yourorg
+</Directory>
</highlight>
<p>To take authorization a little further, authorization container
that will be called during the authorization stage of the request
processing. For example:</p>
- <highlight language="config">
- Require ip <var>address</var>
- </highlight>
+ <highlight language="config">Require ip <var>address</var></highlight>
<p>where <var>address</var> is an IP address (or a partial IP
address) or:</p>
- <highlight language="config">
- Require host <var>domain_name</var>
- </highlight>
+ <highlight language="config">Require host <var>domain_name</var></highlight>
<p>where <var>domain_name</var> is a fully qualified domain name
(or a partial domain name); you may provide multiple addresses or
following:</p>
<highlight language="config">
- <RequireAll>
- Require all granted
- Require not ip 10.252.46.165
- </RequireAll>
+<RequireAll>
+ Require all granted
+ Require not ip 10.252.46.165
+</RequireAll>
</highlight>
<p>Visitors coming from that address will not be able to see
machine name, rather than an IP address, you can use that.</p>
<highlight language="config">
- <RequireAll>
- Require all granted
- Require not host <var>host.example.com</var>
- </RequireAll>
+<RequireAll>
+ Require all granted
+ Require not host <var>host.example.com</var>
+</RequireAll>
</highlight>
<p>And, if you'd like to block access from an entire domain,
you can specify just part of an address or domain name:</p>
<highlight language="config">
- <RequireAll>
+<RequireAll>
Require all granted
<RequireNone>
- Require ip 192.168.205
- Require host phishers.example.com moreidiots.example
- Require host ke
+ Require ip 192.168.205
+ Require host phishers.example.com moreidiots.example
+ Require host ke
</RequireNone>
- </RequireAll>
+</RequireAll>
</highlight>
<p>The above example uses the <directive module="mod_authz_core"
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision : 1328337 -->
+<!-- English Revision: 1328337:1330260 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviwed by : Vincent Deffontaines -->
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 479777:1328337 (outdated) -->
+<!-- English Revision: 479777:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 105989:1328337 (outdated) -->
+<!-- English Revision: 105989:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<variants>
<variant>en</variant>
- <variant>fr</variant>
+ <variant outdated="yes">fr</variant>
<variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
<variant outdated="yes">tr</variant>
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.tr.xsl"?>
-<!-- English Revision: 1070891:1328337 (outdated) -->
+<!-- English Revision: 1070891:1330260 (outdated) -->
<!-- =====================================================
Translated by: Umut Samuk <umut belgeler.org>
Reviewed by: Nilgün Belma Bugüner <nilgun belgeler.org>
if you would rather call the file <code>.config</code> then you
can put the following in your server configuration file:</p>
- <div class="example"><p><code>
- AccessFileName .config
- </code></p></div>
+ <pre class="prettyprint lang-config">AccessFileName .config</pre>
+
</div>
<p>In general, <code>.htaccess</code> files use the same syntax as
<div class="example"><h3>Contents of .htaccess file in
<code>/www/htdocs/example</code></h3><p><code>
- AddType text/example .exm
+ <pre class="prettyprint lang-config">AddType text/example .exm</pre>
+
</code></p></div>
<div class="example"><h3>Section from your <code>httpd.conf</code>
file</h3><p><code>
- <Directory /www/htdocs/example><br />
- <span class="indent">
- AddType text/example .exm<br />
- </span>
- </Directory>
+ <pre class="prettyprint lang-config">
+<Directory /www/htdocs/example><br />
+ AddType text/example .exm<br />
+</Directory>
+ </pre>
+
</code></p></div>
<p>However, putting this configuration in your server configuration
by setting the <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
directive to <code>none</code>:</p>
- <div class="example"><p><code>
- AllowOverride None
- </code></p></div>
+ <pre class="prettyprint lang-config">AllowOverride None</pre>
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="how" id="how">How directives are applied</a></h2>
<p>In the directory <code>/www/htdocs/example1</code> we have a
<code>.htaccess</code> file containing the following:</p>
- <div class="example"><p><code>
- Options +ExecCGI
- </code></p></div>
+ <pre class="prettyprint lang-config">Options +ExecCGI</pre>
+
<p>(Note: you must have "<code>AllowOverride Options</code>" in effect
to permit the use of the "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" directive in
<p>In the directory <code>/www/htdocs/example1/example2</code> we have
a <code>.htaccess</code> file containing:</p>
- <div class="example"><p><code>
- Options Includes
- </code></p></div>
+ <pre class="prettyprint lang-config">Options Includes</pre>
+
<p>Because of this second <code>.htaccess</code> file, in the directory
<code>/www/htdocs/example1/example2</code>, CGI execution is not
<p><code>.htaccess</code> file contents:</p>
<pre class="prettyprint lang-config">
- AuthType Basic
- AuthName "Password Required"
- AuthUserFile /www/passwords/password.file
- AuthGroupFile /www/passwords/group.file
- Require Group admins
+AuthType Basic
+AuthName "Password Required"
+AuthUserFile /www/passwords/password.file
+AuthGroupFile /www/passwords/group.file
+Require Group admins
</pre>
<code>.htaccess</code> file in the desired directory:</p>
<pre class="prettyprint lang-config">
- Options +Includes
- AddType text/html shtml
- AddHandler server-parsed shtml
+Options +Includes
+AddType text/html shtml
+AddHandler server-parsed shtml
</pre>
implemented with the following configuration:</p>
<pre class="prettyprint lang-config">
- Options +ExecCGI<br />
- AddHandler cgi-script cgi pl
+Options +ExecCGI
+AddHandler cgi-script cgi pl
</pre>
configuration:</p>
<pre class="prettyprint lang-config">
- Options +ExecCGI<br />
- SetHandler cgi-script
+Options +ExecCGI
+SetHandler cgi-script
</pre>
if you would rather call the file <code>.config</code> then you
can put the following in your server configuration file:</p>
- <example>
- AccessFileName .config
- </example>
+ <highlight language="config">AccessFileName .config</highlight>
</note>
<p>In general, <code>.htaccess</code> files use the same syntax as
<example><title>Contents of .htaccess file in
<code>/www/htdocs/example</code></title>
- AddType text/example .exm
+ <highlight language="config">AddType text/example .exm</highlight>
</example>
<example><title>Section from your <code>httpd.conf</code>
file</title>
- <Directory /www/htdocs/example><br />
- <indent>
- AddType text/example .exm<br />
- </indent>
- </Directory>
+ <highlight language="config">
+<Directory /www/htdocs/example><br />
+ AddType text/example .exm<br />
+</Directory>
+ </highlight>
</example>
<p>However, putting this configuration in your server configuration
by setting the <directive module="core">AllowOverride</directive>
directive to <code>none</code>:</p>
- <example>
- AllowOverride None
- </example>
+ <highlight language="config">AllowOverride None</highlight>
</section>
<section id="how"><title>How directives are applied</title>
<p>In the directory <code>/www/htdocs/example1</code> we have a
<code>.htaccess</code> file containing the following:</p>
- <example>
- Options +ExecCGI
- </example>
+ <highlight language="config">Options +ExecCGI</highlight>
<p>(Note: you must have "<code>AllowOverride Options</code>" in effect
to permit the use of the "<directive
<p>In the directory <code>/www/htdocs/example1/example2</code> we have
a <code>.htaccess</code> file containing:</p>
- <example>
- Options Includes
- </example>
+ <highlight language="config">Options Includes</highlight>
<p>Because of this second <code>.htaccess</code> file, in the directory
<code>/www/htdocs/example1/example2</code>, CGI execution is not
<p><code>.htaccess</code> file contents:</p>
<highlight language="config">
- AuthType Basic
- AuthName "Password Required"
- AuthUserFile /www/passwords/password.file
- AuthGroupFile /www/passwords/group.file
- Require Group admins
+AuthType Basic
+AuthName "Password Required"
+AuthUserFile /www/passwords/password.file
+AuthGroupFile /www/passwords/group.file
+Require Group admins
</highlight>
<p>Note that <code>AllowOverride AuthConfig</code> must be in effect
<code>.htaccess</code> file in the desired directory:</p>
<highlight language="config">
- Options +Includes
- AddType text/html shtml
- AddHandler server-parsed shtml
+Options +Includes
+AddType text/html shtml
+AddHandler server-parsed shtml
</highlight>
<p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
implemented with the following configuration:</p>
<highlight language="config">
- Options +ExecCGI<br />
- AddHandler cgi-script cgi pl
+Options +ExecCGI
+AddHandler cgi-script cgi pl
</highlight>
<p>Alternately, if you wish to have all files in the given directory be
configuration:</p>
<highlight language="config">
- Options +ExecCGI<br />
- SetHandler cgi-script
+Options +ExecCGI
+SetHandler cgi-script
</highlight>
<p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision : 1326216 -->
+<!-- English Revision: 1326216:1330260 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 574882:1326216 (outdated) -->
+<!-- English Revision: 574882:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 151408:1326216 (outdated) -->
+<!-- English Revision: 151408:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<variants>
<variant>en</variant>
- <variant>fr</variant>
+ <variant outdated="yes">fr</variant>
<variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
<variant outdated="yes">pt-br</variant>
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.pt-br.xsl"?>
-<!-- English Revision: 151408:1326216 (outdated) -->
+<!-- English Revision: 151408:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
assumed to be a directory path relative to the home directory of the
specified user. Given this configuration:</p>
- <div class="example"><p><code>
- UserDir public_html
- </code></p></div>
+ <pre class="prettyprint lang-config">UserDir public_html</pre>
+
<p>the URL <code>http://example.com/~rbowen/file.html</code> will be
translated to the file path
constructed using that path, plus the username specified. Given this
configuration:</p>
- <pre class="prettyprint lang-config">
- UserDir /var/html
- </pre>
+ <pre class="prettyprint lang-config">UserDir /var/html</pre>
<p>the URL <code>http://example.com/~rbowen/file.html</code> will be
in which the asterisk is replaced with the username. Given this
configuration:</p>
- <pre class="prettyprint lang-config">
- UserDir /var/www/*/docs
- </pre>
+ <pre class="prettyprint lang-config">UserDir /var/www/*/docs</pre>
<p>the URL <code>http://example.com/~rbowen/file.html</code> will be
<p>Multiple directories or directory paths can also be set.</p>
- <div class="example"><p><code>
- UserDir public_html /var/html
- </code></p></div>
+ <pre class="prettyprint lang-config">UserDir public_html /var/html</pre>
+
<p>For the URL <code>http://example.com/~rbowen/file.html</code>,
Apache will search for <code>~rbowen</code>. If it isn't found,
<p>The <code class="directive"><a href="../mod/mod_userdir.html#userdir">UserDir</a></code> directive can be
used to redirect user directory requests to external URLs.</p>
- <pre class="prettyprint lang-config">
- UserDir http://example.org/users/*/
- </pre>
+ <pre class="prettyprint lang-config">UserDir http://example.org/users/*/</pre>
<p>The above example will redirect a request for
<p>Using the syntax shown in the UserDir documentation, you can restrict
what users are permitted to use this functionality:</p>
- <pre class="prettyprint lang-config">
- UserDir disabled root jro fish
- </pre>
+ <pre class="prettyprint lang-config">UserDir disabled root jro fish</pre>
<p>The configuration above will enable the feature for all users
cgi-enabled.</p>
<pre class="prettyprint lang-config">
- <Directory /home/*/public_html/cgi-bin/>
- Options ExecCGI
- SetHandler cgi-script
- </Directory>
+<Directory /home/*/public_html/cgi-bin/>
+ Options ExecCGI
+ SetHandler cgi-script
+</Directory>
</pre>
assumed to be a directory path relative to the home directory of the
specified user. Given this configuration:</p>
- <example>
- UserDir public_html
- </example>
+ <highlight language="config">UserDir public_html</highlight>
<p>the URL <code>http://example.com/~rbowen/file.html</code> will be
translated to the file path
constructed using that path, plus the username specified. Given this
configuration:</p>
- <highlight language="config">
- UserDir /var/html
- </highlight>
+ <highlight language="config">UserDir /var/html</highlight>
<p>the URL <code>http://example.com/~rbowen/file.html</code> will be
translated to the file path <code>/var/html/rbowen/file.html</code></p>
in which the asterisk is replaced with the username. Given this
configuration:</p>
- <highlight language="config">
- UserDir /var/www/*/docs
- </highlight>
+ <highlight language="config">UserDir /var/www/*/docs</highlight>
<p>the URL <code>http://example.com/~rbowen/file.html</code> will be
translated to the file path
<p>Multiple directories or directory paths can also be set.</p>
- <example>
- UserDir public_html /var/html
- </example>
+ <highlight language="config">UserDir public_html /var/html</highlight>
<p>For the URL <code>http://example.com/~rbowen/file.html</code>,
Apache will search for <code>~rbowen</code>. If it isn't found,
<p>The <directive module="mod_userdir">UserDir</directive> directive can be
used to redirect user directory requests to external URLs.</p>
- <highlight language="config">
- UserDir http://example.org/users/*/
- </highlight>
+ <highlight language="config">UserDir http://example.org/users/*/</highlight>
<p>The above example will redirect a request for
<code>http://example.com/~bob/abc.html</code> to
<p>Using the syntax shown in the UserDir documentation, you can restrict
what users are permitted to use this functionality:</p>
- <highlight language="config">
- UserDir disabled root jro fish
- </highlight>
+ <highlight language="config">UserDir disabled root jro fish</highlight>
<p>The configuration above will enable the feature for all users
except for those listed in the <code>disabled</code> statement.
cgi-enabled.</p>
<highlight language="config">
- <Directory /home/*/public_html/cgi-bin/>
- Options ExecCGI
- SetHandler cgi-script
- </Directory>
+<Directory /home/*/public_html/cgi-bin/>
+ Options ExecCGI
+ SetHandler cgi-script
+</Directory>
</highlight>
<p>Then, presuming that <code>UserDir</code> is set to
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision : 1174747 -->
+<!-- English Revision: 1174747:1330260 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 659902:1174747 (outdated) -->
+<!-- English Revision: 659902:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 151408:1174747 (outdated) -->
+<!-- English Revision: 151408:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<variants>
<variant>en</variant>
- <variant>fr</variant>
+ <variant outdated="yes">fr</variant>
<variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
- <variant>tr</variant>
+ <variant outdated="yes">tr</variant>
</variants>
</metafile>
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.tr.xsl"?>
-<!-- English Revision: 1174747 -->
+<!-- English Revision: 1174747:1330260 (outdated) -->
<!-- =====================================================
Translated by: Nilgün Belma Bugüner <nilgun belgeler.org>
Reviewed by: Orhan Berent <berent belgeler.org>
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision : 1174747 -->
+<!-- English Revision: 1174747:1330260 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 659902:1174747 (outdated) -->
+<!-- English Revision: 659902:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 659902:1174747 (outdated) -->
+<!-- English Revision: 659902:1330260 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<variants>
<variant>en</variant>
- <variant>fr</variant>
+ <variant outdated="yes">fr</variant>
<variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
</variants>