<h2><a name="ipv6" id="ipv6">Betrachtung von IPv6-Besonderheiten</a></h2>
- <p>Eine wachsende Anzahl von Plattformen implementiert IPv6. Die APR
+ <p>Eine wachsende Anzahl von Plattformen implementiert IPv6. Die
+ <a class="glossarylink" href="./glossary.html#apr" title="siehe Glossar">APR</a>
unterstützt IPv6 auf den meisten dieser Plattformen und
ermöglicht dem Apache, IPv6-Sockets zu verwenden und Anfragen zu
behandeln, die über IPv6 gesendet wurden.</p>
<h2><a name="ipv6" id="ipv6">Special IPv6 Considerations</a></h2>
- <p>A growing number of platforms implement IPv6, and APR supports
- IPv6 on most of these platforms, allowing Apache to allocate IPv6
- sockets and handle requests which were sent over IPv6.</p>
+ <p>A growing number of platforms implement IPv6, and
+ <a class="glossarylink" href="./glossary.html#apr" title="see glossary">APR</a> supports IPv6 on most of these platforms,
+ allowing Apache to allocate IPv6 sockets and handle requests which
+ were sent over IPv6.</p>
<p>One complicating factor for Apache administrators is whether or
not an IPv6 socket can handle both IPv4 connections and IPv6
<a href="./ja/bind.html" title="Japanese"> ja </a> |
<a href="./ko/bind.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<p>Apache ¤¬»ÈÍѤ¹¤ë¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÎÀßÄê¤ò¤·¤Þ¤¹¡£</p>
</div>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.fr.xsl"?>
-<!-- English Revision: 103425:151408 (outdated) -->
+<!-- English Revision: 103425:290801 (outdated) -->
<!--
Copyright 2004-2005 The Apache Software Foundation or its licensors,
<?xml version="1.0" encoding="iso-2022-jp" ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ja.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290801 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors,
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ko.xsl"?>
-<!-- English Revision: 105989:151408 (outdated) -->
+<!-- English Revision: 105989:290801 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
<variant>de</variant>
<variant>en</variant>
<variant outdated="yes">fr</variant>
- <variant>ja</variant>
+ <variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
</variants>
</metafile>
<h3><a name="type-map" id="type-map">Using a type-map file</a></h3>
- <p>A type map is a document which is associated with the
- handler named <code>type-map</code> (or, for
- backwards-compatibility with older Apache configurations, the
- MIME type <code>application/x-type-map</code>). Note that to
- use this feature, you must have a handler set in the
- configuration that defines a file suffix as
- <code>type-map</code>; this is best done with</p>
+ <p>A type map is a document which is associated with the handler
+ named <code>type-map</code> (or, for backwards-compatibility with
+ older Apache configurations, the <a class="glossarylink" href="./glossary.html#mime-type" title="see glossary">MIME-type</a>
+ <code>application/x-type-map</code>). Note that to use this
+ feature, you must have a handler set in the configuration that
+ defines a file suffix as <code>type-map</code>; this is best done
+ with</p>
<div class="example"><p><code>AddHandler type-map .var</code></p></div>
<a href="./ja/content-negotiation.html" title="Japanese"> ja </a> |
<a href="./ko/content-negotiation.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<p>Apache ¤Ï HTTP/1.1 ¤Îµ¬³Ê¤Ëµ½Ò¤µ¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò
<a href="./ja/content-negotiation.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="./ko/content-negotiation.html" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">ÀÌ ¹®¼´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù.
+ ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼¸¦ Âü°íÇϼ¼¿ä.</div>
<p>¾ÆÆÄÄ¡´Â HTTP/1.1 ±Ô¾à¿¡ ±â¼úµÈ ³»¿ëÇù»ó(content
<?xml version='1.0' encoding='iso-2022-jp' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ja.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors,
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ko.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
<variants>
<variant>en</variant>
- <variant>ja</variant>
- <variant>ko</variant>
+ <variant outdated="yes">ja</variant>
+ <variant outdated="yes">ko</variant>
</variants>
</metafile>
Siehe: <code class="program"><a href="./programs/apxs.html">apxs</a></code>-Dokumentation
</dd>
+ <dt><a name="apacheportableruntime" id="apacheportableruntime">Apache Portable Runtime</a> <a name="apr" id="apr">(APR)</a></dt>
+ <dd>Eine Menge von Bibliotheken, die viele grundlegende Schnittstellen
+ zwischen dem Server und dem Betriebssystem anbietet. Die APR
+ wird parallel zum Apache HTTP Server in einem eigenständigen Projekt
+ entwickelt.<br />
+ Siehe auch: <a href="http://apr.apache.org/">Apache Portable Runtime
+ Project</a>
+ </dd>
+
<dt><a name="authentication" id="authentication">Authentifizierung</a></dt>
<dd>Die positive Identifizierung einer Netzwerkeinheit, wie z.B.
eines Servers, eines Clients oder eines Benutzers.<br />
See: Manual Page: <code class="program"><a href="./programs/apxs.html">apxs</a></code>
</dd>
+ <dt><a name="apacheportableruntime" id="apacheportableruntime">Apache Portable Runtime</a> <a name="apr" id="apr">(APR)</a></dt>
+ <dd>A set of libraries providing many of the basic interfaces
+ between the server and the operating system. APR is developed
+ parallel to the Apache HTTP Server as an independent project.<br />
+ See: <a href="http://apr.apache.org/">Apache Portable Runtime
+ Project</a>
+ </dd>
+
<dt><a name="authentication" id="authentication">Authentication</a></dt>
<dd>The positive identification of a network entity such as a server, a
client, or a user.<br />
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.es.xsl"?>
-<!-- English Revision: 105174:151408 (outdated) -->
+<!-- English Revision: 105174:290803 (outdated) -->
<!--
Copyright 2004-2005 The Apache Software Foundation or its licensors,
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ko.xsl"?>
-<!-- English Revision: 105989:151408 (outdated) -->
+<!-- English Revision: 105989:290803 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
programming, and CGI programming.</p>
<p>First, all output from your CGI program must be preceded by
- a MIME-type header. This is HTTP header that tells the client
+ a <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> header. This is HTTP header that tells the client
what sort of content it is receiving. Most of the time, this
will look like:</p>
<a href="../ja/howto/cgi.html" title="Japanese"> ja </a> |
<a href="../ko/howto/cgi.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#intro">¤Ï¤¸¤á¤Ë</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#configuring">CGI ¤òµö²Ä¤¹¤ë¤è¤¦¤Ë Apache ¤òÀßÄꤹ¤ë</a></li>
<?xml version='1.0' encoding='iso-2022-jp' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors,
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 105989:151408 (outdated) -->
+<!-- English Revision: 105989:290816 (outdated) -->
<!--
Copyright 2004-2005 The Apache Software Foundation or its licensors,
<variants>
<variant>en</variant>
- <variant>ja</variant>
+ <variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
</variants>
</metafile>
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.0.33 and later</td></tr>
</table>
<p>This directive activates a particular output <a href="../filter.html">filter</a> for a request depending on the
- response MIME-type.</p>
+ response <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a>.</p>
<p>The following example uses the <code>DEFLATE</code> filter, which
is provided by <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>. It will compress all
<div class="warning"><h3>Note</h3>
<p>Enabling filters with <code class="directive">AddOutputFilterByType</code>
may fail partially or completely in some cases. For example, no
- filters are applied if the MIME-type could not be determined and falls
+ filters are applied if the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> could not be determined and falls
back to the <code class="directive"><a href="#defaulttype">DefaultType</a></code> setting,
even if the <code class="directive"><a href="#defaulttype">DefaultType</a></code> is the
same.</p>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
</table>
<p>There will be times when the server is asked to provide a
- document whose type cannot be determined by its MIME types
- mappings.</p>
+ document whose type cannot be determined by its <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME types</a> mappings.</p>
<p>The server must inform the client of the content-type of the
document, so in the event of an unknown type it uses the
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.de.xsl"?>
-<!-- English Revision: 167959:290729 (outdated) -->
+<!-- English Revision: 167959:290816 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 190982:290729 (outdated) -->
+<!-- English Revision: 190982:290816 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
<code>--with-mpm=event</code> to the <code class="program"><a href="../programs/configure.html">configure</a></code>
script's arguments when building the <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
- <p>This MPM depends on APR's atomic compare-and-swap operations for
- thread synchronization. If you are compiling for an x86 target
- and you don't need to support 386s, or you are compiling for a
- SPARC and you don't need to run on pre-UltraSPARC chips, add
+ <p>This MPM depends on <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a>'s atomic
+ compare-and-swap operations for thread synchronization. If you are
+ compiling for an x86 target and you don't need to support 386s, or
+ you are compiling for a SPARC and you don't need to run on
+ pre-UltraSPARC chips, add
<code>--enable-nonportable-atomics=yes</code> to the
<code class="program"><a href="../programs/configure.html">configure</a></code> script's arguments. This will cause
- APR to implement atomic operations
- using efficient opcodes not available in older CPUs.</p>
+ APR to implement atomic operations using efficient opcodes not
+ available in older CPUs.</p>
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
<h3>Zusammenfassung</h3>
<p>Das Modul besitzt zwei Direktiven. Die Direktive <code class="directive"><a href="#action">Action</a></code> erlaubt die Ausführung von
- CGI-Skripten immer dann, wenn eine Anfrage zu einem bestimmten MIME-Type
- erfolgt. Die Direktive <code class="directive"><a href="#script">Script</a></code>
- erlaubt die Ausführung von CGI-Skripten abhängig von einer
- bestimmten Methode, die in der Anfrage verwendet wird. Dies macht es
- deutlich einfacher, Skripte auszuführen, die Dateien
- verarbeiten.</p>
+ CGI-Skripten immer dann, wenn eine Anfrage zu einem bestimmten <a class="glossarylink" href="../glossary.html#mime-type" title="siehe Glossar">MIME-Type</a> erfolgt. Die Direktive <code class="directive"><a href="#script">Script</a></code> erlaubt die Ausführung von
+ CGI-Skripten abhängig von einer bestimmten Methode, die in der
+ Anfrage verwendet wird. Dies macht es deutlich einfacher, Skripte
+ auszuführen, die Dateien verarbeiten.</p>
</div>
<div id="quickview"><h3 class="directives">Direktiven</h3>
<ul id="toc">
<var>CGI-Skript</var> aktiviert, sobald die <var>Aktionsart</var> durch
eine Anfrage ausgelöst wird. <var>CGI-Skript</var> ist der URL-Pfad
zu einer Ressource, die unter Verwendung von <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> oder <code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code> als CGI-Skript gekennzeichnet
- wurde. Die <var>Aktionsart</var> kann entweder ein <a href="../handler.html">Handler</a> oder ein MIME-Type sein. Die URL und
+ wurde. Die <var>Aktionsart</var> kann entweder ein <a href="../handler.html">Handler</a> oder ein <a class="glossarylink" href="../glossary.html#mime-type" title="siehe Glossar">MIME-Type</a> sein. Die URL und
den Dateipfad des angeforderten Dokuments in den
Standard-CGI-Umgebungsvariablen <code>PATH_INFO</code> und
<code>PATH_TRANSLATED</code> übergeben. Der für die jeweilige
<h3>Summary</h3>
<p>This module has two directives. The <code class="directive"><a href="#action">Action</a></code> directive lets you run CGI
- scripts whenever a file of a certain MIME content type is requested. The
+ scripts whenever a file of a certain <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME content type</a> is requested. The
<code class="directive"><a href="#script">Script</a></code> directive lets
you run CGI scripts whenever a particular method is used in a
request. This makes it much easier to execute scripts that process
- files.</p>
-</div>
+ files.</p> </div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
<li><img alt="" src="../images/down.gif" /> <a href="#action">Action</a></li>
introduced in Apache 2.1</td></tr>
</table>
<p>This directive adds an action, which will activate
- <var>cgi-script</var> when <var>action-type</var> is triggered by the
- request. The <var>cgi-script</var> is the URL-path to a resource
- that has been designated as a CGI script using <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> or <code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code>. The
- <var>action-type</var> can be either a <a href="../handler.html">handler</a> or a MIME content type. It
- sends the URL and file path of the requested document using the
- standard CGI <code>PATH_INFO</code> and <code>PATH_TRANSLATED</code>
- environment variables. The handler used for the particular request is
- passed using the <code>REDIRECT_HANDLER</code> variable.</p>
+ <var>cgi-script</var> when <var>action-type</var> is triggered by
+ the request. The <var>cgi-script</var> is the URL-path to a
+
resource that has been designated as a CGI script using <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> or <code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code>. The
+ <var>action-type</var> can be either a <a href="../handler.html">handler</a> or a <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME content type</a>. It sends the URL and
+ file path of the requested document using the standard CGI
+ <code>PATH_INFO</code> and <code>PATH_TRANSLATED</code>
+ environment variables. The handler used for the particular request
+ is passed using the <code>REDIRECT_HANDLER</code> variable.</p>
<div class="example"><h3>Examples</h3><p><code>
# Requests for files of a particular MIME content type:<br />
<a href="../ja/mod/mod_actions.html" title="Japanese"> ja </a> |
<a href="../ko/mod/mod_actions.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">ÀâÌÀ:</a></th><td>¥á¥Ç¥£¥¢¥¿¥¤¥×¤ä¥ê¥¯¥¨¥¹¥È¥á¥½¥Ã¥É¤Ë±þ¤¸¤Æ
CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ëµ¡Ç½¤òÄó¶¡</td></tr>
<tr><th><a href="module-dict.html#Status">¥¹¥Æ¡¼¥¿¥¹:</a></th><td>Base</td></tr>
<a href="../ja/mod/mod_actions.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="../ko/mod/mod_actions.html" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">ÀÌ ¹®¼´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù.
+ ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼¸¦ Âü°íÇϼ¼¿ä.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">¼³¸í:</a></th><td>ÀÌ ¸ðµâÀº ¹Ìµð¾îÁ¾·ù³ª ¿äû¸Þ¼µå¿¡ µû¶ó CGI
½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÑ´Ù.</td></tr>
<tr><th><a href="module-dict.html#Status">»óÅÂ:</a></th><td>Base</td></tr>
<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors,
<?xml version="1.0" encoding='EUC-KR' ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
<variants>
<variant>de</variant>
<variant>en</variant>
- <variant>ja</variant>
- <variant>ko</variant>
+ <variant outdated="yes">ja</variant>
+ <variant outdated="yes">ko</variant>
</variants>
</metafile>
<p>The character set name parameters of <code class="directive"><a href="#charsetsourceenc">CharsetSourceEnc</a></code> and
<code class="directive"><a href="#charsetdefault">CharsetDefault</a></code>
- must be acceptable to the translation mechanism used by APR on the
- system where <code class="module"><a href="../mod/mod_charset_lite.html">mod_charset_lite</a></code> is deployed. These
- character set names are not standardized and are usually not the
- same as the corresponding values used in http headers. Currently,
- APR can only use iconv(3), so you can easily test your character
- set names using the iconv(1) program, as follows:</p>
+ must be acceptable to the translation mechanism used by
+ <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> on the system where
+ <code class="module"><a href="../mod/mod_charset_lite.html">mod_charset_lite</a></code> is deployed. These character
+ set names are not standardized and are usually not the same as
+ the corresponding values used in http headers. Currently, APR
+ can only use iconv(3), so you can easily test your character set
+ names using the iconv(1) program, as follows:</p>
<div class="example"><p><code>
iconv -f charsetsourceenc-value -t charsetdefault-value
<p>The value of the <var>charset</var> argument must be accepted
as a valid character set name by the character set support in
- APR. Generally, this means that it must be supported by
- iconv.</p>
+ <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a>. Generally, this means that it must be
+ supported by iconv.</p>
<div class="example"><h3>Example</h3><p><code>
<Directory /export/home/trawick/apacheinst/htdocs/convert><br />
<p>The value of the <var>charset</var> argument must be accepted
as a valid character set name by the character set support in
- APR. Generally, this means that it must be supported by
- iconv.</p>
+ <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a>. Generally, this means that it must be
+ supported by iconv.</p>
<div class="example"><h3>Example</h3><p><code>
<Directory /export/home/trawick/apacheinst/htdocs/convert><br />
<p><span>°¡´ÉÇÑ ¾ð¾î: </span><a href="../en/mod/mod_charset_lite.html" hreflang="en" rel="alternate" title="English"> en </a> |
<a href="../ko/mod/mod_charset_lite.html" title="Korean"> ko </a></p>
</div>
+<div class="outofdate">ÀÌ ¹®¼´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù.
+ ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼¸¦ Âü°íÇϼ¼¿ä.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">¼³¸í:</a></th><td>¹®ÀÚÁýÇÕ º¯È¯À» ÁöÁ¤</td></tr>
<tr><th><a href="module-dict.html#Status">»óÅÂ:</a></th><td>Experimental</td></tr>
<tr><th><a href="module-dict.html#ModuleIdentifier">¸ðµâ¸í:</a></th><td>charset_lite_module</td></tr>
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290801 (outdated) -->
<!--
Copyright 2003-2005 The Apache Software Foundation or its licensors,
<variants>
<variant>en</variant>
- <variant>ko</variant>
+ <variant outdated="yes">ko</variant>
</variants>
</metafile>
<h3><a name="element.include" id="element.include">The include Element</a></h3>
<p>This command inserts the text of another document or file
- into the parsed file. Any included file is subject to the
- usual access control. If the directory containing the
-
parsed file has <a href="core.html#options">Options</a>
- <code>IncludesNOEXEC</code> set, then only documents with
- a text MIME type (<code>text/plain</code>, <code>text/html</code>
- etc.) will be included. Otherwise CGI scripts are invoked as normal
- using the complete URL given in the command, including any query
- string.</p>
+ into the parsed file. Any included file is subject to the usual
+ access control. If the directory containing the parsed file has
+ <a href="core.html#options">Options</a>
+ <code>IncludesNOEXEC</code> set, then only documents with a text
+ <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> (<code>text/plain</code>,
+ <code>text/html</code> etc.) will be included. Otherwise CGI
+ scripts are invoked as normal using the complete URL given in
+ the command, including any query string.</p>
<p>An attribute defines the location of the document; the
inclusion is done for each attribute given to the include
</table>
<p>The <code class="directive">XBitHack</code> directive controls the parsing
of ordinary html documents. This directive only affects files associated
- with the MIME type <code>text/html</code>. <code class="directive">XBitHack</code> can take on the following values:</p>
+ with the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> <code>text/html</code>. <code class="directive">XBitHack</code> can take on the following values:</p>
<dl>
<dt><code>off</code></dt>
<p><span>Available Languages: </span><a href="../en/mod/mod_include.html" hreflang="en" rel="alternate" title="English"> en </a> |
<a href="../ja/mod/mod_include.html" title="Japanese"> ja </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">ÀâÌÀ:</a></th><td>¥µ¡¼¥Ð¤¬¥Ñ¡¼¥¹¤¹¤ë html ¥É¥¥å¥á¥ó¥È (Server Side Includes)</td></tr>
<tr><th><a href="module-dict.html#Status">¥¹¥Æ¡¼¥¿¥¹:</a></th><td>Base</td></tr>
<tr><th><a href="module-dict.html#ModuleIdentifier">¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:</a></th><td>include_module</td></tr>
<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors,
<variants>
<variant>en</variant>
- <variant>ja</variant>
+ <variant outdated="yes">ja</variant>
</variants>
</metafile>
Apache.</p>
<p>SSL/TLS support is dependant on which LDAP toolkit has been
- linked to APR. As of this writing, APR-util supports:
+ linked to <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a>. As of this writing, APR-util supports:
<a href="http://www.openldap.org/">OpenLDAP SDK</a> (2.x or later),
<a href="http://developer.novell.com/ndk/cldap.htm">Novell LDAP
SDK</a>, <a href="http://www.mozilla.org/directory/csdk.html">
<p>The directives <code class="directive"><a href="#addcharset">AddCharset</a></code>, <code class="directive"><a href="#addencoding">AddEncoding</a></code>, <code class="directive"><a href="#addlanguage">AddLanguage</a></code> and <code class="directive"><a href="#addtype">AddType</a></code> are all used to map file
extensions onto the meta-information for that file. Respectively
they set the character set, content-encoding, content-language,
- and
MIME-type (content-type) of documents. The directive <code class="directive"><a href="#typesconfig">TypesConfig</a></code> is used to specify a
+ and
<a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> (content-type) of documents. The directive <code class="directive"><a href="#typesconfig">TypesConfig</a></code> is used to specify a
file which also maps extensions onto MIME types. </p>
<p>In addition, <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> may define the <a href="../handler.html">handler</a> and <a href="../filter.html">filters</a> that originate and process
extensions is <em>normally</em> irrelevant. For example, if the
file <code>welcome.html.fr</code> maps onto content type
<code>text/html</code> and language French then the file
- <code>welcome.fr.html</code> will map onto exactly the same information.
- If more than one extension is given which maps onto the same
- type of meta-information, then the one to the right will be
- used, except for languages and content encodings. For example, if
- <code>.gif</code> maps to the MIME-type <code>image/gif</code> and
- <code>.html</code> maps to the MIME-type <code>text/html</code>, then the
- file <code>welcome.gif.html</code> will be associated with the MIME-type
- <code>text/html</code>.</p>
+ <code>welcome.fr.html</code> will map onto exactly the same
+ information. If more than one extension is given which maps onto
+ the same type of meta-information, then the one to the right will
+ be used, except for languages and content encodings. For example,
+ if <code>.gif</code> maps to the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a>
+ <code>image/gif</code> and <code>.html</code> maps to the
+ MIME-type <code>text/html</code>, then the file
+ <code>welcome.gif.html</code> will be associated with the
+ MIME-type <code>text/html</code>.</p>
<p><a href="#charset-lang">Languages</a> and <a href="#contentencoding">content encodings</a> are treated accumulative, because one can assign
more than one language or encoding to a particular ressource. For example,
text/html</code>.</p>
<p>Care should be taken when a file with multiple extensions
- gets associated with both a MIME-type and a handler. This will
+ gets associated with both a <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> and a handler. This will
usually result in the request being by the module associated
with the handler. For example, if the <code>.imap</code>
extension is mapped to the handler <code>imap-file</code> (from
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="contentencoding" id="contentencoding">Content encoding</a></h2>
- <p>A file of a particular MIME type can additionally be encoded a
+ <p>A file of a particular <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> can additionally be encoded a
particular way to simplify transmission over the Internet.
While this usually will refer to compression, such as
<code>gzip</code>, it can also refer to encryption, such a
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
- <p>The <code class="directive">AddType</code> directive maps the given filename
- extensions onto the specified content type. <var>MIME-type</var> is the
- MIME type to use for filenames containing <var>extension</var>. This
- mapping is added to any already in force, overriding any mappings that
- already exist for the same <var>extension</var>. This directive can
- be used to add mappings not listed in the MIME types file (see the
- <code class="directive"><a href="#typesconfig">TypesConfig</a></code> directive).</p>
+ <p>The <code class="directive">AddType</code> directive maps the given
+ filename extensions onto the specified content
+ type. <var>MIME-type</var> is the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME
+ type</a> to use for filenames containing
+ <var>extension</var>. This mapping is added to any already in
+ force, overriding any mappings that already exist for the same
+ <var>extension</var>. This directive can be used to add mappings
+ not listed in the MIME types file (see the <code class="directive"><a href="#typesconfig">TypesConfig</a></code> directive).</p>
<div class="example"><h3>Example</h3><p><code>
AddType image/gif .gif
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
- <p>The <code class="directive">RemoveType</code> directive removes any MIME
- type associations for files with the given extensions. This allows
- <code>.htaccess</code> files in subdirectories to undo any
- associations inherited from parent directories or the server
- config files. An example of its use might be:</p>
+ <p>The <code class="directive">RemoveType</code> directive removes any
+ <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME type</a> associations for files with
+ the given extensions. This allows <code>.htaccess</code> files in
+ subdirectories to undo any associations inherited from parent
+ directories or the server config files. An example of its use
+ might be:</p>
<div class="example"><h3>/foo/.htaccess:</h3><p><code>
RemoveType .cgi
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
- <p>The <code class="directive">TypesConfig</code> directive sets the location
- of the MIME types configuration file. <var>File-path</var> is relative
- to the <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>. This file sets
+ <p>The <code class="directive">TypesConfig</code> directive sets the
+ location of the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME types</a>
+ configuration file. <var>File-path</var> is relative to the
+ <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>. This file sets
the default list of mappings from filename extensions to content
- types. Most administrators use the provided <code>mime.types</code>
- file, which associates common filename extensions with IANA registered
- content types. The current list is maintained at <a href="http://www.iana.org/assignments/media-types/index.html">http://www.iana.org/assignments/media-types/index.html</a>.
- This simplifies the <code>httpd.conf</code> file by providing the
+ types. Most administrators use the provided
+ <code>mime.types</code> file, which associates common filename
+ extensions with IANA registered content types. The current list is
+ maintained at <a href="http://www.iana.org/assignments/media-types/index.html">http://www.iana.org/assignments/media-types/index.html</a>. This
+ simplifies the <code>httpd.conf</code> file by providing the
majority of media-type definitions, and may be overridden by
<code class="directive"><a href="#addtype">AddType</a></code> directives as
- needed. You should not edit the <code>mime.types</code> file, because
- it may be replaced when you upgrade your server.</p>
+ needed. You should not edit the <code>mime.types</code> file,
+ because it may be replaced when you upgrade your server.</p>
<p>The file contains lines in the format of the arguments to
an <code class="directive"><a href="#addtype">AddType</a></code> directive:</p>
<p><span>Available Languages: </span><a href="../en/mod/mod_mime.html" hreflang="en" rel="alternate" title="English"> en </a> |
<a href="../ja/mod/mod_mime.html" title="Japanese"> ja </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">ÀâÌÀ:</a></th><td>¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤È¥Õ¥¡¥¤¥ë¤Î¿¶¤ëÉñ¤¤
(¥Ï¥ó¥É¥é¤È¥Õ¥£¥ë¥¿)¡¢ÆâÍÆ (MIME ¥¿¥¤¥×¡¢¸À¸ì¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°)
¤È¤ò´ØÏ¢ÉÕ¤±¤ë</td></tr>
<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 193037 -->
+<!-- English Revision: 193037:290816 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors, as
<variants>
<variant>en</variant>
- <variant>ja</variant>
+ <variant outdated="yes">ja</variant>
</variants>
</metafile>
<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_mime_magic.c</td></tr></table>
<h3>Summary</h3>
- <p>This module determines the MIME type of files in the same
- way the Unix <code>file(1)</code> command works: it looks at the first
- few bytes of the file. It is intended as a "second line of defense"
+ <p>This module determines the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME
+ type</a> of files in the same way the Unix
+ <code>file(1)</code> command works: it looks at the first few
+ bytes of the file. It is intended as a "second line of defense"
for cases that <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> can't resolve.</p>
<p>This module is derived from a free version of the
<dt><code>Content-Type:</code></dt>
<dd>
- The MIME media type of the document, with optional
- parameters. Parameters are separated from the media type
- and from one another by a semi-colon, with a syntax of
- <code>name=value</code>. Common parameters include:
+ The <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME media type</a> of
+ the document, with optional parameters. Parameters are
+ separated from the media type and from one another by a
+ semi-colon, with a syntax of <code>name=value</code>. Common
+ parameters include:
<dl>
<dt><code>level</code></dt>
<p><span>Available Languages: </span><a href="../en/mod/mod_negotiation.html" hreflang="en" rel="alternate" title="English"> en </a> |
<a href="../ja/mod/mod_negotiation.html" title="Japanese"> ja </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">ÀâÌÀ:</a></th><td><a href="../content-negotiation.html">¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó</a>
µ¡Ç½¤òÄ󶡤¹¤ë</td></tr>
<tr><th><a href="module-dict.html#Status">¥¹¥Æ¡¼¥¿¥¹:</a></th><td>Base</td></tr>
<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 151408 -->
+<!-- English Revision: 151408:290816 (outdated) -->
<!--
Copyright 2002-2005 The Apache Software Foundation or its licensors,
<variants>
<variant>en</variant>
- <variant>ja</variant>
+ <variant outdated="yes">ja</variant>
</variants>
</metafile>
<li>
'<strong><code>type|T</code></strong>=<em>MIME-type</em>'
(force MIME <strong>t</strong>ype)<br />
- Force the MIME-type of the target file to be
+ Force the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> of the target file to be
<em>MIME-type</em>. For instance, this can be used to
setup the content-type based on some conditions.
For example, the following snippet allows <code>.php</code> files to
<p>
This is an elegant Mutex variant where a Posix Semaphore is used when possible.
It is only available when the underlying platform
- and APR supports it.</p></li>
+ and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports it.</p></li>
<li><code>sysvsem</code>
<p>
This is a somewhat elegant Mutex variant where a SystemV IPC Semaphore is used when
possible. It is possible to "leak" SysV semaphores if processes crash before
the semaphore is removed. It is only available when the underlying platform
- and APR supports it.</p></li>
+ and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports it.</p></li>
<li><code>sem</code>
<p>
This directive tells the SSL Module to pick the "best" semaphore implementation
available to it, choosing between Posix and SystemV IPC, in that order. It is only
- available when the underlying platform and APR supports at least one of the 2.</p></li>
+ available when the underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports at least one of the 2.</p></li>
<li><code>pthread</code>
<p>
This directive tells the SSL Module to use Posix thread mutexes. It is only available
- if the underlying platform and APR supports it.</p></li>
+ if the underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports it.</p></li>
<li><code>fcntl:/path/to/mutex</code>
<p>
This is a portable Mutex variant where a physical (lock-)file and the <code>fcntl()</code>
fucntion are used as the Mutex.
Always use a local disk filesystem for <code>/path/to/mutex</code> and never a file
residing on a NFS- or AFS-filesystem. It is only available when the underlying platform
- and APR supports it. Note: Internally, the Process ID (PID) of the
+ and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports it. Note: Internally, the Process ID (PID) of the
Apache parent process is automatically appended to
<code>/path/to/mutex</code> to make it unique, so you don't have to worry
about conflicts yourself. Notice that this type of mutex is not available
This is similar to the <code>fcntl:/path/to/mutex</code> method with the
exception that the <code>flock()</code> function is used to provide file
locking. It is only available when the underlying platform
- and APR supports it.</p></li>
+ and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports it.</p></li>
<li><code>file:/path/to/mutex</code>
<p>
This directive tells the SSL Module to pick the "best" file locking implementation
available to it, choosing between <code>fcntl</code> and <code>flock</code>,
- in that order. It is only available when the underlying platform and APR supports
+ in that order. It is only available when the underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> supports
at least one of the 2.</p></li>
<li><code>default | yes</code>
<p>
This directive tells the SSL Module to pick the default locking implementation
- as determined by the platform and APR.</p></li>
+ as determined by the platform and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a>.</p></li>
</ul>
<div class="example"><h3>Example</h3><p><code>
SSLMutex file:/usr/local/apache/logs/ssl_mutex
</div><div id="footer">
<p class="apache">Copyright 1995-2005 The Apache Software Foundation or its licensors, as applicable.<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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
-</body></html>
+</body></html>
\ No newline at end of file
<dt>Regular Expression Library Updated</dt>
<dd>Version 5.0 of the
<a href="http://www.pcre.org/">Perl Compatible Regular Expression
- Library</a> (PCRE) is now included.</dd>
+ Library</a> (PCRE) is now included. <code class="program"><a href="./programs/httpd.html">httpd</a></code> can be
+ configured to use a system installation of PCRE by passing the
+ <code>--with-pcre</code> flag to configure.</dd>
<dt>Smart Filtering</dt>
<dd><code class="module"><a href="./mod/mod_filter.html">mod_filter</a></code> introduces dynamic configuration
<h2><a name="developer" id="developer">Module Developer Changes</a></h2>
<dl>
- <dt>APR 1.0 API</dt>
+ <dt><a class="glossarylink" href="./glossary.html#apr" title="see glossary">APR</a> 1.0 API</dt>
<dd>Apache 2.2 uses the APR 1.0 API. All deprecated functions and
symbols have been removed from <code>APR</code> and
<dt>Monitor hook added</dt>
<dd>Monitor hook enables modules to run regular/scheduled jobs
in the parent (root) process.</dd>
+
+ <dt>Regular expression API changes</dt>
+
+ <dd>The <code>pcreposix.h</code> header is no longer available;
+ it is replaced by the new <code>ap_regex.h</code> header. The
+ POSIX.2 <code>regex.h</code> implementation exposed by the old
+ header is now available under the <code>ap_</code> namespace
+ from <code>ap_regex.h</code>. Calls to <code>regcomp</code>,
+ <code>regexec</code> and so on can be replaced by calls to
+ <code>ap_regcomp</code>, <code>ap_regcomp</code>.</dd>
+
</dl>
</div></div>
<div class="bottomlang">
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ko.xsl"?>
-<!-- English Revision: 105989:264105 (outdated) -->
+<!-- English Revision: 105989:290931 (outdated) -->
<!--
Copyright 2004-2005 The Apache Software Foundation or its licensors,
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.pt-br.xsl"?>
-<!-- English Revision: 151408:264105 (outdated) -->
+<!-- English Revision: 151408:290931 (outdated) -->
<!--
Copyright 2005 The Apache Software Foundation or its licensors,
to the server without this module.</dd>
<dt><code>--disable-mime</code></dt>
- <dd><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> associates the requested filename's
- extensions with the file's behavior and content (mime-type,
- language, character set and encoding). Disabling the mapping of
- file-extensions to MIME is normally not recommended.</dd>
+ <dd><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> associates the requested
+ filename's extensions with the file's behavior and content
+ (<a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">mime-type</a>, language, character set and
+ encoding). Disabling this module is normally not recommended.</dd>
<dt><code>--disable-negotiation</code></dt>
<dd>Disable content negotiation provided by
<dd>Enable memory caching provided by
<code class="module"><a href="../mod/mod_mem_cache.html">mod_mem_cache</a></code>.</dd>
- <dt><code>--enable-mime-magic</code></dt>
- <dd>Enable automatical determining of MIME types, which is provided by
- <code class="module"><a href="../mod/mod_mime_magic.html">mod_mime_magic</a></code>.</dd>
+ <dt><code>--enable-mime-magic</code></dt>
+ <dd>Enable
+ automatical determining of <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME
+ types</a>, which is provided by
+ <code class="module"><a href="../mod/mod_mime_magic.html">mod_mime_magic</a></code>.</dd>
<dt><code>--enable-isapi</code></dt>
<dd>Enable the isapi extension support provided by
<h4><a name="packageopt" id="packageopt">Specific packages</a></h4>
<dl>
<dt><code>--with-apr=<var>DIR</var>|<var>FILE</var></code></dt>
- <dd>The Apache Portable Runtime (APR) is part of the httpd
+ <dd>The <a class="glossarylink" href="../glossary.html#apr" title="see glossary">Apache Portable Runtime</a> (APR)
+ is part of the httpd
source distribution and will automatically be build together with the
HTTP server. If you want to use an already installed APR instead you
have to tell <code>configure</code> the path to the
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 105989:201979 (outdated) -->
+<!-- English Revision: 105989:290816 (outdated) -->
<!--
Copyright 2004-2005 The Apache Software Foundation or its licensors,
<dt><code>-f</code></dt>
<dd>Specify the DBM type to be used for the output. If not specified, will
- use the APR Default. Available types are:<br />
+ use the <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> Default. Available types are:<br />
<code>GDBM</code> for GDBM files<br />
<code>SDBM</code> for SDBM files<br />
<code>DB</code> for berkeley DB files<br />
projects / apache / commitdiff