summaryrefslogtreecommitdiffstats
path: root/docs/manual/howto/htaccess.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-07 15:01:30 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-07 15:01:30 +0000
commit6beeb1b708550be0d4a53b272283e17e5e35fe17 (patch)
tree1ce8673d4aaa948e5554000101f46536a1e4cc29 /docs/manual/howto/htaccess.html
parentInitial commit. (diff)
downloadapache2-6beeb1b708550be0d4a53b272283e17e5e35fe17.tar.xz
apache2-6beeb1b708550be0d4a53b272283e17e5e35fe17.zip
Adding upstream version 2.4.57.upstream/2.4.57upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r--docs/manual/howto/htaccess.html25
-rw-r--r--docs/manual/howto/htaccess.html.en465
-rw-r--r--docs/manual/howto/htaccess.html.es464
-rw-r--r--docs/manual/howto/htaccess.html.fr.utf8512
-rw-r--r--docs/manual/howto/htaccess.html.ja.utf8417
-rw-r--r--docs/manual/howto/htaccess.html.ko.euc-kr363
-rw-r--r--docs/manual/howto/htaccess.html.pt-br407
7 files changed, 2653 insertions, 0 deletions
diff --git a/docs/manual/howto/htaccess.html b/docs/manual/howto/htaccess.html
new file mode 100644
index 0000000..1e6a6f0
--- /dev/null
+++ b/docs/manual/howto/htaccess.html
@@ -0,0 +1,25 @@
+# GENERATED FROM XML -- DO NOT EDIT
+
+URI: htaccess.html.en
+Content-Language: en
+Content-type: text/html; charset=UTF-8
+
+URI: htaccess.html.es
+Content-Language: es
+Content-type: text/html; charset=ISO-8859-1
+
+URI: htaccess.html.fr.utf8
+Content-Language: fr
+Content-type: text/html; charset=UTF-8
+
+URI: htaccess.html.ja.utf8
+Content-Language: ja
+Content-type: text/html; charset=UTF-8
+
+URI: htaccess.html.ko.euc-kr
+Content-Language: ko
+Content-type: text/html; charset=EUC-KR
+
+URI: htaccess.html.pt-br
+Content-Language: pt-br
+Content-type: text/html; charset=ISO-8859-1
diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en
new file mode 100644
index 0000000..e16fc1f
--- /dev/null
+++ b/docs/manual/howto/htaccess.html.en
@@ -0,0 +1,465 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Apache HTTP Server Tutorial: .htaccess files - Apache HTTP Server Version 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
+<p class="apache">Apache HTTP Server Version 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.4</a> &gt; <a href="./">How-To / Tutorials</a></div><div id="page-content"><div id="preamble"><h1>Apache HTTP Server Tutorial: .htaccess files</h1>
+<div class="toplang">
+<p><span>Available Languages: </span><a href="../en/howto/htaccess.html" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div>
+
+<p><code>.htaccess</code> files provide a way to make configuration
+changes on a per-directory basis.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">.htaccess files</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#what">What they are/How to use them</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#when">When (not) to use .htaccess files</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#how">How directives are applied</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#auth">Authentication example</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Server Side Includes example</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#rewrite">Rewrite Rules in .htaccess files</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI example</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">Troubleshooting</a></li>
+</ul><h3>See also</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">.htaccess files</a></h2>
+ <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_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li></ul></td></tr></table>
+
+ <div class="note">You should avoid using <code>.htaccess</code> files completely if you have access to
+ httpd main server config file. Using <code>.htaccess</code> files slows down your Apache http server.
+ Any directive that you can include in a <code>.htaccess</code> file is better set in a <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> block, as it will have the same effect with better performance.</div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="what" id="what">What they are/How to use them</a></h2>
+
+
+ <p><code>.htaccess</code> files (or "distributed configuration files")
+ provide a way to make configuration changes on a per-directory basis. A
+ file, containing one or more configuration directives, is placed in a
+ particular document directory, and the directives apply to that
+ directory, and all subdirectories thereof.</p>
+
+ <div class="note"><h3>Note:</h3>
+ <p>If you want to call your <code>.htaccess</code> file something
+ else, you can change the name of the file using the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code> directive. For example,
+ if you would rather call the file <code>.config</code> then you
+ can put the following in your server configuration file:</p>
+
+ <pre class="prettyprint lang-config">AccessFileName ".config"</pre>
+
+ </div>
+
+ <p>In general, <code>.htaccess</code> files use the same syntax as
+ the <a href="../configuring.html#syntax">main configuration
+ files</a>. What you can put in these files is determined by the
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive. This
+ directive specifies, in categories, what directives will be
+ honored if they are found in a <code>.htaccess</code> file. If a
+ directive is permitted in a <code>.htaccess</code> file, the
+ documentation for that directive will contain an Override section,
+ specifying what value must be in <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> in order for that
+ directive to be permitted.</p>
+
+ <p>For example, if you look at the documentation for the <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>
+ directive, you will find that it is permitted in <code>.htaccess</code>
+ files. (See the Context line in the directive summary.) The <a href="../mod/directive-dict.html#Context">Override</a> line reads
+ <code>FileInfo</code>. Thus, you must have at least
+ <code>AllowOverride FileInfo</code> in order for this directive to be
+ honored in <code>.htaccess</code> files.</p>
+
+ <div class="example"><h3>Example:</h3><table>
+ <tr>
+ <td><a href="../mod/directive-dict.html#Context">Context:</a></td>
+ <td>server config, virtual host, directory, .htaccess</td>
+ </tr>
+
+ <tr>
+ <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
+ <td>FileInfo</td>
+ </tr>
+ </table></div>
+
+ <p>If you are unsure whether a particular directive is permitted in a
+ <code>.htaccess</code> file, look at the documentation for that
+ directive, and check the Context line for ".htaccess".</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="when" id="when">When (not) to use .htaccess files</a></h2>
+
+ <p>In general, you should only use <code>.htaccess</code> files when
+ you don't have access to the main server configuration file. There is,
+ for example, a common misconception that user authentication should
+ always be done in <code>.htaccess</code> files, and, in more recent years,
+ another misconception that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> directives
+ must go in <code>.htaccess</code> files. This is simply not the
+ case. You can put user authentication configurations in the main server
+ configuration, and this is, in fact, the preferred way to do
+ things. Likewise, <code>mod_rewrite</code> directives work better,
+ in many respects, in the main server configuration.</p>
+
+ <p><code>.htaccess</code> files should be used in a case where the
+ content providers need to make configuration changes to the server on a
+ per-directory basis, but do not have root access on the server system.
+ In the event that the server administrator is not willing to make
+ frequent configuration changes, it might be desirable to permit
+ individual users to make these changes in <code>.htaccess</code> files
+ for themselves. This is particularly true, for example, in cases where
+ ISPs are hosting multiple user sites on a single machine, and want
+ their users to be able to alter their configuration.</p>
+
+ <p>However, in general, use of <code>.htaccess</code> files should be
+ avoided when possible. Any configuration that you would consider
+ putting in a <code>.htaccess</code> file, can just as effectively be
+ made in a <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> section in your main server
+ configuration file.</p>
+
+ <p>There are two main reasons to avoid the use of
+ <code>.htaccess</code> files.</p>
+
+ <p>The first of these is performance. When <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ is set to allow the use of <code>.htaccess</code> files, httpd will
+ look in every directory for <code>.htaccess</code> files. Thus,
+ permitting <code>.htaccess</code> files causes a performance hit,
+ whether or not you actually even use them! Also, the
+ <code>.htaccess</code> file is loaded every time a document is
+ requested.</p>
+
+ <p>Further note that httpd must look for <code>.htaccess</code> files
+ in all higher-level directories, in order to have a full complement of
+ directives that it must apply. (See section on <a href="#how">how
+ directives are applied</a>.) Thus, if a file is requested out of a
+ directory <code>/www/htdocs/example</code>, httpd must look for the
+ following files:</p>
+
+ <div class="example"><p><code>
+ /.htaccess<br />
+ /www/.htaccess<br />
+ /www/htdocs/.htaccess<br />
+ /www/htdocs/example/.htaccess
+ </code></p></div>
+
+ <p>And so, for each file access out of that directory, there are 4
+ additional file-system accesses, even if none of those files are
+ present. (Note that this would only be the case if
+ <code>.htaccess</code> files were enabled for <code>/</code>, which
+ is not usually the case.)</p>
+
+ <p>In the case of <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives, in
+ <code>.htaccess</code> context these regular expressions must be
+ re-compiled with every request to the directory, whereas in main
+ server configuration context they are compiled once and cached.
+ Additionally, the rules themselves are more complicated, as one must
+ work around the restrictions that come with per-directory context
+ and <code>mod_rewrite</code>. Consult the <a href="../rewrite/intro.html#htaccess">Rewrite Guide</a> for more
+ detail on this subject.</p>
+
+ <p>The second consideration is one of security. You are permitting
+ users to modify server configuration, which may result in changes over
+ which you have no control. Carefully consider whether you want to give
+ your users this privilege. Note also that giving users less
+ privileges than they need will lead to additional technical support
+ requests. Make sure you clearly tell your users what level of
+ privileges you have given them. Specifying exactly what you have set
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> to, and pointing them
+ to the relevant documentation, will save yourself a lot of confusion
+ later.</p>
+
+ <p>Note that it is completely equivalent to put a <code>.htaccess</code>
+ file in a directory <code>/www/htdocs/example</code> containing a
+ directive, and to put that same directive in a Directory section
+ <code>&lt;Directory "/www/htdocs/example"&gt;</code> in your main server
+ configuration:</p>
+
+ <p><code>.htaccess</code> file in <code>/www/htdocs/example</code>:</p>
+
+ <div class="example"><h3>Contents of .htaccess file in
+ <code>/www/htdocs/example</code></h3><pre class="prettyprint lang-config">AddType text/example ".exm"</pre>
+</div>
+
+ <div class="example"><h3>Section from your <code>httpd.conf</code>
+ file</h3><pre class="prettyprint lang-config">&lt;Directory "/www/htdocs/example"&gt;
+ AddType text/example ".exm"
+&lt;/Directory&gt;</pre>
+</div>
+
+ <p>However, putting this configuration in your server configuration
+ file will result in less of a performance hit, as the configuration is
+ loaded once when httpd starts, rather than every time a file is
+ requested.</p>
+
+ <p>The use of <code>.htaccess</code> files can be disabled completely
+ by setting the <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ directive to <code>none</code>:</p>
+
+ <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>The configuration directives found in a <code>.htaccess</code> file
+ are applied to the directory in which the <code>.htaccess</code> file
+ is found, and to all subdirectories thereof. However, it is important
+ to also remember that there may have been <code>.htaccess</code> files
+ in directories higher up. Directives are applied in the order that they
+ are found. Therefore, a <code>.htaccess</code> file in a particular
+ directory may override directives found in <code>.htaccess</code> files
+ found higher up in the directory tree. And those, in turn, may have
+ overridden directives found yet higher up, or in the main server
+ configuration file itself.</p>
+
+ <p>Example:</p>
+
+ <p>In the directory <code>/www/htdocs/example1</code> we have a
+ <code>.htaccess</code> file containing the following:</p>
+
+ <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
+ <code>.htaccess</code> files.)</p>
+
+ <p>In the directory <code>/www/htdocs/example1/example2</code> we have
+ a <code>.htaccess</code> file containing:</p>
+
+ <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
+ permitted, as only <code>Options Includes</code> is in effect, which
+ completely overrides any earlier setting that may have been in
+ place.</p>
+
+ <h3><a name="merge" id="merge">Merging of .htaccess with the main
+ configuration files</a></h3>
+
+ <p>As discussed in the documentation on <a href="../sections.html">Configuration Sections</a>,
+ <code>.htaccess</code> files can override the <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> sections for
+ the corresponding directory, but will be overridden by other types
+ of configuration sections from the main configuration files. This
+ fact can be used to enforce certain configurations, even in the
+ presence of a liberal <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> setting. For example, to
+ prevent script execution while allowing anything else to be set in
+ <code>.htaccess</code> you can use:</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/htdocs"&gt;
+ AllowOverride All
+&lt;/Directory&gt;
+
+&lt;Location "/"&gt;
+ Options +IncludesNoExec -ExecCGI
+&lt;/Location&gt;</pre>
+
+
+ <div class="note">This example assumes that your <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> is <code>/www/htdocs</code>.</div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="auth" id="auth">Authentication example</a></h2>
+
+ <p>If you jumped directly to this part of the document to find out how
+ to do authentication, it is important to note one thing. There is a
+ common misconception that you are required to use
+ <code>.htaccess</code> files in order to implement password
+ authentication. This is not the case. Putting authentication directives
+ in a <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>
+ section, in your main server configuration file, is the preferred way
+ to implement this, and <code>.htaccess</code> files should be used only
+ if you don't have access to the main server configuration file. See <a href="#when">above</a> for a discussion of when you should and should
+ not use <code>.htaccess</code> files.</p>
+
+ <p>Having said that, if you still think you need to use a
+ <code>.htaccess</code> file, you may find that a configuration such as
+ what follows may work for you.</p>
+
+ <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</pre>
+
+
+ <p>Note that <code>AllowOverride AuthConfig</code> must be in effect
+ for these directives to have any effect.</p>
+
+ <p>Please see the <a href="auth.html">authentication tutorial</a> for a
+ more complete discussion of authentication and authorization.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ssi" id="ssi">Server Side Includes example</a></h2>
+
+ <p>Another common use of <code>.htaccess</code> files is to enable
+ Server Side Includes for a particular directory. This may be done with
+ the following configuration directives, placed in a
+ <code>.htaccess</code> file in the desired directory:</p>
+
+ <pre class="prettyprint lang-config">Options +Includes
+AddType text/html shtml
+AddHandler server-parsed shtml</pre>
+
+
+ <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
+ FileInfo</code> must both be in effect for these directives to have any
+ effect.</p>
+
+ <p>Please see the <a href="ssi.html">SSI tutorial</a> for a more
+ complete discussion of server-side includes.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="rewrite" id="rewrite">Rewrite Rules in .htaccess files</a></h2>
+<p>When using <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> in
+<code>.htaccess</code> files, be aware that the per-directory context
+changes things a bit. In particular, rules are taken to be relative to
+the current directory, rather than being the original requested URI.
+Consider the following examples:</p>
+
+<pre class="prettyprint lang-config"># In httpd.conf
+RewriteRule "^/images/(.+)\.jpg" "/images/$1.png"
+
+# In .htaccess in root dir
+RewriteRule "^images/(.+)\.jpg" "images/$1.png"
+
+# In .htaccess in images/
+RewriteRule "^(.+)\.jpg" "$1.png"</pre>
+
+
+<p>In a <code>.htaccess</code> in your document directory, the leading
+slash is removed from the value supplied to <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, and in the
+<code>images</code> subdirectory, <code>/images/</code> is removed from
+it. Thus, your regular expression needs to omit that portion as
+well.</p>
+
+<p>Consult the <a href="../rewrite/">mod_rewrite documentation</a> for
+further details on using <code>mod_rewrite</code>.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="cgi" id="cgi">CGI example</a></h2>
+
+ <p>Finally, you may wish to use a <code>.htaccess</code> file to permit
+ the execution of CGI programs in a particular directory. This may be
+ implemented with the following configuration:</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI
+AddHandler cgi-script cgi pl</pre>
+
+
+ <p>Alternately, if you wish to have all files in the given directory be
+ considered to be CGI programs, this may be done with the following
+ configuration:</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI
+SetHandler cgi-script</pre>
+
+
+ <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
+ FileInfo</code> must both be in effect for these directives to have any
+ effect.</p>
+
+ <p>Please see the <a href="cgi.html">CGI tutorial</a> for a more
+ complete discussion of CGI programming and configuration.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="troubleshoot" id="troubleshoot">Troubleshooting</a></h2>
+
+ <p>When you put configuration directives in a <code>.htaccess</code>
+ file, and you don't get the desired effect, there are a number of
+ things that may be going wrong.</p>
+
+ <p>Most commonly, the problem is that <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> is not
+ set such that your configuration directives are being honored. Make
+ sure that you don't have a <code>AllowOverride None</code> in effect
+ for the file scope in question. A good test for this is to put garbage
+ in your <code>.htaccess</code> file and reload the page. If a server error is
+ not generated, then you almost certainly have <code>AllowOverride
+ None</code> in effect.</p>
+
+ <p>If, on the other hand, you are getting server errors when trying to
+ access documents, check your httpd error log. It will likely tell you
+ that the directive used in your <code>.htaccess</code> file is not
+ permitted.</p>
+
+ <div class="example"><p><code>
+ [Fri Sep 17 18:43:16 2010] [alert] [client 192.168.200.51] /var/www/html/.htaccess: DirectoryIndex not allowed here
+ </code></p></div>
+
+ <p>This will indicate either that you've used a directive that is
+ never permitted in <code>.htaccess</code> files, or that you simply
+ don't have <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> set to
+ a level sufficient for the directive you've used. Consult the
+ documentation for that particular directive to determine which is
+ the case.</p>
+
+ <p>Alternately, it may tell you that you had a syntax error in your
+ usage of the directive itself.</p>
+
+ <div class="example"><p><code>
+ [Sat Aug 09 16:22:34 2008] [alert] [client 192.168.200.51] /var/www/html/.htaccess: RewriteCond: bad flag delimiters
+ </code></p></div>
+
+ <p>In this case, the error message should be specific to the
+ particular syntax error that you have committed.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>Available Languages: </span><a href="../en/howto/htaccess.html" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/htaccess.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 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>
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/htaccess.html.es b/docs/manual/howto/htaccess.html.es
new file mode 100644
index 0000000..ad63d84
--- /dev/null
+++ b/docs/manual/howto/htaccess.html.es
@@ -0,0 +1,464 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head>
+<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Tutorial del Servidor Apache HTTP: Ficheros .htaccess - Servidor HTTP Apache Versi&#243;n 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">M&#243;dulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa del sitio web</a></p>
+<p class="apache">Versi&#243;n 2.4 del Servidor HTTP Apache</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">Servidor HTTP</a> &gt; <a href="http://httpd.apache.org/docs/">Documentaci&#243;n</a> &gt; <a href="../">Versi&#243;n 2.4</a> &gt; <a href="./">How-To / Tutoriales</a></div><div id="page-content"><div id="preamble"><h1>Tutorial del Servidor Apache HTTP: Ficheros .htaccess</h1>
+<div class="toplang">
+<p><span>Idiomas disponibles: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Portugu&#234;s (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div>
+
+ <p>Los ficheros <code>.htaccess</code> facilitan una forma de realizar
+ cambios en la configuraci&#243;n en contexto directorio.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">Ficheros .htaccess</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#what">Qu&#233; son/C&#243;mo usarlos</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#when">Cuando (no) usar ficheros .htaccess</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#how">How directives are applied</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#auth">Ejemplo de Autenticaci&#243;n</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Ejemplo de Server Side Includes</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#rewrite">Reglas de Rewrite en ficheros .htaccess</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#cgi">Ejemplo de CGI</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">Resoluci&#243;n de problemas</a></li>
+</ul><h3>Consulte tambi&#233;n</h3><ul class="seealso"><li><a href="#comments_section">Comentarios</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">Ficheros .htaccess</a></h2>
+ <table class="related"><tr><th>M&#243;dulos Relacionados</th><th>Directivas Relacionadas</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_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li></ul></td></tr></table>
+
+ <div class="note">Deber&#237;a evitar usar ficheros <code>.htaccess</code> completamente si
+ tiene acceso al fichero de configuraci&#243;n principal de httpd. Usar ficheros
+ <code>.htaccess</code> ralentiza su servidor Apache http. Cualquier
+ directiva que pueda incluir en un fichero <code>.htaccess</code>
+ estar&#225; mejor configurada dentro de una secci&#243;n
+ <code class="directive"><a href="../mod/core.html#directory">Directory</a></code>, tendr&#225; el mismo efecto y
+ mejor rendimiento.</div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="what" id="what">Qu&#233; son/C&#243;mo usarlos</a></h2>
+
+
+ <p>Los ficheros <code>.htaccess</code> (o "ficheros de configuraci&#243;n
+ distribuida") facilitan una forma de realizar cambios en la configuraci&#243;n
+ en contexto directorio. Un fichero, que contiene una o m&#225;s directivas, se
+ coloca en un documento espec&#237;fico de un directorio, y estas directivas
+ aplican a ese directorio y todos sus subdirectorios.</p>
+
+ <div class="note"><h3>Nota:</h3>
+ <p>Si quiere llamar a su fichero <code>.htaccess</code> de otra manera,
+ puede cambiar el nombre del fichero usando la directiva <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code>. Por ejemplo, si usted prefiere
+ llamar al fichero <code>.config</code>, entonces puede poner lo siguiente
+ en el fichero de configuraci&#243;n de su servidor:</p>
+
+ <pre class="prettyprint lang-config">AccessFileName ".config"</pre>
+
+ </div>
+
+ <p>Generalmente, los ficheros <code>.htaccess</code> usan la misma sint&#225;xis
+ que los <a href="../configuring.html#syntax">ficheros de la configuraci&#243;n
+ principal</a>. Lo que puede utilizar en estos ficheros lo determina la
+ directiva <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>. Esta directiva
+ especifica, en categor&#237;as, qu&#233; directivas tendr&#225;n efecto si se encuentran en
+ un fichero <code>.htaccess</code>. Si se permite una directiva en un fichero
+ <code>.htaccess</code>, la documentaci&#243;n para esa directiva contendr&#225; una
+ secci&#243;n Override, especificando qu&#233; valor debe ir en
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> para que se permita esa
+ directiva.</p>
+
+ <p>Por ejemplo, si busca en la documentaci&#243;n la directiva <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>, encontrar&#225; que se permite en
+ ficheros <code>.htaccess</code>. (Vea la l&#237;nea de Contexto en el sumario de
+ la directiva.) La l&#237;nea <a href="../mod/directive-dict.html#Context">Override</a> muestra
+ <code>FileInfo</code>. De este modo, debe tener al menos
+ <code>AllowOverride FileInfo</code> para que esta directiva se aplique en
+ ficheros <code>.htaccess</code>.</p>
+
+ <div class="example"><h3>Ejemplo:</h3><table>
+ <tr>
+ <td><a href="../mod/directive-dict.html#Context">Context:</a></td>
+ <td>server config, virtual host, directory, .htaccess</td>
+ </tr>
+
+ <tr>
+ <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
+ <td>FileInfo</td>
+ </tr>
+ </table></div>
+
+ <p>Si no est&#225; seguro de cu&#225;ndo, una directiva en concreto, se puede usar en un
+ fichero <code>.htaccess</code>, consulte la documentaci&#243;n para esa directiva,
+ y compruebe la l&#237;nea Context buscando ".htaccess".</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="when" id="when">Cuando (no) usar ficheros .htaccess</a></h2>
+
+ <p>Generalmente, solo deber&#237;a usar ficheros <code>.htaccess</code> cuando no
+ tiene acceso al fichero principal de configuraci&#243;n del servidor. Hay, por
+ ejemplo, una creencia err&#243;nea de que la autenticaci&#243;n de usuario deber&#237;a
+ hacerse siempre dentro de ficheros <code>.htaccess</code>, y, m&#225;s recientemente, otra creencia err&#243;nea de que las directivas de
+ <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> deben ir en ficheros <code>.htaccess</code>.
+ Esto sencillamente no es el caso. Puede poner las configuraciones de
+ autenticaci&#243;n de usuario en la configuraci&#243;n principal del servidor, y esto
+ es de hecho, el m&#233;todo preferido de configurar Apache. Del mismo modo, las
+ directivas <code>mod_rewrite</code> funcionan mejor, en muchos sentidos, en
+ el fichero de configuraci&#243;n principal del servidor.</p>
+
+ <p>Los ficheros <code>.htaccess</code> deber&#237;an usarse cuando su proveedor
+ de contenidos le permite hacer modificaciones de configuraci&#243;n
+ en contexto directorio, pero usted no tiene acceso de root en el servidor.
+ En el caso de que el administrador no est&#233; dispuesto a hacer cambios
+ frecuentes en la configuraci&#243;n, puede que sea necesario permitir a usuarios
+ individuales realizar estos cambios de configuraci&#243;n en ficheros
+ <code>.htaccess</code> por ellos mismos. Lo cual ocurre a menudo, por
+ ejemplo, en casos donde los ISP est&#225;n albergando m&#250;ltiples sitios web de
+ usuario en una sola m&#225;quina, y quieren que sus usuarios tengan la
+ posibilidad de modificar sus configuraciones.</p>
+
+ <p>Aun as&#237;, generalmente, el uso de ficheros <code>.htaccess</code> deber&#237;a
+ evitarse cuando sea posible. Cualquier configuraci&#243;n que considerar&#237;a poner
+ en un fichero <code>.htaccess</code>, puede usarse con la misma efectividad
+ en una secci&#243;n <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> en el fichero de configuraci&#243;n
+ del servidor.</p>
+
+ <p>Hay dos razones para evitar el uso de ficheros <code>.htaccess</code>.</p>
+
+ <p>La primera es el rendimiento. Cuando <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ est&#225; configurado para permitir el uso de ficheros <code>.htaccess</code>,
+ httpd buscar&#225; ficheros <code>.htaccess</code> en cada directorio. As&#237;,
+ permitiendo ficheros <code>.htaccess</code> provoca una p&#233;rdida de
+ rendimiento, &#161;incluso aunque no los use! Adem&#225;s, los ficheros
+ <code>.htaccess</code> se cargan cada vez que se solicita un documento.</p>
+
+ <p>Adem&#225;s tenga en cuenta que httpd debe buscar ficheros
+ <code>.htaccess</code> en todos los directorios de mayor jerarqu&#237;a,
+ para poder terner la lista completa de directivas que debe aplicar. (Vea
+ la secci&#243;n sobre <a href="#how">C&#243;mo se aplican las directivas</a>.) As&#237;, si
+ se solicita un fichero de un directorio <code>/www/htdocs/example</code>,
+ httpd debe buscar los siguientes ficheros:</p>
+
+ <div class="example"><p><code>
+ /.htaccess<br />
+ /www/.htaccess<br />
+ /www/htdocs/.htaccess<br />
+ /www/htdocs/example/.htaccess
+ </code></p></div>
+
+ <p>De esta manera, por cada acceso a un fichero de ese directorio, hay 4
+ accesos adicionales al sistema de ficheros, incluso si ninguno de esos
+ ficheros est&#225; presente. (Tenga en cuenta que este caso solo se dar&#237;a si los
+ ficheros <code>.htaccess</code> est&#225;n activados en <code>/</code>, que
+ generalmente no es el caso.).</p>
+
+ <p>En el caso de las directivas <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, en el contexto de
+ <code>.htaccess</code> estas expresiones regulares deben recompilarse con
+ cada solicitud a ese directorio, cuando en el contexto de configuraci&#243;n del
+ servidor solo se compilan una vez y se cachean. Adicionalmente, las reglas
+ en s&#237; mismas son m&#225;s complicadas, puesto que uno debe sortear las
+ restricciones que vienen acompa&#241;adas del contexto directorio y
+ <code>mod_rewrite</code>. Consulte la <a href="../rewrite/intro.html#htaccess">Gu&#237;a de Rewrite</a> para un mayor
+ detalle sobre este tema.</p>
+
+ <p>La segunda consideraci&#243;n es de seguridad. Estar&#225; permitiendo que usuarios
+ modifiquen la configuraci&#243;n del servidor, lo cual puede dar lugar a cambios sobre los que usted no tendr&#225; ning&#250;n control. Medite profundamente si debe
+ dar a sus usuarios ese privilegio. Adem&#225;s tenga en cuenta que dar a los usuarios menos privilegios de los que necesitan dar&#225; lugar a m&#225;s peticiones
+ de soporte. Aseg&#250;rese de que le indica a sus usuarios claramente el nivel de privilegios que les est&#225; dando. Especificando exactamente c&#243;mo ha
+ configurado <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>, e inv&#237;teles
+ a revisar la documentaci&#243;n relacionada, lo cual le ahorrar&#225;
+ bastantes confusiones m&#225;s adelante.</p>
+
+ <p>Tenga en cuenta que esto es equivalente por completo a poner un fichero
+ <code>.htaccess</code> en un directorio <code>/www/htdocs/example</code>
+ con una directiva, y poner la misma directiva en una secci&#243;n
+ Directory <code>&lt;Directory "/www/htdocs/example"&gt;</code> en su
+ configuraci&#243;n principal del servidor:</p>
+
+ <p>Fichero <code>.htaccess</code> en <code>/www/htdocs/example</code>:</p>
+
+ <div class="example"><h3>Contenido de fichero .htaccess en
+ <code>/www/htdocs/example</code></h3><pre class="prettyprint lang-config">AddType text/example ".exm"</pre>
+</div>
+
+ <div class="example"><h3>Secci&#243;n de su fichero <code>httpd.conf</code></h3><pre class="prettyprint lang-config">&lt;Directory "/www/htdocs/example"&gt;
+ AddType text/example ".exm"
+&lt;/Directory&gt;</pre>
+</div>
+
+ <p>Aun as&#237;, poniendo &#233;sta en el fichero de configuraci&#243;n dar&#225; como resultado
+ una menor p&#233;rdida de rendimiento, y como la configuraci&#243;n se carga una vez
+ cuando el httpd arranca, en lugar de cada vez que se solicita un fichero.</p>
+
+ <p>El uso de ficheros <code>.htaccess</code> puede desactivarse por completo
+ configurando la directiva <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ a <code>none</code>:</p>
+
+ <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>Las directivas de configuraci&#243;n que se encuentran en el fichero
+ <code>.htaccess</code> se aplican al directorio en el que el fichero
+ <code>.htaccess</code> se encuentra, y a todos sus subdirectorios. Sin
+ embargo, es importante recordar que puede haber otros ficheros
+ <code>.htaccess</code> en directorios previos. Las directivas se aplican en
+ el orden en el que se encuentran. Por lo tanto, un fichero
+ <code>.htaccess</code> puede sobrescribir directivas que se encuentran
+ en ficheros <code>.htaccess</code> que se encuentran en directorios previos
+ del &#225;rbol de directorios. Y estos, en cambio, pueden haber sobrescrito
+ directivas que se encontraban m&#225;s arriba, o en el fichero principal de
+ configuraci&#243;n del servidor mismo.</p>
+
+ <p>Ejemplo:</p>
+
+ <p>En el directorio <code>/www/htdocs/example1</code> tenemos un fichero
+ <code>.htaccess</code> que contiene lo siguiente:</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI</pre>
+
+
+ <p>(Nota: debe terner "<code>AllowOverride Options</code>" configurado para
+ permitir el uso de la directiva "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" en ficheros
+ <code>.htaccess</code> files.)</p>
+
+ <p>En el directorio <code>/www/htdocs/example1/example2</code> tenemos un
+ fichero <code>.htaccess</code> que contiene:</p>
+
+ <pre class="prettyprint lang-config">Options Includes</pre>
+
+
+ <p>Por este segundo fichero <code>.htaccess</code>, en el directorio
+ <code>/www/htdocs/example1/example2</code>, la ejecuci&#243;n de CGI execution no
+ est&#225; permitida, porque solo se ha definido <code>Options Includes</code>,
+ que sobrescribe completamente una configuraci&#243;n previa que se pudiera haber
+ definido.</p>
+
+ <h3><a name="merge" id="merge">Incorporando el .htaccess en los ficheros de
+ configuraci&#243;n principal</a></h3>
+
+ <p>Como se ha comentado en la documentaci&#243;n en las <a href="../sections.html">Secciones de Configuraci&#243;n</a>, los ficheros
+ <code>.htaccess</code> pueden sobrescribir las secciones <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> por el directorio
+ correspondiente, pero se sobrescribir&#225;n por otros tipos de secciones de
+ configuraci&#243;n de los ficheros de configuraci&#243;n principal. Este hecho se
+ puede usar para forzar ciertas configuraciones, incluso en presencia
+ de una configuraci&#243;n laxa de
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>. Por ejemplo, para
+ prevenir la ejecuci&#243;n de un script mientras se permite cualquier otra cosa
+ en <code>.htaccess</code> puede usar:</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/htdocs"&gt;
+ AllowOverride All
+&lt;/Directory&gt;
+
+&lt;Location "/"&gt;
+ Options +IncludesNoExec -ExecCGI
+&lt;/Location&gt;</pre>
+
+
+ <div class="note">Este ejemplo asume que su <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> es <code>/www/htdocs</code>.</div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="auth" id="auth">Ejemplo de Autenticaci&#243;n</a></h2>
+
+ <p>Si salt&#243; directamente a esta parte del documento para averiguar como
+ hacer la autenticaci&#243;n, es important que tenga en cuenta una cosa. Hay una
+ creencia err&#243;nea de que necesita usar ficheros <code>.htaccess</code> para
+ configurar autenticaci&#243;n con contrase&#241;a. Este no es el caso. Colocar las
+ directivas de autenticaci&#243;n en una secci&#243;n
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>, en su fichero
+ de configuraci&#243;n principal, es el m&#233;todo recomendado para configurar esto,
+ y los ficheros <code>.htaccess</code> deber&#237;an usarse solamente si no tiene
+ acceso al fichero de configuraci&#243;n principal del servidor. Vea <a href="#when">m&#225;s arriba</a> una explicaci&#243;n de cuando deber&#237;a y cuando no
+ deber&#237;a usar ficheros <code>.htaccess</code>.</p>
+
+ <p>Dicho esto, si todav&#237;a cree que debe usar el fichero
+ <code>.htaccess</code>, podr&#225; ver que una configuraci&#243;n como la que sigue
+ podr&#237;a servirle.</p>
+
+ <p>Contenido del fichero <code>.htaccess</code>:</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "Password Required"
+AuthUserFile "/www/passwords/password.file"
+AuthGroupFile "/www/passwords/group.file"
+Require group admins</pre>
+
+
+ <p>Tenga en cuenta que <code>AllowOverride AuthConfig</code> debe estar
+ habilitado para que estas directivas tengan alg&#250;n efecto.</p>
+
+ <p>Por favor vea el <a href="auth.html">tutorial de autenticaci&#243;n</a> para
+ una explicaci&#243;n m&#225;s completa de la autenticaci&#243;n y la autorizaci&#243;n.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ssi" id="ssi">Ejemplo de Server Side Includes</a></h2>
+
+ <p>Otro uso com&#250;n de ficheros <code>.htaccess</code> es activar Server Side
+ Includes para un directorio en particular. Esto puede hacerse
+ con las siguientes directivas de configuraci&#243;n, colocadas en un fichero
+ <code>.htaccess</code> y el directorio deseado:</p>
+
+ <pre class="prettyprint lang-config">Options +Includes
+AddType text/html "shtml"
+AddHandler server-parsed shtml</pre>
+
+
+ <p>Tenga en cuenta que <code>AllowOverride Options</code> y
+ <code>AllowOverride FileInfo</code> deben estar activadas para que estas
+ directivas tengan efecto.</p>
+
+ <p>Por favor vea el <a href="ssi.html">tutorial de SSI</a> para una
+ explicaci&#243;n m&#225;s completa de server-side includes.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="rewrite" id="rewrite">Reglas de Rewrite en ficheros .htaccess</a></h2>
+ <p>Cuando use <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> en
+ ficheros <code>.htaccess</code>, tenga en cuenta que el contexto
+ directorio cambia las cosas un poco. En concreto, las reglas son
+ relativas al directorio actual, en lugar de serlo de la petici&#243;n de URI
+ solicitada originalmente.
+ Considere los siguientes ejemplos:</p>
+
+<pre class="prettyprint lang-config"># En httpd.conf
+RewriteRule "^/images/(.+)\.jpg" "/images/$1.png"
+
+# En .htaccess en el directorio ra&#237;z
+RewriteRule "^images/(.+)\.jpg" "images/$1.png"
+
+# En .htaccess en images/
+RewriteRule "^(.+)\.jpg" "$1.png"</pre>
+
+
+ <p>En un <code>.htaccess</code> en cualquier directorio del DocumentRoot, la
+ barra ("/") inicial se elimina del valor facilitado a <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, y en el subdirectorio
+ <code>images</code>, se elimina <code>/images/</code> tambi&#233;n de este valor.
+ As&#237;, su expresi&#243;n regular necesita omitir tambi&#233;n esa parte.</p>
+
+ <p>Consulte la <a href="../rewrite/">documentaci&#243;n de mod_rewrite</a> para
+ m&#225;s detalles al usar <code>mod_rewrite</code>.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="cgi" id="cgi">Ejemplo de CGI</a></h2>
+
+ <p>Finalmente, puede que quiera usar un fichero <code>.htaccess</code> para
+ permitir la ejecuci&#243;n de programas CGI en un directorio en particular. Esto
+ se puede implementar con la siguiente configuraci&#243;n:</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI
+AddHandler cgi-script "cgi" "pl"</pre>
+
+
+ <p>Alternativamente, si quiere considerar como programas CGI todos los
+ ficheros de un directorio concreto, esto se puede conseguir con la siguiente
+ configuraci&#243;n:</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI
+SetHandler cgi-script</pre>
+
+
+ <p>Tenga en cuenta que <code>AllowOverride Options</code> y
+ <code>AllowOverride FileInfo</code> deben estar ambas activadas para que
+ estas directivas tengan efecto.</p>
+
+ <p>Por favor vea el <a href="cgi.html">tutorial CGI</a> para mayor detalle
+ sobre programaci&#243;n y configuraci&#243;n de CGI.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="troubleshoot" id="troubleshoot">Resoluci&#243;n de problemas</a></h2>
+
+ <p>Cuando pone directivas en un fichero <code>.htaccess</code> y no obtiene
+ el efecto deseado hay una serie de cosas que pueden haber ido mal.</p>
+
+ <p>El problema m&#225;s com&#250;n es que <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride
+ </a></code> no est&#225; configurada para que sus directivas puedan surtir
+ efecto. Aseg&#250;rese de que no tiene <code>AllowOverride None</code>
+ configurado para el directorio en cuesti&#243;n. Una buena forma de probar esto
+ es poner "basura" en su fichero <code>.htaccess</code> y recargar la p&#225;gina.
+ Si no se genera un error en el servidor, casi seguro que tiene configurado
+ <code>AllowOverride None</code>.</p>
+
+ <p>Si, por otro lado, obtiene errores de servidor al intentar acceder a
+ documentos, compruebe el log de errores de httpd. Seguramente le indiquen
+ que la directiva en uso en su fichero <code>.htaccess</code> no est&#225;
+ permitida.</p>
+
+ <div class="example"><p><code>
+ [Fri Sep 17 18:43:16 2010] [alert] [client 192.168.200.51] /var/www/html/.htaccess: DirectoryIndex not allowed here
+ </code></p></div>
+
+ <p>Esto indicar&#225; que o bien ha usado una directiva que no se permite nunca
+ en ficheros <code>.htaccess</code>, o que simplementa no tiene
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> configurado
+ a un nivel suficiente para la directiva que ha usado. Consulte la
+ documentaci&#243;n para esa directiva en particular para determinar cual es el
+ caso.</p>
+
+ <p>Alternativamente, puede que le indique que hay un error de sintaxis en
+ el uso de la propia directiva.</p>
+
+ <div class="example"><p><code>
+ [Sat Aug 09 16:22:34 2008] [alert] [client 192.168.200.51] /var/www/html/.htaccess: RewriteCond: bad flag delimiters
+ </code></p></div>
+
+ <p>En este caso, el mensaje de error deber&#237;a ser espec&#237;fico para el error de
+ sintaxis concreto que ha cometido.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>Idiomas disponibles: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Portugu&#234;s (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comentarios</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/htaccess.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licencia bajo los t&#233;rminos de la <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">M&#243;dulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa del sitio web</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/htaccess.html.fr.utf8 b/docs/manual/howto/htaccess.html.fr.utf8
new file mode 100644
index 0000000..2b71c5b
--- /dev/null
+++ b/docs/manual/howto/htaccess.html.fr.utf8
@@ -0,0 +1,512 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="fr" xml:lang="fr"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Tutoriel du serveur HTTP Apache : fichiers .htaccess - Serveur HTTP Apache Version 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p>
+<p class="apache">Serveur HTTP Apache Version 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">Serveur HTTP</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.4</a> &gt; <a href="./">Recettes / Tutoriels</a></div><div id="page-content"><div id="preamble"><h1>Tutoriel du serveur HTTP Apache : fichiers .htaccess</h1>
+<div class="toplang">
+<p><span>Langues Disponibles: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" title="Français">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div>
+
+<p>Les fichiers <code>.htaccess</code> fournissent une méthode pour
+modifier la configuration du serveur au niveau de chaque répertoire.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">Fichiers .htaccess</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#what">Que sont ce fichiers, comment les utiliser ?</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#when">Quand doit-on (ne doit-on pas) utiliser
+ les fichiers .htaccess ?</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#how">Comment sont appliquées les directives ?</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#auth">Exemple d'authentification</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Exemple d'Inclusion Côté Serveur (Server Side
+Includes - SSI)</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#rewrite">Les règles de réécriture dans les fichiers .htaccess</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#cgi">Exemple de CGI</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">Résolution des problèmes</a></li>
+</ul><h3>Voir aussi</h3><ul class="seealso"><li><a href="#comments_section">Commentaires</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">Fichiers .htaccess</a></h2>
+
+ <table class="related"><tr><th>Modules Apparentés</th><th>Directives Apparentées</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_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li></ul></td></tr></table>
+ <div class="note">Les fichiers <code>.htaccess</code> ne doivent être utilisés
+ que si vous n'avez pas accès au fichier de configuration du serveur
+ principal. L'utilisation des fichiers <code>.htaccess</code>
+ ralentit le fonctionnement de votre serveur HTTP Apache. Il est toujours
+ préférable de définir les directives que vous pouvez inclure dans un
+ fichier <code>.htaccess</code> dans une section <code class="directive"><a href="../mod/core.html#directory">Directory</a></code>, car elles produiront le
+ même effet avec de meilleures performances.</div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="what" id="what">Que sont ce fichiers, comment les utiliser ?</a></h2>
+
+
+ <p>Les fichiers <code>.htaccess</code> (ou "fichiers de
+ configuration distribués") fournissent une méthode pour modifier la
+ configuration du serveur au niveau d'un répertoire. Un fichier,
+ contenant une ou plusieurs directives de configuration, est placé
+ dans un répertoire de documents particulier, et ses directives
+ s'appliquent à ce répertoire et à tous ses sous-répertoires.</p>
+
+ <div class="note"><h3>Note :</h3>
+ <p>Si vous voulez donner un autre nom à votre fichier
+ <code>.htaccess</code>, vous pouvez le faire en utilisant la
+ directive <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code>. Par
+ exemple, si vous préférez nommer votre fichier
+ <code>.config</code>, vous pouvez mettre ceci dans le fichier de
+ configuration de votre serveur :</p>
+
+ <pre class="prettyprint lang-config">AccessFileName ".config"</pre>
+
+ </div>
+
+ <p>En général, les fichiers <code>.htaccess</code> utilisent la même
+ syntaxe que les <a href="../configuring.html#syntax">fichiers de
+ configuration principaux</a>. Ce que vous pouvez mettre dans ces
+ fichier est déterminé par la directive <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>. Cette directive spécifie,
+ sous forme de catégories, quelles directives seront traitées si
+ elles se trouvent dans un fichier <code>.htaccess</code>. Si une
+ directive est permise dans un fichier <code>.htaccess</code> file,
+ la documentation de cette directive contiendra une section Override,
+ spécifiant quelle valeur doit prendre <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> pour que cette directive
+ soit traitée.</p>
+
+ <p>Par exemple, si vous regardez la documentation de la directive
+ <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>, vous verrez
+ que cette dernière est permise dans les fichiers
+ <code>.htaccess</code> (Voir la ligne de contexte dans le résumé de
+ la directive). La ligne <a href="../mod/directive-dict.html#Context">Override</a> indique
+ <code>FileInfo</code>. Vous devez donc avoir au moins
+ <code>AllowOverride FileInfo</code> pour que cette directive soit
+ traitée dans les fichiers <code>.htaccess</code>.</p>
+
+ <div class="example"><h3>Exemple :</h3><table>
+ <tr>
+ <td><a href="../mod/directive-dict.html#Context">Contexte :</a></td>
+ <td>configuration du serveur, serveur virtuel, directory, .htaccess</td>
+ </tr>
+
+ <tr>
+ <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
+ <td>FileInfo</td>
+ </tr>
+ </table></div>
+
+ <p>Si vous n'êtes pas sûr qu'une directive particulière soit permise
+ dans un fichier <code>.htaccess</code>, lisez la documentation de
+ cette directive, et consultez la ligne de contexte pour
+ ".htaccess".</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="when" id="when">Quand doit-on (ne doit-on pas) utiliser
+ les fichiers .htaccess ?</a></h2>
+
+ <p>En principe, vous ne devriez utiliser les fichiers
+ <code>.htaccess</code> que lorsque vous n'avez pas accès au fichier de
+ configuration du serveur principal. Par exemple, la fausse
+ idée
+ selon laquelle l'authentification de l'utilisateur devrait toujours
+ être faite dans les fichiers <code>.htaccess</code> est très
+ répandue. Il est aussi souvent avancé, ces dernières
+ années, que les directives de <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> doivent
+ être définies dans les fichiers <code>.htaccess</code>. Ceci est
+ tout simplement faux. Vous pouvez configurer
+ l'authentification des utilisateurs au niveau de la configuration du
+ serveur principal, et c'est en fait cette méthode qui doit être
+ privilégiée. De même, les directives de
+ <code>mod_rewrite</code> fonctionneront mieux, à de nombreux égards,
+ dans le contexte du serveur principal.</p>
+
+ <p>Les fichiers <code>.htaccess</code> ne devraient être utilisés
+ que dans le cas où les fournisseurs de contenu ont besoin de
+ modifier la configuration du serveur au niveau d'un répertoire, mais
+ ne possèdent pas l'accès root sur le système du serveur. Si
+ l'administrateur du serveur ne souhaite pas effectuer des
+ modifications de configuration incessantes, il peut être intéressant
+ de permettre aux utilisateurs isolés d'effectuer eux-mêmes ces
+ modifications par le biais de fichiers <code>.htaccess</code>. Ceci
+ est particulièrement vrai dans le cas où le fournisseur d'accès à
+ Internet héberge de nombreux sites d'utilisateurs sur un seul
+ serveur, et souhaite que ces utilisateurs puissent modifier
+ eux-mêmes leurs configurations.</p>
+
+ <p>Cependant et d'une manière générale, il vaut mieux éviter
+ d'utiliser les fichiers <code>.htaccess</code>. Tout élément de
+ configuration que vous pourriez vouloir mettre dans un fichier
+ <code>.htaccess</code>, peut aussi être mis, et avec la même
+ efficacité, dans une section <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> du fichier de configuration de
+ votre serveur principal.</p>
+
+ <p>Il y a deux raisons principales d'éviter l'utilisation des
+ fichiers <code>.htaccess</code>.</p>
+
+ <p>La première est liée aux performances. Lorsque la directive
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> est définie de
+ façon à autoriser l'utilisation des fichiers <code>.htaccess</code>,
+ httpd va rechercher leur présence dans chaque répertoire. Ainsi,
+ permettre l'utilisation des fichiers <code>.htaccess</code> est déjà
+ en soi une cause de dégradation des performances, que vous utilisiez
+ effectivement ces fichiers ou non ! De plus, le fichier
+ <code>.htaccess</code> est chargé en mémoire chaque fois qu'un
+ document fait l'objet d'une requête.</p>
+
+ <p>Notez aussi que httpd doit rechercher les fichiers
+ <code>.htaccess</code> dans tous les répertoires de niveau
+ supérieur, afin de rassembler toutes les directives qui s'appliquent
+ au répertoire courant (Voir la section <a href="#how">comment sont
+ appliquées les directives</a>). Ainsi, si un fichier fait l'objet
+ d'une requête à partir d'un répertoire
+ <code>/www/htdocs/exemple</code>, httpd doit rechercher les
+ fichiers suivants :</p>
+
+ <div class="example"><p><code>
+ /.htaccess<br />
+ /www/.htaccess<br />
+ /www/htdocs/.htaccess<br />
+ /www/htdocs/exemple/.htaccess
+ </code></p></div>
+
+ <p>En conséquence, chaque accès à un fichier de ce répertoire
+ nécessite 4 accès au système de fichiers supplémentaires pour
+ rechercher des fichiers <code>.htaccess</code>, même si
+ aucun de ces fichiers n'est présent. Notez que cet exemple ne peut
+ se produire que si les fichiers <code>.htaccess</code> ont été
+ autorisés pour le répertoire <code>/</code>, ce qui est rarement le
+ cas.</p>
+
+ <p>La seconde raison d'éviter l'utilisation des fichiers
+ <code>.htaccess</code> est liée à la sécurité. Si vous permettez aux
+ utilisateurs de modifier la configuration du serveur, il peut en
+ résulter des conséquences sur lesquelles vous n'aurez aucun
+ contrôle. Réfléchissez bien avant de donner ce privilège à vos
+ utilisateurs. Notez aussi que ne pas donner aux utilisateurs les
+ privilèges dont ils ont besoin va entraîner une augmentation des
+ demandes de support technique. Assurez-vous d'avoir informé
+ clairement vos utilisateurs du niveau de privilèges que vous leur
+ avez attribué. Indiquer exactement comment vous avez défini la
+ directive <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> et
+ diriger les utilisateurs vers la documentation correspondante vous
+ évitera bien des confusions ultérieures.</p>
+
+ <p>Notez que mettre un fichier <code>.htaccess</code> contenant une
+ directive dans un répertoire <code>/www/htdocs/exemple</code>
+ revient exactement au même que mettre la même directive dans une
+ section Directory <code>&lt;Directory "/www/htdocs/exemple"&gt;</code>
+ du fichier de configuration de votre serveur principal :</p>
+
+ <p>Fichier <code>.htaccess</code> dans
+ <code>/www/htdocs/exemple</code> :</p>
+
+ <div class="example"><h3>Contenu du fichier .htaccess dans
+ <code>/www/htdocs/exemple</code></h3><pre class="prettyprint lang-config">AddType text/example ".exm"</pre>
+</div>
+
+ <div class="example"><h3>Section de votre fichier
+ <code>httpd.conf</code></h3><pre class="prettyprint lang-config">&lt;Directory "/www/htdocs/example"&gt;
+ AddType text/example .exm
+&lt;/Directory&gt;</pre>
+</div>
+
+ <p>Cependant, la perte de performances sera moindre si vous
+ définissez cette directive dans la configuration de
+ votre serveur principal, car cette dernière ne sera chargée qu'une
+ seule fois au moment du démarrage du serveur, alors qu'elle le sera
+ à chaque accès dans le cas d'un fichier <code>.htaccess</code>.</p>
+
+ <p>L'utilisation des fichiers <code>.htaccess</code> peut être
+ entièrement désactivée en définissant la directive <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> à <code>none</code> :</p>
+
+ <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">Comment sont appliquées les directives ?</a></h2>
+
+ <p>Les directives de configuration situées dans un fichier
+ <code>.htaccess</code> s'appliquent au répertoire dans lequel ce
+ fichier <code>.htaccess</code> se trouve, ainsi qu'à tous ses
+ sous-répertoires. Cependant, il est important de garder à l'esprit
+ qu'il peut y avoir des fichiers <code>.htaccess</code> dans les
+ répertoires de niveau supérieur. Les directives sont appliquées
+ selon l'ordre dans lequel elles sont rencontrées. Ainsi, les
+ directives d'un fichier <code>.htaccess</code> situé dans un
+ répertoire particulier peuvent écraser les directives se trouvant
+ dans des fichiers <code>.htaccess</code> situés à un niveau
+ supérieur dans l'arborescence des répertoires. Et ces dernières
+ peuvent elles-mêmes avoir écrasé des directives d'un fichier
+ <code>.htaccess</code> situé à un niveau encore plus haut, ou dans
+ le fichier de configuration du serveur principal.</p>
+
+ <p>Exemple :</p>
+
+ <p>Dans le répertoire <code>/www/htdocs/exemple1</code> se trouve un
+ fichier <code>.htaccess</code> contenant ce qui suit :</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI</pre>
+
+
+ <p>Note : "<code>AllowOverride Options</code>" doit être présent
+ pour permettre l'utilisation de la directive "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" dans les fichiers
+ <code>.htaccess</code>.</p>
+
+ <p>Dans le répertoire <code>/www/htdocs/exemple1/exemple2</code> se
+ trouve un fichier <code>.htaccess</code> contenant ce qui suit
+ :</p>
+
+ <pre class="prettyprint lang-config">Options Includes</pre>
+
+
+ <p>Ainsi, à cause de ce second fichier <code>.htaccess</code> du
+ répertoire <code>/www/htdocs/exemple1/exemple2</code>, l'exécution
+ des CGI est interdite, car la dernière définition d'options
+ <code>Options Includes</code> écrase toute autre définition
+ d'options d'un fichier <code>.htaccess</code> situé dans un
+ répertoire de niveau supérieur.</p>
+
+ <h3><a name="merge" id="merge">Interactions entre les fichiers .htaccess
+ et les fichiers de configuration du serveur principal</a></h3>
+
+ <p>Comme indiqué dans la documentation sur les <a href="../sections.html">Sections de configuration</a>, les fichiers
+ <code>.htaccess</code> peuvent écraser les directives des sections
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> pour
+ le répertoire correspondant, mais peuvent eux-mêmes être écrasés
+ par d'autres types de sections des fichiers de la
+ configuration principale. Cette possibilité peut s'avérer utile pour
+ forcer certaines configurations, même en cas de présence de l'option
+ libérale <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>. Par
+ exemple, pour interdire l'exécution de scripts en autorisant la
+ définition de toute autre option dans les fichiers
+ <code>.htaccess</code>, vous pouvez utiliser :</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/htdocs"&gt;
+ AllowOverride All
+&lt;/Directory&gt;
+
+&lt;Location "/"&gt;
+ Options +IncludesNoExec -ExecCGI
+&lt;/Location&gt;</pre>
+
+
+ <div class="note">Dans cet exemple, on considère que le chemin défini par la
+ directive <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> est
+ <code>/www/htdocs</code>.</div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="auth" id="auth">Exemple d'authentification</a></h2>
+
+ <p>Si vous accédez directement à ce point du document pour apprendre
+ à effectuer une authentification, il est important de noter ceci. Il
+ existe une fausse idée selon laquelle il serait nécessaire
+ d'utiliser les fichiers <code>.htaccess</code> pour implémenter
+ l'authentification par mot de passe. Ceci est tout simplement faux.
+ Pour y parvenir, il est préférable de mettre les directives
+ d'authentification dans une section <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> du fichier de configuration de
+ votre serveur principal, et les fichiers <code>.htaccess</code> ne
+ devraient être utilisés que dans le cas où vous n'avez pas accès au
+ fichier de configuration du serveur principal. Voir <a href="#when">ci-dessus</a> pour savoir dans quels cas vous devez ou
+ ne devez pas utiliser les fichiers <code>.htaccess</code>.</p>
+
+ <p>Ceci étant dit, si vous pensez que vous devez quand-même utiliser
+ un fichier <code>.htaccess</code>, vous pouvez utiliser la
+ configuration suivante :</p>
+
+ <p>Contenu du fichier <code>.htaccess</code> :</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "Password Required"
+AuthUserFile "/www/passwords/password.file"
+AuthGroupFile "/www/passwords/group.file"
+Require group admins</pre>
+
+
+ <p>Notez que <code>AllowOverride AuthConfig</code> doit être présent
+ pour que ces directives produisent leur effet.</p>
+
+ <p>Vous pouvez vous référer au <a href="auth.html">tutoriel sur
+ l'authentification</a> pour une description plus détaillée de
+ l'authentification et de l'autorisation.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ssi" id="ssi">Exemple d'Inclusion Côté Serveur (Server Side
+Includes - SSI)</a></h2>
+
+ <p>Les fichiers <code>.htaccess</code> sont aussi couramment
+ utilisés pour activer les SSI pour un répertoire particulier. Pour y
+ parvenir, on utilise les directives de configuration suivantes,
+ placées dans un fichier <code>.htaccess</code> enregistré dans le
+ répertoire considéré :</p>
+
+ <pre class="prettyprint lang-config">Options +Includes
+AddType text/html shtml
+AddHandler server-parsed shtml</pre>
+
+
+ <p>Notez que <code>AllowOverride Options</code> et <code>AllowOverride
+ FileInfo</code> doivent être tous les deux présents pour que ces
+ directives puissent produire leur effet.</p>
+
+ <p>Vous pouvez vous référer au <a href="ssi.html">tutoriel SSI</a>
+ pour une description plus détaillée des SSI.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="rewrite" id="rewrite">Les règles de réécriture dans les fichiers .htaccess</a></h2>
+<p>Sivous utilisez des directives <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> dans un fichier
+<code>.htaccess</code>, gardez à l'esprit que les choses sont légèrement
+différentes dans un contexte de répertoire. En particulier, les règles
+sont relatives au répertoire courant, et non à l'URI original. Considérez
+les exemples suivants :</p>
+
+<pre class="prettyprint lang-config"># Dans httpd.conf
+RewriteRule "^/images/(.+)\.jpg" "/images/$1.png"
+
+# Dans un fichier .htaccess situé dans le répertoire racine de vos
+# documents
+RewriteRule "^images/(.+)\.jpg" "images/$1.png"
+
+# Dans un fichier .htaccess situé dans le répertoire images/
+RewriteRule "^(.+)\.jpg" "$1.png"</pre>
+
+
+<p>On voit que si le fichier <code>.htaccess</code> se situe à la racine
+de vos documents, le slash de tête est supprimé de la valeur de
+remplacement spécifiée pour la règle <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, et que si le fichier
+<code>.htaccess</code> se situe dans le répertoire <code>images</code>,
+la chaîne <code>/images/</code> disparaît de cette même valeur de
+remplacement. Il doit donc en être de même dans votre expression
+rationnelle.</p>
+
+<p>Veuillez vous référer à cette <a href="../rewrite/">documentation</a>
+pour une étude détaillée de l'utilisation du module
+<code>mod_rewrite</code>.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="cgi" id="cgi">Exemple de CGI</a></h2>
+
+ <p>En fin de compte, vous avez décidé d'utiliser un fichier
+ <code>.htaccess</code> pour permettre l'exécution des programmes CGI
+ dans un répertoire particulier. Pour y parvenir, vous pouvez
+ utiliser la configuration suivante :</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI
+AddHandler cgi-script cgi pl</pre>
+
+
+ <p>Alternativement, si vous souhaitez que tous les fichiers d'un
+ répertoire donné soient considérés comme des programmes CGI, vous
+ pouvez utiliser la configuration suivante :</p>
+
+ <pre class="prettyprint lang-config">Options +ExecCGI
+SetHandler cgi-script</pre>
+
+
+ <p>Notez que <code>AllowOverride Options</code> et <code>AllowOverride
+ FileInfo</code> doivent être tous les deux présents pour que ces
+ directives puissent produire leur effet.</p>
+
+ <p>Vous pouvez vous référer au <a href="cgi.html">tutoriel CGI</a>
+ pour une description plus détaillée de la configuration et de la
+ proprammation CGI.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="troubleshoot" id="troubleshoot">Résolution des problèmes</a></h2>
+
+ <p>De nombreuses raisons peuvent être à l'origine du fait que
+ les directives que vous avez mises dans un fichier
+ <code>.htaccess</code> ne produisent pas l'effet désiré.</p>
+
+ <p>Le plus souvent, le problème vient du fait que la définition de
+ la directive <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ ne permet pas l'activation des directives de votre fichier
+ <code>.htaccess</code>. Vérifiez si une directive
+ <code>AllowOverride None</code> n'affecte pas le répertoire où se
+ trouve votre fichier. Un bon test consiste à mettre des directives
+ dont la syntaxe est erronée dans votre ficher <code>.htaccess</code>
+ et de recharger la page. Si aucune erreur n'est générée par le
+ serveur, il est pratiquement certain qu'une directive
+ <code>AllowOverride None</code> affecte votre répertoire.</p>
+
+ <p>Par contre, si vous obtenez des erreurs de serveur lorsque vous
+ tentez d'accéder à des documents, consultez votre journal des
+ erreurs de httpd. Il vous indiquera probablement que la directive
+ utilisée dans votre fichier <code>.htaccess</code> n'est pas
+ permise.</p>
+
+<div class="example"><p><code>
+ [Fri Sep 17 18:43:16 2010] [alert] [client 192.168.200.51] /var/www/html/.htaccess: DirectoryIndex not allowed here
+</code></p></div>
+ <p>Cela signifie soit que vous utilisez une directive qui n'est
+ jamais permise dans les fichiers <code>.htaccess</code>, soit
+ que vous n'avez tout simplement pas défini la directive
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> à un niveau
+ suffisant pour la directive que vous utilisez. Consultez la
+ documentation de cette directive pour déterminer quel cas
+ s'applique.</p>
+
+ <p>Le journal des erreurs peut aussi vous signaler une erreur de
+ syntaxe dans l'usage de la directive elle-même.</p>
+
+ <div class="example"><p><code>
+ [Sat Aug 09 16:22:34 2008] [alert] [client 192.168.200.51] /var/www/html/.htaccess: RewriteCond: bad flag delimiters
+ </code></p></div>
+
+ <p>Dans ce cas, le message d'erreur sera spécifique à l'erreur
+ de syntaxe que vous avez commise.</p>
+</div></div>
+<div class="bottomlang">
+<p><span>Langues Disponibles: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" title="Français">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Commentaires</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/htaccess.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Autorisé sous <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/htaccess.html.ja.utf8 b/docs/manual/howto/htaccess.html.ja.utf8
new file mode 100644
index 0000000..6d42801
--- /dev/null
+++ b/docs/manual/howto/htaccess.html.ja.utf8
@@ -0,0 +1,417 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="ja" xml:lang="ja"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Apache チュートリアル: .htaccess ファイル - Apache HTTP サーバ バージョン 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">モジュール</a> | <a href="../mod/directives.html">ディレクティブ</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">用語</a> | <a href="../sitemap.html">サイトマップ</a></p>
+<p class="apache">Apache HTTP サーバ バージョン 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP サーバ</a> &gt; <a href="http://httpd.apache.org/docs/">ドキュメンテーション</a> &gt; <a href="../">バージョン 2.4</a> &gt; <a href="./">How-To / チュートリアル</a></div><div id="page-content"><div id="preamble"><h1>Apache チュートリアル: .htaccess ファイル</h1>
+<div class="toplang">
+<p><span>翻訳済み言語: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div>
+<div class="outofdate">この日本語訳はすでに古くなっている
+ 可能性があります。
+ 最近更新された内容を見るには英語版をご覧下さい。
+ </div>
+
+<p><code>.htaccess</code> ファイルはディレクトリ毎に設定を変更する方法を
+提供します。</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">.htaccess ファイル</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#what">.htaccess ファイルとは何か/その使い方</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#when">いつ .htaccess ファイルを使う(使わない)か。</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#how">ディレクティブの適用のされ方</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#auth">認証の例</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#ssi">SSI の例</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI の例</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">問題解決</a></li>
+</ul><h3>参照</h3><ul class="seealso"><li><a href="#comments_section">コメント</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">.htaccess ファイル</a></h2>
+ <table class="related"><tr><th>関連モジュール</th><th>関連ディレクティブ</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_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li></ul></td></tr></table>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="what" id="what">.htaccess ファイルとは何か/その使い方</a></h2>
+
+
+ <p><code>.htaccess</code> ファイル (「分散設定ファイル」) は
+ ディレクトリ毎に設定を変更する方法を提供します。ディレクティブの
+ 書かれたファイルをディレクトリに置くことで、そのディレクトリとその
+ サブディレクトリすべてにディレクティブを適用させることができます。</p>
+
+ <div class="note"><h3>注:</h3>
+ <p><code>.htaccess</code> ファイルを別の名前にしたい場合は、
+ <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code> ディレクティブを
+ 使って変更することができます。例えば、そのファイルを <code>.config</code>
+ という名前にしたい場合は、以下の設定をサーバ設定ファイルに入れることが
+ できます:</p>
+
+ <div class="example"><p><code>
+ AccessFileName .config
+ </code></p></div>
+ </div>
+
+ <p>一般に、<code>.htaccess</code> ファイルの構文は
+ <a href="../configuring.html#syntax">主設定ファイル</a>
+ と同じです。これらのファイルに書くことのできるディレクティブは <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> ディレクティブにより決まります。
+ このディレクティブは、<code>.htaccess</code> ファイルに
+ 書かれたディレクティブの中で、、
+ どのディレクティブが適用されるかをカテゴリー単位で指定します。
+ <code>.htaccess</code> に書くことのできるディレクティブであれば、
+ 説明文書には「上書き」という項目があり、.htaccess に書くことができるように
+ なるための <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> の値が指定されています。</p>
+
+ <p>例えば、<code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code> ディレクティブの説明を
+ 見ると、<code>.htaccess</code> ファイルでの使用が許可されていることが
+ わかります。 (ディレクティブの概要の所にある「コンテキスト」と書かれている
+ 行を見てください。) <a href="../mod/directive-dict.html#Context">上書き</a>と書かれている行には
+ <code>FileInfo</code> とあります。ですから、<code>.htaccess</code> 中の
+ このディレクティブが有効になるためには、少なくとも
+ <code>AllowOverride FileInfo</code> が設定されている必要があります。</p>
+
+ <div class="example"><h3>例:</h3><table>
+ <tr>
+ <td><a href="../mod/directive-dict.html#Context">コンテキスト:</a></td>
+ <td>サーバ設定ファイル,バーチャルホスト,ディレクトリ,.htaccess</td>
+ </tr>
+
+ <tr>
+ <td><a href="../mod/directive-dict.html#Override">上書き:</a></td>
+ <td>FileInfo</td>
+ </tr>
+ </table></div>
+
+ <p>あるディレクティブを <code>.htaccess</code> ファイルに書くことができるか
+ どうかわからないときは、そのディレクティブの説明を探して、".htaccess"
+ のための「コンテキスト」の行を調べてください。</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="when" id="when">いつ .htaccess ファイルを使う(使わない)か。</a></h2>
+
+ <p>一般的に、サーバの主設定ファイルにアクセスできない場合を除いて、
+ <code>.htaccess</code> ファイルの使用は極力避けてください。
+ 世の中には、例えば、ユーザ認証は常に <code>.htaccess</code> ファイルで
+ 行なわなければならない、という誤解が広まっていますが、まったくそんなことは
+ ありません。ユーザ認証の設定はサーバ主設定ファイルに書くことができ、
+ 実際、その方がより良い設定方法です。</p>
+
+ <p><code>.htaccess</code> ファイルはコンテンツ提供者がディレクトリ毎の
+ 設定を行ないたいけれど、サーバシステムの root アクセス権限を持っていない
+ という場合にのみ使うべきものです。サーバ管理者が頻繁に設定変更を行ないたくは
+ ない、というときには個々のユーザが <code>.htaccess</code> ファイルを使って
+ 自分で設定の変更を行なうことを許可した方が良いときもあるでしょう。
+ これは特に、ISP が複数のユーザのサイトを一つのマシンでホストしていて、
+ 各ユーザが設定の変更をできるようにしたいようなときにあてはまります。</p>
+
+ <p>しかし、普通は可能であれば <code>.htaccess</code> ファイルの使用は
+ 避けてください。<code>.htaccess</code> ファイルに書こうと考えるような
+ すべての設定は、サーバの主設定ファイルの <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> セクションで同じように行なうことが
+ できます。</p>
+
+ <p><code>.htaccess</code> ファイルの使用を避ける理由は主に二つあります。</p>
+
+ <p>一つ目はサーバの性能の問題です。<code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> ディレクティブが
+ <code>.htaccess</code> ファイルの設定を許可している場合は、Apache は
+ 各ディレクトリで <code>.htaccess</code> ファイルを探します。
+ ですから、<code>.htaccess</code> ファイルを許可すると、実際に使用しているか
+ どうかに関わらず、性能の低下を招くことになります! また、<code>.htaccess</code>
+ ファイルは文書がリクエストされる度に読み込まれます。</p>
+
+ <p>さらに、Apache は適用すべきディレクティブを集めるために、すべての
+ 上位のディレクトリの <code>.htaccess</code> ファイルを探す必要があることにも
+ 注意してください。(<a href="#how">ディレクティブが適用される方法</a>を
+ 参照してください。)ですから、<code>/www/htdocs/example</code> にある
+ ファイルがリクエストされたときは、Apache は以下のファイルを調べます。</p>
+
+ <div class="example"><p><code>
+ /.htaccess<br />
+ /www/.htaccess<br />
+ /www/htdocs/.htaccess<br />
+ /www/htdocs/example/.htaccess
+ </code></p></div>
+
+ <p>ですから、そのディレクトリのそれぞれのファイルへのアクセスに対して、
+ 上の例のファイルがまったく存在しないときでも、追加のファイルシステムの
+ アクセスが行なわれることになります。(これは、<code>.htaccess</code> が
+ <code>/</code> に対して有効になっているときの場合で、普通はそうなって
+ いないことに注意してください。)</p>
+
+ <p>二つ目はセキュリティです。ユーザにサーバの設定を変更することを
+ 許可することになりますので、あなた自身が管理できない変更をされる
+ 恐れがあります。ユーザにこの特権を与えるのが良いのかどうか、十分
+ 検討してください。また、ユーザに与える権限が必要なものよりも少なすぎると、
+ 余分な技術サポート報告を受け取るようになる可能性が高いことにも
+ 注意してください。確実に、ユーザにどの程度の権限を与えたか明確に告げるように
+ してください。<code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> に
+ 何を設定したかということと、関連する文書を示すことで、
+ 後々の混乱をぐっと減らすことが
+ できます。</p>
+
+ <p>ところで、ディレクティブの書かれた <code>.htaccess</code> を
+ <code>/www/htdocs/example</code> に置くことと、同じディレクティブを
+ 主サーバ設定の Directory セクション
+ <code>&lt;Directory /www/htdocs/example&gt;</code> に書くことは
+ 完全に等価です:</p>
+
+ <p><code>/www/htdocs/example</code> の <code>.htaccess</code> ファイル:</p>
+
+ <div class="example"><h3><code>/www/htdocs/example</code> の .htaccess ファイルの
+ 内容</h3><p><code>
+ AddType text/example .exm
+ </code></p></div>
+
+ <div class="example"><h3><code>httpd.conf のセクション</code>
+ file</h3><p><code>
+ &lt;Directory /www/htdocs/example&gt;<br />
+ <span class="indent">
+ AddType text/example .exm<br />
+ </span>
+ &lt;/Directory&gt;
+ </code></p></div>
+
+ <p>しかし、この設定はサーバ設定ファイルに書いた方がパフォーマンスの
+ 低下が少なくなります。ファイルがリクエストされる度に
+ 読み込まれる代わりに、Apache の起動時に 1 回だけ読み込めば
+ よくなるからです。</p>
+
+ <p><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> ディレクティブの
+ 値を <code>none</code> に設定することで <code>.htaccess</code> ファイル
+ の使用を完全に無効にすることができます。</p>
+
+ <div class="example"><p><code>
+ AllowOverride None
+ </code></p></div>
+</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">ディレクティブの適用のされ方</a></h2>
+
+ <p><code>.htaccess</code> ファイルの設定ディレクティブは <code>.htaccess</code>
+ ファイルの存在するディレクトリと、そのサブディレクトリすべてに適用されます。
+ しかし、上の階層のディレクトリにも <code>.htaccess</code> ファイルが
+ 存在するかもしれないことを覚えておくことは大切です。ディレクティブは現れる
+ 順番に適用されます。ですから、あるディレクトリの <code>.htaccess</code> は
+ ディレクトリツリーのより上の階層の <code>.htaccess</code> ファイルの
+ 設定を上書きするかもしれません。そして、その <code>.htaccess</code> も
+ より上の階層で書かれたディレクティブを上書きしたり、主サーバ設定ファイル
+ そのものの設定を上書きしたりしているかもしれません。</p>
+
+ <p>例:</p>
+
+ <p>ディレクトリ <code>/www/htdocs/example1</code> に以下の内容の
+ <code>.htaccess</code> ファイルがあります:</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI
+ </code></p></div>
+
+ <p>(注: <code>.htaccess</code>
+ ファイルで "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" ディレクティブが有効になるためには、
+ "<code>AllowOverride Options</code>" を有効にする必要があります。)</p>
+
+ <p>ディレクトリ <code>/www/htdocs/example1/example2</code> には
+ 以下のような <code>.htaccess</code> ファイルがあります:</p>
+
+ <div class="example"><p><code>
+ Options Includes
+ </code></p></div>
+
+ <p>二つめの <code>.htaccess</code> により、ディレクトリ
+ <code>/www/htdocs/example1/example2</code> では CGI の実行は
+ 許可されません。これは、<code>Options Includes</code> のみが
+ 効力を持ち、それがすべての以前の設定を上書きするからです。</p>
+
+ <h3><a name="merge" id="merge">メイン設定ファイルに対する
+ .htaccess のマージ</a></h3>
+
+ <p>As discussed in the documentation on <a href="../sections.html">Configuration Sections</a>,
+ <code>.htaccess</code> files can override the <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> sections for
+ the corresponding directory, but will be overriden by other types
+ of configuration sections from the main configuration files. This
+ fact can be used to enforce certain configurations, even in the
+ presence of a liberal <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> setting. For example, to
+ prevent script execution while allowing anything else to be set in
+ <code>.htaccess</code> you can use:</p>
+ <p><a href="../sections.html">セクションの設定</a>
+ に記載されているように、<code>.htaccess</code> ファイルを使って
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>
+ セクションの設定をディレクトリ毎に上書きできますが、
+ メイン設定ファイル中にある、他の種類の設定セクションによって
+ さらに上書きされることもあります。
+ この特徴を使って、
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ で自由度の高い設定があったとしても、ある特定の設定が確実に
+ 反映されるようにできます。例えば、CGI スクリプトの実行は
+ 不許可に、かつ、<code>.htaccess</code> でその他の項目は
+ 設定できるように、という場合は次のようにできます :</p>
+
+ <div class="example"><p><code>
+&lt;Directory /&gt;<br />
+<span class="indent">
+Allowoverride All<br />
+</span>
+&lt;/Directory&gt;<br />
+<br />
+&lt;Location /&gt;<br />
+<span class="indent">
+Options +IncludesNoExec -ExecCGI<br />
+</span>
+&lt;/Location&gt;
+ </code></p></div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="auth" id="auth">認証の例</a></h2>
+
+ <p>もし認証の方法を知るためにこの部分に直接来たのであれば、次のことを
+ 知っておくことが重要です。よくある誤解に、パスワード認証を行なうためには
+ <code>.htaccess</code> ファイルを使う必要がある、というものがあります。
+ これは正しくありません。主サーバ設定ファイルの <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> セクションに
+ 認証用のディレクティブを書く方が推奨される方法で、<code>.htaccess</code>
+ ファイルは主サーバ設定ファイルを変更できないときにのみ使用すべきです。
+ いつ <code>.htaccess</code> ファイルを使うべきで、いつ使うべきではないかに
+ ついては <a href="#when">上</a>を参照してください。</p>
+
+ <p>以上のことをふまえた上で、もし <code>.htaccess</code> の使用が
+ まだ必要だと思う場合は、次のようなものが望みのことをしてくれるかも
+ しれません。</p>
+
+ <p><code>.htaccess</code> ファイルの内容:</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "Password Required"<br />
+ AuthUserFile /www/passwords/password.file<br />
+ AuthGroupFile /www/passwords/group.file<br />
+ Require Group admins
+ </code></p></div>
+
+ <p>これらのディレクティブが有効になるためには、
+ <code>AllowOverride AuthConfig</code> が有効でなくてはならないことに
+ 注意してください。</p>
+
+ <p>認証と承認については <a href="auth.html">認証チュートリアル</a>を
+ 参照してください。</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ssi" id="ssi">SSI の例</a></h2>
+
+ <p>もう一つの <code>.htaccess</code> ファイルのよくある利用法は
+ 特定のディレクトリで SSI を有効にすることです。これは、望みのディレクトリの
+ <code>.htaccess</code> ファイルに以下の設定ディレクティブを書くことで
+ 達成できます:</p>
+
+ <div class="example"><p><code>
+ Options +Includes<br />
+ AddType text/html shtml<br />
+ AddHandler server-parsed shtml
+ </code></p></div>
+
+ <p>これらのディレクティブが有効になるためには、
+ <code>AllowOverride Options</code> と <code>AllowOverride
+ FileInfo</code> が有効になっている必要があることに注意してください。</p>
+
+ <p>よりまとまった SSI の説明は <a href="ssi.html">SSI チュートリアル</a>を
+ 参照してください。</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="cgi" id="cgi">CGI の例</a></h2>
+
+ <p>最後に、特定のディレクトリで CGI プログラムの実行を許可したいことが
+ あるでしょう。これは以下の設定で行なうことができます:</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI<br />
+ AddHandler cgi-script cgi pl
+ </code></p></div>
+
+ <p>もしくは、あるディレクトリのすべてのファイルが CGI プログラムと
+ みなされるようにしたいなら、以下の設定で実現することができます:</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI<br />
+ SetHandler cgi-script
+ </code></p></div>
+
+ <p>これらのディレクティブが有効になるためには、
+ <code>AllowOverride Options</code> と <code>AllowOverride
+ FileInfo</code> が有効である必要があることに注意してください。</p>
+
+ <p>CGI プログラムと設定のよりまとまった説明は <a href="cgi.html">CGI チュートリアル</a>を参照してください。</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="troubleshoot" id="troubleshoot">問題解決</a></h2>
+
+ <p>設定ディレクティブを <code>.htaccess</code> ファイルに書いたけれども、
+ 期待した効果が得られないときには、いくつかの原因が考えられます。</p>
+
+ <p>一番よくあることは、設定ディレクティブが考慮されるようには
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> が設定されていない
+ というものです。該当のファイルのスコープに <code>AllowOverride None</code>
+ が設定されていないことを確認してください。これを調べるための良い方法は、
+ <code>.htaccess</code> ファイルにごみを書いて、リロードすることです。
+ サーバのエラーが生成されないときは、ほぼ確実に <code>AllowOverride
+ None</code> が設定されている状態になっています。</p>
+
+ <p>そうではなく、文書をアクセスしようとしたときにエラーが発生している
+ ときは、Apache のエラーログを調べてください。<code>.htaccess</code> ファイルで
+ 使用されたディレクティブが許可されていない、ということを知らせている
+ 可能性が高いです。または、構文の間違いがあることを述べているかもしれません。
+ その場合にはまずそれを修正する必要があります。</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>翻訳済み言語: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">コメント</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/htaccess.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />この文書は <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> のライセンスで提供されています。.</p>
+<p class="menu"><a href="../mod/">モジュール</a> | <a href="../mod/directives.html">ディレクティブ</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">用語</a> | <a href="../sitemap.html">サイトマップ</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/htaccess.html.ko.euc-kr b/docs/manual/howto/htaccess.html.ko.euc-kr
new file mode 100644
index 0000000..69d856f
--- /dev/null
+++ b/docs/manual/howto/htaccess.html.ko.euc-kr
@@ -0,0 +1,363 @@
+<?xml version="1.0" encoding="EUC-KR"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head>
+<meta content="text/html; charset=EUC-KR" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>ġ 丮: .htaccess - Apache HTTP Server Version 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/"></a> | <a href="../mod/directives.html">þ</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html"></a> | <a href="../sitemap.html">Ʈ</a></p>
+<p class="apache">Apache HTTP Server Version 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.4</a> &gt; <a href="./">How-To / Tutorials</a></div><div id="page-content"><div id="preamble"><h1>ġ 丮: .htaccess </h1>
+<div class="toplang">
+<p><span> : </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Portugu&#234;s (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div>
+<div class="outofdate"> ֽ ƴմϴ.
+ ֱٿ ϼ.</div>
+
+<p><code>.htaccess</code> Ͽ 丮
+ ִ.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">.htaccess </a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#what"≯/ ϴ°</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#when"> .htaccess ϳ
+ (Ȥ ʳ)</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#how"> þ ϳ</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#auth"> </a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Server Side Includes </a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI </a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">ذ</a></li>
+</ul><h3></h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">.htaccess </a></h2>
+ <table class="related"><tr><th>õ </th><th>õ þ</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_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/core.html#require">Require</a></code></li></ul></td></tr></table>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="what" id="what"≯/ ϴ°</a></h2>
+
+
+ <p><code>.htaccess</code> (Ȥ "л ")
+ ϸ 丮 ִ. þ
+ ִ Ư 丮 θ, 丮
+ 丮 þ Ѵ.</p>
+
+ <div class="note"><h3>:</h3>
+ <p><code>.htaccess</code> ϸ ٸ ϰ ʹٸ,
+ <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code> þ
+ Ͽ ִ. , <code>.config</code>
+ ϸ Ϸ Ͽ ߰Ѵ.</p>
+
+ <div class="example"><p><code>
+ AccessFileName .config
+ </code></p></div>
+ </div>
+
+ <p>Ϲ <code>.htaccess</code> <a href="../configuring.html#syntax">ּ</a>
+ . <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ þ Ͽ ִ Ѵ. þ
+ <code>.htaccess</code> Ͽ ϴ þ з Ѵ.
+ þ <code>.htaccess</code> Ͽ ִٸ,
+ ش þ Override ׸ þ ϱ
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ ˷ش.</p>
+
+ <p> , <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>
+ þ þ <code>.htaccess</code> Ͽ
+ ִ. (þ ࿡ ׸ .)
+ <a href="../mod/directive-dict.html#Context">Override</a>
+ ٿ <code>FileInfo</code> ִ. ׷ þ
+ <code>.htaccess</code> Ͽ ϱؼ ּ
+ <code>AllowOverride FileInfo</code> ʿϴ.</p>
+
+ <div class="example"><h3>:</h3><table>
+ <tr>
+ <td><a href="../mod/directive-dict.html#Context">:</a></td>
+ <td>ּ, ȣƮ, directory, .htaccess</td>
+ </tr>
+
+ <tr>
+ <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
+ <td>FileInfo</td>
+ </tr>
+ </table></div>
+
+ <p>Ư þ <code>.htaccess</code> Ͽ
+ ִ ñϸ þ ׸ ".htaccess"
+ ִ ȮѴ.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="when" id="when"> .htaccess ϳ
+ (Ȥ ʳ)</a></h2>
+
+ <p>Ϲ ּϿ 찡 ƴ϶
+ <code>.htaccess</code> ϸ ȵȴ. ,
+ ׻ <code>.htaccess</code> Ͽ ־
+ Ѵٴ ߸ ˷ ش. ̴ ƴϴ. ּ
+ ְ, ̷ Ѵ.</p>
+
+ <p><code>.htaccess</code> ڰ 丮
+ ٸϰ ýۿ root
+ 쿡 Ѵ. ڰ ϰ
+ Ϲ ڰ <code>.htaccess</code>
+ ϵ ϴ ٶϴ. ,
+ ǻͿ Ʈ ϴ ISP ڰ
+ ڽ ϰ 찡 ׷ϴ.</p>
+
+ <p>׷ Ϲ <code>.htaccess</code>
+ ؾ Ѵ. <code>.htaccess</code> Ͽ ϴ þ
+ ּ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> ǰ ȿ
+ ִ.</p>
+
+ <p> ΰ ū <code>.htaccess</code>
+ ؾ Ѵ.</p>
+
+ <p>ù° ̴. <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> <code>.htaccess</code>
+ ϵ ϸ, ġ 丮
+ <code>.htaccess</code> ã´. ׷
+ <code>.htaccess</code> ϸ
+ ʴ 쿡 ! , <code>.htaccess</code>
+ ûҶ оδ.</p>
+
+ <p>Դٰ ؾ ϴ ü þ ġ
+ 丮 <code>.htaccess</code> ã´.
+ (<a href="#how"> þ ϳ</a> .)
+ ׷ <code>/www/htdocs/example</code> 丮 ִ
+ ûϸ, ġ ϵ ãƾ Ѵ.</p>
+
+ <div class="example"><p><code>
+ /.htaccess<br />
+ /www/.htaccess<br />
+ /www/htdocs/.htaccess<br />
+ /www/htdocs/example/.htaccess
+ </code></p></div>
+
+ <p>׷ 丮 ִ
+  Ͻý 4 ؾ Ѵ.
+ (<code>/</code> <code>.htaccess</code>
+ 츦 Ѵ. ʴ´.)</p>
+
+ <p>ι° ̴. ڿ
+ ָ ȭ Ͼ ִ. ڿ
+ ̷ ϶. , ڰ ϴ ͺ
+ ָ û ´. ڿ
+ Ȯ ˷. ڿ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>  Ͽ
+ Ȯ ˸ ϸ ȥ
+ ִ.</p>
+
+ <p>þ <code>/www/htdocs/example</code> 丮
+ <code>.htaccess</code> δ Ͱ ּ
+ <code>&lt;Directory /www/htdocs/example&gt;</code> Directory
+ δ .</p>
+
+ <p><code>/www/htdocs/example</code> ִ
+ <code>.htaccess</code> :</p>
+
+ <div class="example"><h3><code>/www/htdocs/example</code> ִ
+ .htaccess </h3><p><code>
+ AddType text/example .exm
+ </code></p></div>
+
+ <div class="example"><h3><code>httpd.conf</code> Ͽ ִ </h3><p><code>
+ &lt;Directory /www/htdocs/example&gt;<br />
+ <span class="indent">
+ AddType text/example .exm<br />
+ </span>
+ &lt;/Directory&gt;
+ </code></p></div>
+
+ <p>׷ û ʰ ġ
+ Ҷ ѹ б⶧ Ͽ
+ ϸ .</p>
+
+ <p><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> þ
+ <code>none</code> ϸ <code>.htaccess</code>
+ .</p>
+
+ <div class="example"><p><code>
+ AllowOverride None
+ </code></p></div>
+</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"> þ ϳ</a></h2>
+
+ <p><code>.htaccess</code> ߰ 丮 丮
+ 丮 <code>.htaccess</code> Ͽ ִ
+ þ Ѵ. ׷ 丮 <code>.htaccess</code>
+ ؾ Ѵ. ߰ þ Ѵ. Ư
+ 丮 ִ <code>.htaccess</code> 丮
+ ִ <code>.htaccess</code> þ ȿ
+ ְ, 丮 ִ þ 丮 Ȥ
+ ּϿ ִ þ ȿ ִ.</p>
+
+ <p>:</p>
+
+ <p><code>/www/htdocs/example1</code> 丮
+ <code>.htaccess</code> ִ.</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI
+ </code></p></div>
+
+ <p>(: <code>.htaccess</code> Ͽ "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" þ Ϸ
+ "<code>AllowOverride Options</code>" ʿϴ.)</p>
+
+ <p><code>/www/htdocs/example1/example2</code> 丮
+ <code>.htaccess</code> ִ.</p>
+
+ <div class="example"><p><code>
+ Options Includes
+ </code></p></div>
+
+ <p> ι° <code>.htaccess</code>
+ <code>Options Includes</code> ȿ
+ ⶧ <code>/www/htdocs/example1/example2</code>
+ 丮 CGI ʴ´.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="auth" id="auth"> </a></h2>
+
+ <p> ˱ ٷ ̰ д´ٸ
+ ִ. ȣ Ϸ <code>.htaccess</code>
+ ʿϴٴ ذ θ ִ. ̴ ƴϴ.
+ ּ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> ǿ þ
+ δ ϴ ̰, ּ
+ 쿡 <code>.htaccess</code> ؾ
+ Ѵ. <code>.htaccess</code> ؾ ϴ
+ ƾ ϴ <a href="#when"></a>
+ Ͽ.</p>
+
+ <p>տ <code>.htaccess</code>
+ ʿϴٰ Ǹ Ʒ ̴.</p>
+
+ <p><code>.htaccess</code> .</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "Password Required"<br />
+ AuthUserFile /www/passwords/password.file<br />
+ AuthGroupFile /www/passwords/group.file<br />
+ Require Group admins
+ </code></p></div>
+
+ <p> þ ϱؼ
+ <code>AllowOverride AuthConfig</code> þ ʿ
+ ϶.</p>
+
+ <p> Ѻο ڼ <a href="auth.html">
+ 丮</a> ٶ.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ssi" id="ssi">Server Side Includes </a></h2>
+
+ <p>Ǵٸ Ϲ <code>.htaccess</code> 뵵
+ Ư 丮 Server Side Includes ϰ
+ ̴. ϴ 丮 <code>.htaccess</code> Ͽ
+ þ ϸ ȴ.</p>
+
+ <div class="example"><p><code>
+ Options +Includes<br />
+ AddType text/html shtml<br />
+ AddHandler server-parsed shtml
+ </code></p></div>
+
+ <p> þ Ϸ <code>AllowOverride Options</code>
+ <code>AllowOverride FileInfo</code> ʿ ϶.</p>
+
+ <p>server-side includes ڼ <a href="ssi.html">SSI 丮</a> ٶ.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="cgi" id="cgi">CGI </a></h2>
+
+ <p> <code>.htaccess</code> Ͽ Ư
+ 丮 CGI α׷ ϰ ʹٸ,
+ Ѵ.</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI<br />
+ AddHandler cgi-script cgi pl
+ </code></p></div>
+
+ <p>Ȥ 丮 ִ CGI α׷
+ óϰ ʹٸ ϴ.</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI<br />
+ SetHandler cgi-script
+ </code></p></div>
+
+ <p> þ Ϸ <code>AllowOverride Options</code>
+ <code>AllowOverride FileInfo</code> ʿ ϶.</p>
+
+ <p>CGI α׷ְ ڼ <a href="cgi.html">CGI 丮</a> ٶ.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="troubleshoot" id="troubleshoot">ذ</a></h2>
+
+ <p><code>.htaccess</code> Ͽ þ ϴ
+ ʴ ִ.</p>
+
+ <p> Ϲ þ ϰ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ . Ǵ <code>AllowOverride None</code>
+ ȮѴ. <code>.htaccess</code> ƹԳ
+ ٽ Ͽ ˻غ ִ.
+ Ȯ
+ <code>AllowOverride None</code> .</p>
+
+ <p>ݴ Ҷ ߻ϸ ġ α׸
+ . Ƹ <code>.htaccess</code> Ͽ ִ þ
+ ʴ´ٰ ̴. ƴϰ ִٸ
+ ģ.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span> : </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Portugu&#234;s (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/htaccess.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 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>
+<p class="menu"><a href="../mod/"></a> | <a href="../mod/directives.html">þ</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html"></a> | <a href="../sitemap.html">Ʈ</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/htaccess.html.pt-br b/docs/manual/howto/htaccess.html.pt-br
new file mode 100644
index 0000000..1468957
--- /dev/null
+++ b/docs/manual/howto/htaccess.html.pt-br
@@ -0,0 +1,407 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="pt-br" xml:lang="pt-br"><head>
+<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Tutorial do Apache: arquivos .htaccess - Servidor HTTP Apache Vers&#227;o 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">M&#243;dulos</a> | <a href="../mod/directives.html">Diretrizes</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Gloss&#225;rio</a> | <a href="../sitemap.html">Mapa do site</a></p>
+<p class="apache">Servidor HTTP Apache Vers&#227;o 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">Servidor HTTP</a> &gt; <a href="http://httpd.apache.org/docs/">Documenta&#231;&#227;o</a> &gt; <a href="../">Vers&#227;o 2.4</a> &gt; <a href="./">How-To / Tutoriais</a></div><div id="page-content"><div id="preamble"><h1>Tutorial do Apache: arquivos .htaccess</h1>
+<div class="toplang">
+<p><span>L&#237;nguas Dispon&#237;veis: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" title="Portugu&#234;s (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div>
+<div class="outofdate">Esta tradu&#231;&#227;o pode estar desatualizada.
+ Confira a vers&#227;o em Ingl&#234;s para mudan&#231;as recentes.</div>
+
+<p>Arquivos <code>.htaccess</code> oferecem um meio de fazer mudan&#231;as
+ nas configura&#231;&#245;es por-diret&#243;rio.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">Arquivos .htaccess </a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#what">O que eles s&#227;o/Como us&#225;-los</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#when">Quando (n&#227;o) usar arquivos .htaccess</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#how">Como as diretrizes s&#227;o aplicadas</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#auth">Exemplo de Autentica&#231;&#227;o</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Exemplo de Server Side Includes</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#cgi">Exemplo de CGI</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">Resolvendo Problemas</a></li>
+</ul><h3>Veja tamb&#233;m</h3><ul class="seealso"><li><a href="#comments_section">Coment&#225;rios</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">Arquivos .htaccess </a></h2>
+ <table class="related"><tr><th>M&#243;dulos Relacionados</th><th>Diretrizes Relacionadas</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_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li></ul></td></tr></table>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="what" id="what">O que eles s&#227;o/Como us&#225;-los</a></h2>
+
+
+ <p>Os arquivos <code>.htaccess</code> (ou "arquivos de
+ configura&#231;&#227;o distribu&#237;da") oferecem um meio de fazer mudan&#231;as nas
+ configura&#231;&#245;es por-diret&#243;rio. Um arquivo, contendo uma ou mais
+ diretrizes de configura&#231;&#245;es, &#233; colocado em um diret&#243;rio
+ em particular, e as diretrizes se aplicam para aquele diret&#243;rio e todos
+ os seu subdiret&#243;rios subseq&#252;entes.</p>
+
+ <div class="note"><h3>Nota:</h3>
+ <p>Se voc&#234; quiser renomear o seu arquivo <code>.htaccess</code>
+ para outro nome, voc&#234; deve usar a diretriz <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code>. Por exemplo, se voc&#234;
+ prefere que o arquivo se chame <code>.config</code>, ent&#227;o voc&#234;
+ pode adicionar a seguinte linha ao seu arquivo de configura&#231;&#227;o
+ do servidor:</p>
+
+ <div class="example"><p><code>
+ AccessFileName .config
+ </code></p></div>
+ </div>
+
+ <p>No geral, arquivos <code>.htaccess</code> usam a mesma sintaxe
+ que os <a href="../configuring.html#syntax">arquivos de
+ configura&#231;&#227;o principal</a>. O que voc&#234; pode colocar nesses
+ arquivos &#233; determinado pele diretriz <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>. Essa diretriz especifica,
+ em categorias, quais diretrizes ser&#227;o aceitas caso sejam
+ encontradas em um arquivo <code>.htaccess</code>. Se uma diretriz
+ for permitida em um arquivo <code>.htaccess</code>, a documenta&#231;&#227;o
+ para essa diretriz ir&#225; conter uma se&#231;&#227;o <em>Override</em>,
+ especificando que valor precisa estar em <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> para que esta diretriz
+ seja permitida.</p>
+
+ <p>Por exemplo, se voc&#234; procurar na documenta&#231;&#227;o pela diretriz
+ <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>, voc&#234;
+ achar&#225; que ela &#233; permitida nos arquivos <code>.htaccess</code>.
+ (Veja a linha Contexto no sum&#225;rio das diretivas.) A
+ linha <a href="../mod/directive-dict.html#Context">Override</a> l&#234;
+ <code>FileInfo</code>. Ent&#227;o, voc&#234; deve ao menos ter
+ <code>AllowOverride FileInfo</code> para que essa diretriz seja
+ aceita nos arquivos <code>.htaccess</code>.</p>
+
+ <div class="example"><h3>Exemplo:</h3><table>
+ <tr>
+ <td><a href="../mod/directive-dict.html#Context">Contexto:</a></td>
+ <td>configura&#231;&#227;o do servidor, hospedeiros virtuais, diret&#243;rio, .htaccess</td>
+ </tr>
+
+ <tr>
+ <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
+ <td>FileInfo</td>
+ </tr>
+ </table></div>
+
+ <p>Se voc&#234; estiver incerto se uma diretriz em particular &#233;
+ aceita em um arquivo <code>.htaccess</code>, procure na
+ documenta&#231;&#227;o por essa diretriz, e verifique a linha de
+ Contexto por ".htaccess".</p> </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="when" id="when">Quando (n&#227;o) usar arquivos .htaccess</a></h2>
+
+ <p>No geral, voc&#234; nunca deve usar arquivos <code>.htaccess</code>
+ a n&#227;o ser que voc&#234; n&#227;o tenha acesso ao arquivo de configura&#231;&#227;o
+ principal do servidor. Existe, por exemplo, um erro de concep&#231;&#227;o
+ que dita que a autentica&#231;&#227;o de usu&#225;rios sempre deve
+ ser feita usando os arquivos <code>.htaccess</code>. Esse
+ simplesmente n&#227;o &#233; o caso. Voc&#234; pode usar as configura&#231;&#245;es de
+ autentica&#231;&#227;o de usu&#225;rio no arquivo de configura&#231;&#227;o principal do
+ servidor, e isso &#233;, de fato, a maneira mais adequada de se fazer
+ as coisas.</p>
+
+ <p>Arquivos <code>.htaccess</code> devem ser usados em casos onde
+ os provedores de conte&#250;do do site precisem fazer mudan&#231;as na
+ configura&#231;&#227;o do servidor por-diret&#243;rio, mas n&#227;o tem
+ acesso <em>root</em> ao sistema do servidor. Caso o administrador do
+ servidor n&#227;o esteja disposto a fazer mudan&#231;as freq&#252;entes nas
+ configura&#231;&#245;es do servidor, &#233; desej&#225;vel permitir que os
+ usu&#225;rios possam fazer essas mudan&#231;as atrav&#233;s de arquivos
+ <code>.htaccess</code> eles mesmos. Isso &#233; particularmente
+ verdade, por exemplo, em casos onde provedores est&#227;o fornecendo
+ m&#250;ltiplos sites para usu&#225;rios em apenas uma m&#225;quina, e querem que
+ seus usu&#225;rios possam alterar suas configura&#231;&#245;es.</p>
+
+ <p>No entanto, de modo geral, o uso de arquivos <code>.htaccess</code>
+ deve ser evitado quando poss&#237;vel. Quaisquer configura&#231;&#245;es
+ que voc&#234; considerar acrescentar em um arquivo <code>.htaccess</code>, podem
+ ser efetivamente colocadas em uma se&#231;&#227;o <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> no arquivo principal de
+ configura&#231;&#227;o de seu servidor.</p>
+
+ <p>Existem duas raz&#245;es principais para evitar o uso de arquivos
+ <code>.htaccess</code>.</p>
+
+ <p>A primeira delas &#233; a performance. Quando <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> &#233; configurado para
+ permitir o uso de arquivos <code>.htaccess</code>, o Apache procura
+ em todos diret&#243;rios por arquivos <code>.htaccess</code>.
+ Logo, permitir arquivos <code>.htaccess</code> causa um impacto na
+ performance, mesmo sem voc&#234; us&#225;-los de fato! Al&#233;m disso,
+ o arquivo <code>.htaccess</code> &#233; carregado toda vez que um documento
+ &#233; requerido.</p>
+
+ <p>Al&#233;m disso, note que o Apache precisa procurar pelos arquivos
+ <code>.htaccess</code> em todos os diret&#243;rios superiores, para ter
+ o complemento total de todas as diretivas que devem ser
+ aplicadas. (Veja a se&#231;&#227;o <a href="#how">como as diretrizes s&#227;o
+ aplicadas</a>.) Ent&#227;o, se um arquivo de um diret&#243;rio
+ <code>/www/htdocs/example</code> &#233; requerido, o Apache precisa
+ procurar pelos seguintes arquivos:</p>
+
+ <div class="example"><p><code>
+ /.htaccess<br />
+ /www/.htaccess<br />
+ /www/htdocs/.htaccess<br />
+ /www/htdocs/example/.htaccess
+ </code></p></div>
+
+ <p>Assim, para cada acesso de arquivo fora desse diret&#243;rio,
+ existem 4 acessos ao sistema de arquivos adicionais, mesmo
+ que nenhum desses arquivos estejam presentes. (Note que esse
+ s&#243; ser&#225; o caso se os arquivos <code>.htaccess</code>
+ estiverem habilitados para <code>/</code>, o que
+ normalmente n&#227;o &#233; o verdade.)</p>
+
+ <p>A segunda considera&#231;&#227;o &#233; relativa &#224; seguran&#231;a.
+ Voc&#234; est&#225; permitindo que os usu&#225;rios modifiquem as
+ configura&#231;&#245;es do servidor, o que pode resultar em mudan&#231;as
+ que podem fugir ao seu controle. Considere com cuidado se voc&#234; quer
+ ou n&#227;o dar aos seus usu&#225;rios esses privil&#233;gios. Note tamb&#233;m
+ que dar aos usu&#225;rios menos privil&#233;gios que eles precisam, acarreta em
+ pedidos de suporte t&#233;cnico adicionais. Tenha certeza que voc&#234; comunicou
+ aos usu&#225;rios que n&#237;vel de privil&#233;gios voc&#234; os deu.
+ Especificar exatamente o que voc&#234; configurou na diretriz <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>, e direcion&#225;-los para a
+ documenta&#231;&#227;o relevante, ir&#225; poup&#225;-lo de muita confus&#227;o
+ depois.</p>
+
+ <p>Perceba que &#233; exatamente equivalente colocar o arquivo
+ <code>.htaccess</code> em um diret&#243;rio
+ <code>/www/htdocs/example</code> contendo uma diretriz, e
+ adicionar a mesma diretriz em uma se&#231;&#227;o <em>Directory</em>
+ <code>&lt;Directory /www/htdocs/example&gt;</code> na configura&#231;&#227;o
+ principal do seu servidor:</p>
+
+ <p>Arquivo <code>.htaccess</code> em <code>/www/htdocs/example</code>:</p>
+
+ <div class="example"><h3>Conte&#250;do de um arquivo .htaccess em
+ <code>/www/htdocs/example</code></h3><p><code>
+ AddType text/example .exm
+ </code></p></div>
+
+ <div class="example"><h3>Se&#231;&#227;o do seu arquivo <code>httpd.conf</code></h3><p><code>
+ &lt;Directory /www/htdocs/example&gt;<br />
+ <span class="indent">
+ AddType text/example .exm<br />
+ </span>
+ &lt;/Directory&gt;
+ </code></p></div>
+
+ <p>No entanto, adicionando isso ao seu arquivo de configura&#231;&#227;o do
+ servidor resultar&#225; em uma menor perda de performance, na medida que
+ a configura&#231;&#227;o &#233; carregada no momento da inicializa&#231;&#227;o do
+ servidor, ao inv&#233;s de toda que que um arquivo &#233; requerido.</p>
+
+ <p>O uso de arquivos <code>.htaccess</code> pode ser totalmente
+ desabilitado, ajustando a diretriz <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> para <code>none</code>:</p>
+
+ <div class="example"><p><code>
+ AllowOverride None
+ </code></p></div>
+</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">Como as diretrizes s&#227;o aplicadas</a></h2>
+
+ <p>As diretrizes de configura&#231;&#227;o que se encontram em um arquivo
+ <code>.htaccess</code> s&#227;o aplicadas para o diret&#243;rio no qual o
+ arquivo <code>.htaccess</code> se encontra, e para todos os
+ subdiret&#243;rios ali presentes. Mas, &#233; importante lembrar tamb&#233;m que
+ podem existir arquivos <code>.htaccess</code> no diret&#243;rios
+ superiores. As diretrizes s&#227;o aplicadas na ordem que s&#227;o
+ achadas. Logo, um arquivo <code>.htaccess</code> em um diret&#243;rio
+ em particular, pode sobrescrever as diretrizes encontradas em um
+ diret&#243;rio acima deste em sua respectiva &#225;rvore. Estes, por sua vez,
+ podem ter suas diretrizes sobrescritas por diretrizes ainda mais
+ acima, ou no pr&#243;prio arquivo de configura&#231;&#227;o principal do
+ servidor.</p>
+
+ <p>Exemplo:</p>
+
+ <p>No diret&#243;rio <code>/www/htdocs/example1</code> n&#243;s temos
+ um arquivo <code>.htaccess</code> contendo o seguinte:</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI
+ </code></p></div>
+
+ <p>(Nota: voc&#234; deve ter "<code>AllowOverride Options</code>" para
+ permitir o uso da diretriz "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" nos arquivos
+ <code>.htaccess</code> .)</p>
+
+ <p>No diret&#243;rio <code>/www/htdocs/example1/example2</code> n&#243;s temos
+ um arquivo <code>.htaccess</code> contendo:</p>
+
+ <div class="example"><p><code>
+ Options Includes
+ </code></p></div>
+
+ <p>Devido a esse segundo arquivo <code>.htaccess</code>, no
+ diret&#243;rio <code>/www/htdocs/example1/example2</code>, a execu&#231;&#227;o
+ de scripts CGI n&#227;o &#233; permitida, pois somente <code>Options
+ Includes</code> est&#225; em efeito, o que sobrescreve completamente
+ quaisquer outros ajustes previamente configurados.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="auth" id="auth">Exemplo de Autentica&#231;&#227;o</a></h2>
+
+ <p>Se voc&#234; veio diretamente &#224; esta parte do documento para
+ aprender como fazer autentica&#231;&#227;o, &#233; importante notar uma
+ coisa. Existe uma concep&#231;&#227;o errada, mas muito comum, de que &#233;
+ necess&#225;rio o uso de arquivos <code>.htaccess</code> para implementar
+ a autentica&#231;&#227;o por senha. Este n&#227;o &#233; o caso. Colocar
+ diretrizes de senha em uma se&#231;&#227;o <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>, no seu arquivo principal de
+ configura&#231;&#227;o do servidor, &#233; a melhor maneira de se implementar
+ isto, e os arquivos <code>.htaccess</code> devem ser usados apenas
+ se voc&#234; n&#227;o tem acesso ao arquivo principal de configura&#231;&#227;o do
+ servidor. Veja <a href="#when">acima</a> a discuss&#227;o sobre quando
+ voc&#234; deve e quando n&#227;o deve usar os arquivos
+ <code>.htaccess</code>.</p>
+
+ <p>Dito isso, se voc&#234; ainda acredita que precisa usar um arquivo
+ <code>.htaccess</code>, a configura&#231;&#227;o a seguir provavelmente
+ funcionar&#225; para voc&#234;.</p>
+
+ <p>Conte&#250;do de um arquivo <code>.htaccess</code>:</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "Password Required"<br />
+ AuthUserFile /www/passwords/password.file<br />
+ AuthGroupFile /www/passwords/group.file<br />
+ Require Group admins
+ </code></p></div>
+
+ <p>Note que <code>AllowOverride AuthConfig</code> precisa estar
+ habilitado para que estas diretrizes tenham efeito.</p>
+
+ <p>Por favor veja o <a href="auth.html">tutorial de
+ autentica&#231;&#227;o</a> para uma discuss&#227;o mais completa sobre
+ autentica&#231;&#227;o e autoriza&#231;&#227;o.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="ssi" id="ssi">Exemplo de Server Side Includes</a></h2>
+
+ <p>Outro uso comum de arquivos <code>.htaccess</code> &#233; ativar o
+ Server Side Includes para um diret&#243;rio em particular. Isto pode
+ ser feito com as seguintes diretrizes de configura&#231;&#227;o, colocadas em
+ um arquivo <code>.htaccess</code> no diret&#243;rio desejado:</p>
+
+ <div class="example"><p><code>
+ Options +Includes<br />
+ AddType text/html shtml<br />
+ AddHandler server-parsed shtml
+ </code></p></div>
+
+ <p>Note que ambos <code>AllowOverride Options</code> e
+ <code>AllowOverride FileInfo</code> precisam estar habilitados
+ para essas diretrizes terem efeito.</p>
+
+ <p>Por favor veja o <a href="ssi.html">tutorial de SSI</a> para
+ uma discuss&#227;o mais completa sobre server-side includes.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="cgi" id="cgi">Exemplo de CGI</a></h2>
+
+ <p>Finalmente, voc&#234; pode querer que um arquivo
+ <code>.htaccess</code> permita a execu&#231;&#227;o de programas CGI em um
+ diret&#243;rio em particular. Isto pode ser implementado com as
+ seguintes configura&#231;&#245;es:</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI<br />
+ AddHandler cgi-script cgi pl
+ </code></p></div>
+
+ <p>Alternativamente, se voc&#234; desejar que todos os arquivos de um
+ dado diret&#243;rio, sejam considerados programas CGI, isso pode ser
+ feito com a seguinte configura&#231;&#227;o:</p>
+
+ <div class="example"><p><code>
+ Options +ExecCGI<br />
+ SetHandler cgi-script
+ </code></p></div>
+
+ <p>Note que ambos <code>AllowOverride Options</code> e
+ <code>AllowOverride FileInfo</code> precisam estar habilitados
+ para que essas diretrizes tenham quaisquer efeito.</p>
+
+ <p>Por favor veja o <a href="cgi.html">tutorial de CGI
+ tutorial</a> para uma discuss&#227;o mais completa sobre programa&#231;&#227;o
+ e configura&#231;&#227;o CGI.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="troubleshoot" id="troubleshoot">Resolvendo Problemas</a></h2>
+
+ <p>Quando voc&#234; adiciona diretrizes de configura&#231;&#227;o em um arquivo
+ <code>.htaccess</code>, e n&#227;o obt&#233;m o efeito desejado, existe uma
+ s&#233;rie de pontos que podem estar errados.</p>
+
+ <p>Mais comumente, o problema &#233; que a diretriz <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> n&#227;o est&#225; habilitada
+ corretamente para que as suas diretrizes de configura&#231;&#245;es sejam
+ honradas. Verifique se voc&#234; n&#227;o possui <code>AllowOverride
+ None</code> ajustado para o escopo do arquivo em quest&#227;o. Um bom
+ meio de testar isso &#233; colocar "lixo" em seu arquivo
+ <code>.htaccess</code> e recarreg&#225;-lo. Se n&#227;o for gerado nenhum
+ erro do servidor, certamente voc&#234; tem <code>AllowOverride
+ None</code> habilitado.</p>
+
+ <p>Se, por outro lado, voc&#234; est&#225; obtendo erros do servidor ao
+ tentar acessar documentos, verifique o registro de erros do
+ Apache. Ele provavelmente ir&#225; indicar que a diretriz usada em
+ seu arquivo <code>.htaccess</code> n&#227;o &#233; permitida.
+ Alternativamente, ele pode acusar erros de sintaxe que voc&#234; ter&#225;
+ que corrigir.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>L&#237;nguas Dispon&#237;veis: </span><a href="../en/howto/htaccess.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../pt-br/howto/htaccess.html" title="Portugu&#234;s (Brasil)">&nbsp;pt-br&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Coment&#225;rios</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/htaccess.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licenciado sob a <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">M&#243;dulos</a> | <a href="../mod/directives.html">Diretrizes</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Gloss&#225;rio</a> | <a href="../sitemap.html">Mapa do site</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file