diff options
Diffstat (limited to 'rubbos/app/httpd-2.0.64/docs/manual/misc')
27 files changed, 10864 insertions, 0 deletions
diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/custom_errordocs.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/custom_errordocs.html new file mode 100644 index 00000000..23ab34ae --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/custom_errordocs.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: custom_errordocs.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/custom_errordocs.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/custom_errordocs.html.en new file mode 100644 index 00000000..fc2ccd8e --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/custom_errordocs.html.en @@ -0,0 +1,577 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>International Customized Server Error Messages - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>International Customized Server Error Messages</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/custom_errordocs.html" title="English"> en </a></p> +</div> + + + <div class="warning"><h3>Warning:</h3> + <p>This document has not been fully updated + to take into account changes made in the 2.0 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <p>This document describes an easy way to provide your Apache + HTTP Server with a set of customized error messages which take + advantage of <a href="../content-negotiation.html">Content + Negotiation</a> and <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> to return + error messages generated by the server in the client's native + language.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#intro">Introduction</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#createdir">Creating an ErrorDocument directory</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#proxy">Customizing Proxy Error Messages</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#listings">HTML Listing of the Discussed Example</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="intro" id="intro">Introduction</a></h2> + + + + <p>By using SSI, all <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> messages + can share a homogenous and consistent style and layout, and + maintenance work (changing images, changing links) is kept to a + minimum because all layout information can be kept in a single + file.</p> + + <p>Error documents can be shared across different servers, or + even hosts, because all varying information is inserted at the + time the error document is returned on behalf of a failed + request.</p> + + <p>Content Negotiation then selects the appropriate language + version of a particular error message text, honoring the + language preferences passed in the client's request. (Users + usually select their favorite languages in the preferences + options menu of today's browsers). When an error document in + the client's primary language version is unavailable, the + secondary languages are tried or a default (fallback) version + is used.</p> + + <p>You have full flexibility in designing your error documents + to your personal taste (or your company's conventions). For + demonstration purposes, we present a simple generic error + document scheme. For this hypothetic server, we assume that all + error messages...</p> + + <ul> + <li>possibly are served by different virtual hosts (different + host name, different IP address, or different port) on the + server machine,</li> + + <li>show a predefined company logo in the right top of the + message (selectable by virtual host),</li> + + <li>print the error title first, followed by an explanatory + text and (depending on the error context) help on how to + resolve the error,</li> + + <li>have some kind of standardized background image,</li> + + <li>display an apache logo and a feedback email address at + the bottom of the error message.</li> + </ul> + + <p>An example of a "document not found" message for a german + client might look like this:</p> + + <p><img src="../images/custom_errordocs.gif" alt="[Needs graphics capability to display]" /></p> + + <p>All links in the document as well as links to the server's + administrator mail address, and even the name and port of the + serving virtual host are inserted in the error document at + "run-time", i.e., when the error actually occurs.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="createdir" id="createdir">Creating an ErrorDocument directory</a></h2> + + + + <p>For this concept to work as easily as possible, we must take + advantage of as much server support as we can get:</p> + + <ol> + <li>By defining the MultiViews <code class="directive"><a href="../mod/core.html#options">Options</a></code>, we + enable the language selection of the most appropriate + language alternative (content negotiation).</li> + + <li>By setting the <code class="directive"><a href="../mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code> + directive we define a set of default fallback languages in + the situation where the client's browser did not express any + preference at all.</li> + + <li>By enabling <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> + (and disallowing execution of cgi scripts for + security reasons), we allow the server to include building + blocks of the error message, and to substitute the value of + certain environment variables into the generated document + (dynamic HTML) or even to conditionally include or omit parts + of the text.</li> + + <li>The <code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code> and <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> directives + are useful for automatically SSI-expanding all files with a + <code>.shtml</code> suffix to <em>text/html</em>.</li> + + <li>By using the <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code> directive, we + keep the error document directory outside of the document + tree because it can be regarded more as a server part than + part of the document tree.</li> + + <li>The <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> block + restricts these "special" settings to the error document + directory and avoids an impact on any of the settings for the + regular document tree.</li> + + <li>For each of the error codes to be handled (see RFC2068 + for an exact description of each error code, or look at + <code>src/main/http_protocol.c</code> if you wish to see + apache's standard messages), an <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> in + the aliased <code>/errordocs</code> directory is defined. + Note that we only define the basename of the document here + because the MultiViews option will select the best candidate + based on the language suffixes and the client's preferences. + Any error situation with an error code <em>not</em> handled + by a custom document will be dealt with by the server in the + standard way (<em>i.e.</em>, a plain error message in + english).</li> + + <li>Finally, the <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive tells + apache that it is not necessary to look for a .htaccess file + in the /errordocs directory: a minor speed optimization.</li> + </ol> + + <p>The resulting <code>httpd.conf</code> configuration would then + look similar to this:</p> + + <div class="note"><h3>Note</h3>Note that you can define your own + error messages using this method for only part of the document + tree, e.g., a /~user/ subtree. In this case, the configuration + could as well be put into the .htaccess file at the root of the + subtree, and the <Directory> and </Directory> + directives -but not the contained directives- must be + omitted.</div> + +<div class="example"><p><code> + LanguagePriority en fr de <br /> + Alias /errordocs /usr/local/apache/errordocs <br /> + <br /> + <Directory /usr/local/apache/errordocs> <br /> + <span class="indent"> + AllowOverride none <br /> + Options MultiViews IncludesNoExec FollowSymLinks <br /> + AddType text/html .shtml <br /> + <FilesMatch "\.shtml[.$]"> <br /> + <span class="indent"> + SetOutputFilter INCLUDES <br /> + </span> + </FilesMatch> <br /> + </span> + </Directory> <br /> + <br /> + # "400 Bad Request", <br /> + ErrorDocument 400 /errordocs/400 <br /> + # "401 Authorization Required", <br /> + ErrorDocument 401 /errordocs/401 <br /> + # "403 Forbidden", <br /> + ErrorDocument 403 /errordocs/403 <br /> + # "404 Not Found", <br /> + ErrorDocument 404 /errordocs/404 <br /> + # "500 Internal Server Error", <br /> + ErrorDocument 500 /errordocs/500 <br /> +</code></p></div> + + <p>The directory for the error messages (here: + <code>/usr/local/apache/errordocs/</code>) must then be created + with the appropriate permissions (readable and executable by + the server uid or gid, only writable for the administrator).</p> + + <h3><a name="naming" id="naming">Naming the Individual Error Document files</a></h3> + + + + <p>By defining the <code>MultiViews</code> option, the server was + told to automatically scan the directory for matching variants + (looking at language and content type suffixes) when a + requested document was not found. In the configuration, we + defined the names for the error documents to be just their + error number (without any suffix).</p> + + <p>The names of the individual error documents are now + determined like this (I'm using 403 as an example, think of it + as a placeholder for any of the configured error + documents):</p> + + <ul> + <li>No file errordocs/403 should exist. Otherwise, it would + be found and served (with the DefaultType, usually + text/plain), all negotiation would be bypassed.</li> + + <li>For each language for which we have an internationalized + version (note that this need not be the same set of languages + for each error code - you can get by with a single language + version until you actually <em>have</em> translated + versions), a document + <code>errordocs/403.shtml.<em>lang</em></code> is created and + filled with the error text in that language (<a href="#createdocs">see below</a>).</li> + + <li>One fallback document called + <code>errordocs/403.shtml</code> is created, usually by + creating a symlink to the default language variant (<a href="#fallback">see below</a>).</li> + </ul> + + + <h3><a name="headfoot" id="headfoot">The Common Header and Footer Files</a></h3> + + + + <p>By putting as much layout information in two special "include + files", the error documents can be reduced to a bare minimum.</p> + + <p>One of these layout files defines the HTML document header + and a configurable list of paths to the icons to be shown in + the resulting error document. These paths are exported as a set + of SSI environment variables and are later evaluated by the + "footer" special file. The title of the current error (which is + put into the TITLE tag and an H1 header) is simply passed in + from the main error document in a variable called + <code>title</code>.</p> + + <p><strong>By changing this file, the layout of all generated + error messages can be changed in a second.</strong> (By + exploiting the features of SSI, you can easily define + different layouts based on the current virtual host, or even + based on the client's domain name).</p> + + <p>The second layout file describes the footer to be displayed + at the bottom of every error message. In this example, it shows + an apache logo, the current server time, the server version + string and adds a mail reference to the site's webmaster.</p> + + <p>For simplicity, the header file is simply called + <code>head.shtml</code> because it contains server-parsed + content but no language specific information. The footer file + exists once for each language translation, plus a symlink for + the default language.</p> + +<div class="example"><p><code> +for English, French and German versions (default english) <br /> +<br /> +foot.shtml.en, <br /> +foot.shtml.fr, <br /> +foot.shtml.de, <br /> +foot.shtml symlink to <br /> +foot.shtml.en +</code></p></div> + + <p>Both files are included into the error document by using the + directives <code><!--#include virtual="head" --></code> + and <code><!--#include virtual="foot" --></code> + respectively: the rest of the magic occurs in mod_negotiation + and in mod_include.</p> + + <p>See <a href="#listings">the listings below</a> to see an + actual HTML implementation of the discussed example.</p> + + + <h3><a name="createdocs" id="createdocs">Creating ErrorDocuments in Different Languages</a></h3> + + + + <p>After all this preparation work, little remains to be said + about the actual documents. They all share a simple common + structure:</p> + +<div class="example"><p><code> +<!--#set var="title" value="<em>error description title</em>" --> <br /> +<!--#include virtual="head" --> <br /> +<span class="indent"> + <em>explanatory error text</em> <br /> +</span> +<!--#include virtual="foot" --> +</code></p></div> + + <p>In the <a href="#listings">listings section</a>, you can see an + example of a [400 Bad Request] error document. Documents as + simple as that certainly cause no problems to translate or + expand.</p> + + + <h3><a name="fallback" id="fallback">The Fallback Language</a></h3> + + + + <p>Do we need a special handling for languages other than those we + have translations for? We did set the LanguagePriority, didn't + we?!</p> + + <p>Well, the LanguagePriority directive is for the case where + the client does not express any language priority at all. But + what happens in the situation where the client wants one of the + languages we do not have, and none of those we do have?</p> + + <p>Without doing anything, the Apache server will usually + return a [406 no acceptable variant] error, listing the choices + from which the client may select. But we're in an error message + already, and important error information might get lost when + the client had to choose a language representation first.</p> + + <p>So, in this situation it appears to be easier to define a + fallback language (by copying or linking, <em>e.g.</em>, the + english version to a language-less version). Because the + negotiation algorithm prefers "more specialized" variants over + "more generic" variants, these generic alternatives will only + be chosen when the normal negotiation did not succeed.</p> + + <p>A simple shell script to do it (execute within the + errordocs/ dir):</p> + +<div class="example"><p><code> + for f in *.shtml.en <br /> + do <br /> + <span class="indent"> + ln -s $f `basename $f .en` <br /> + </span> + done +</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="proxy" id="proxy">Customizing Proxy Error Messages</a></h2> + + + + <p>As of Apache-1.3, it is possible to use the + <code>ErrorDocument</code> mechanism for proxy error messages + as well (previous versions always returned fixed predefined + error messages).</p> + + <p>Most proxy errors return an error code of [500 Internal + Server Error]. To find out whether a particular error document + was invoked on behalf of a proxy error or because of some other + server error, and what the reason for the failure was, you can + check the contents of the new <code>ERROR_NOTES</code> CGI + environment variable: if invoked for a proxy error, this + variable will contain the actual proxy error message text in + HTML form.</p> + + <p>The following excerpt demonstrates how to exploit the + <code>ERROR_NOTES</code> variable within an error document:</p> + +<div class="example"><p><code> + <!--#if expr="$REDIRECT_ERROR_NOTES = ''" --> <br /> + <br /> + <p> <br /> + <span class="indent"> + The server encountered an unexpected condition <br /> + which prevented it from fulfilling the request. <br /> + </span> + </p> <br /> +<br /> + <p> <br /> + <span class="indent"> + <a href="mailto:<!--#echo var="SERVER_ADMIN" -->" <br /> + SUBJECT="Error message [<!--#echo var="REDIRECT_STATUS" -->] <!--#echo var="title" --> for <!--#echo var="REQUEST_URI" -->"> <br /> + Please forward this error screen to <!--#echo var="SERVER_NAME" -->'s <br /> + WebMaster</a>; it includes useful debugging information about <br /> + the Request which caused the error. <br /> +<br /> + <pre><!--#printenv --></pre> <br /> + </span> + </p> <br /> + <br /> + <!--#else --> <br /> + <span class="indent"> + <!--#echo var="REDIRECT_ERROR_NOTES" --><br /> + </span> +<br /> + <!--#endif --> +</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="listings" id="listings">HTML Listing of the Discussed Example</a></h2> + + + + <p>So, to summarize our example, here's the complete listing of + the <code>400.shtml.en</code> document. You will notice that it + contains almost nothing but the error text (with conditional + additions). Starting with this example, you will find it easy + to add more error documents, or to translate the error + documents to different languages.</p> + +<div class="example"><p><code> +<!--#set var="title" value="Bad Request"--> <br /> +<!--#include virtual="head" --><br /> +<br /> + <p> <br /> + <span class="indent"> + Your browser sent a request that this server could not understand: <br /> + <blockquote> <br /> + <span class="indent"> + <strong><!--#echo var="REQUEST_URI" --></strong><br /> + </span> + </blockquote> <br /> + <br /> + The request could not be understood by the server due to malformed <br /> + syntax. The client should not repeat the request without <br /> + modifications. <br /> + </span> + </p> <br /> +<br /> + <p> <br /> + <span class="indent"> + <!--#if expr="$HTTP_REFERER != ''" --> <br /> + <span class="indent"> + Please inform the owner of <br /> + <a href="<!--#echo var="HTTP_REFERER" -->">the referring page</a> about <br /> + the malformed link. <br /> + </span> + <br /> + <!--#else --> <br /> + <span class="indent"> + Please check your request for typing errors and retry. <br /> + </span> + <br /> + <!--#endif --> <br /> + </span> + </p> <br /> +<br /> +<!--#include virtual="foot" --> +</code></p></div> + + <p>Here is the complete <code>head.shtml.en</code> file (the funny + line breaks avoid empty lines in the document after SSI + processing). Note the configuration section at top. That's + where you configure the images and logos as well as the apache + documentation directory. Look how this file displays two + different logos depending on the content of the virtual host + name ($SERVER_NAME), and that an animated apache logo is shown + if the browser appears to support it (the latter requires + server configuration lines of the form </p> + + <div class="example"><p><code>BrowserMatch "^Mozilla/[2-4]" anigif</code></p></div> + + <p>for browser types which support animated GIFs).</p> + +<div class="example"><p><code> +<!--#if expr="$SERVER_NAME = /.*\.mycompany\.com/" --><br /> +<span class="indent"> +<!--#set var="IMG_CorpLogo" value="http://$SERVER_NAME:$SERVER_PORT/errordocs/CorpLogo.gif" --><br /> +<!--#set var="ALT_CorpLogo" value="Powered by Linux!" --><br /> +</span> +<br /> +<!--#else --> <br /> +<span class="indent"> +<!--#set var="IMG_CorpLogo" value="http://$SERVER_NAME:$SERVER_PORT/errordocs/PrivLogo.gif" --> <br /> +<!--#set var="ALT_CorpLogo" value="Powered by Linux!" --> <br /> +</span> +<!--#endif--> <br /> +<br /> +<!--#set var="IMG_BgImage" value="http://$SERVER_NAME:$SERVER_PORT/errordocs/BgImage.gif" --> <br /> +<!--#set var="DOC_Apache" value="http://$SERVER_NAME:$SERVER_PORT/Apache/" --> <br /> +<br /> +<!--#if expr="$anigif" --> <br /> +<span class="indent"> +<!--#set var="IMG_Apache" value="http://$SERVER_NAME:$SERVER_PORT/icons/apache_anim.gif" --> <br /> +</span> +<!--#else--><br /> +<span class="indent"> +<!--#set var="IMG_Apache" value="http://$SERVER_NAME:$SERVER_PORT/icons/apache_pb.gif" --><br /> +</span> +<!--#endif--><br /> +<br /> + +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> <br /> +<html> <br /> +<head> <br /> + <span class="indent"> + <title> <br /> + [<!--#echo var="REDIRECT_STATUS" -->] <!--#echo var="title" --> <br /> + </title> <br /> + </span> +</head> <br /> +<br /> +<body bgcolor="white" background="<!--#echo var="IMG_BgImage" -->"> <br /> +<span class="indent"> + <h1 align="center"> <br /> + [<!--#echo var="REDIRECT_STATUS" -->] + <!--#echo var="title" --> <br /> + <img src="<!--#echo var="IMG_CorpLogo" -->" <br /> + alt="<!--#echo var="ALT_CorpLogo" -->" align="right"> <br /> + </h1> <br /> +<br /> + <hr /> + <!-- ======================================================== --> <br /> + <div> +</span> +</code></p></div> + + <p>and this is the <code>foot.shtml.en</code> file:</p> + +<div class="example"><p><code> +<span class="indent"> + </div> <br /> + <hr /> <br /> + <br /> + <div align="right"> <br /> + <span class="indent"> + <small>Local Server time: + <!--#echo var="DATE_LOCAL" --></small> <br /> + </span> + </div> <br /> + <br /> + <div align="center"><br /> + <span class="indent"> + <a href="<!--#echo var="DOC_Apache" -->"> <br /> + <img src="<!--#echo var="IMG_Apache" -->" border="0" align="bottom" <br /> + alt="Powered by <!--#echo var="SERVER_SOFTWARE" -->"></a> <br /> + <br /><br /> + + <small><!--#set var="var" value="Powered by $SERVER_SOFTWARE -- <br /> + File last modified on $LAST_MODIFIED" --> <br /> + <!--#echo var="var" --></small> <br /> + </span> + </div> <br /> + <br /> + <p>If the indicated error looks like a misconfiguration, please inform <br /> + <a href="mailto:<!--#echo var="SERVER_ADMIN" -->" <br /> + subject="Feedback about Error message [<!--#echo var="REDIRECT_STATUS" -->] <br /> + <!--#echo var="title" -->, req=<!--#echo var="REQUEST_URI" -->"> <br /> + <!--#echo var="SERVER_NAME" -->'s WebMaster</a>.<br /> + </p><br /> + </span> +<br /> +</body><br /> +</html> +</code></p></div> + + <p>If you have tips to contribute, send mail to <a href="mailto:martin@apache.org">martin@apache.org</a></p> + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/custom_errordocs.html" title="English"> en </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/descriptors.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/descriptors.html new file mode 100644 index 00000000..e751d582 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/descriptors.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: descriptors.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/descriptors.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/descriptors.html.en new file mode 100644 index 00000000..005356d6 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/descriptors.html.en @@ -0,0 +1,233 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Descriptors and Apache - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Descriptors and Apache</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/descriptors.html" title="English"> en </a></p> +</div> + + + <div class="warning"><h3>Warning:</h3> + <p>This document has not been fully updated + to take into account changes made in the 2.0 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <p>A <em>descriptor</em>, also commonly called a <em>file + handle</em> is an object that a program uses to read or write + an open file, or open network socket, or a variety of other + devices. It is represented by an integer, and you may be + familiar with <code>stdin</code>, <code>stdout</code>, and + <code>stderr</code> which are descriptors 0, 1, and 2 + respectively. Apache needs a descriptor for each log file, plus + one for each network socket that it listens on, plus a handful + of others. Libraries that Apache uses may also require + descriptors. Normal programs don't open up many descriptors at + all, and so there are some latent problems that you may + experience should you start running Apache with many + descriptors (<em>i.e.</em>, with many virtual hosts).</p> + + <p>The operating system enforces a limit on the number of + descriptors that a program can have open at a time. There are + typically three limits involved here. One is a kernel + limitation, depending on your operating system you will either + be able to tune the number of descriptors available to higher + numbers (this is frequently called <em>FD_SETSIZE</em>). Or you + may be stuck with a (relatively) low amount. The second limit + is called the <em>hard resource</em> limit, and it is sometimes + set by root in an obscure operating system file, but frequently + is the same as the kernel limit. The third limit is called the + <em>soft resource</em> limit. The soft limit is always less + than or equal to the hard limit. For example, the hard limit + may be 1024, but the soft limit only 64. Any user can raise + their soft limit up to the hard limit. Root can raise the hard + limit up to the system maximum limit. The soft limit is the + actual limit that is used when enforcing the maximum number of + files a process can have open.</p> + + <p>To summarize:</p> + +<div class="example"><p><code> + #open files <= soft limit <= hard limit <= kernel limit +</code></p></div> + + + <p>You control the hard and soft limits using the + <code>limit</code> (csh) or <code>ulimit</code> (sh) + directives. See the respective man pages for more information. + For example you can probably use <code>ulimit -n + unlimited</code> to raise your soft limit up to the hard limit. + You should include this command in a shell script which starts + your webserver.</p> + + <p>Unfortunately, it's not always this simple. As mentioned + above, you will probably run into some system limitations that + will need to be worked around somehow. Work was done in version + 1.2.1 to improve the situation somewhat. Here is a partial list + of systems and workarounds (assuming you are using 1.2.1 or + later).</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#bsdi">BSDI 2.0</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#freebsd">FreeBSD 2.2, BSDI 2.1+</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#linux">Linux</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#solaris">Solaris through 2.5.1</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#AIX">AIX</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#sco">SCO OpenServer</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#tru64">Compaq Tru64 UNIX/Digital UNIX/OSF</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#others">Others</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="bsdi" id="bsdi">BSDI 2.0</a></h2> + + <p>Under BSDI 2.0 you can build Apache to support more + descriptors by adding <code>-DFD_SETSIZE=nnn</code> to + <code>EXTRA_CFLAGS</code> (where nnn is the number of + descriptors you wish to support, keep it less than the hard + limit). But it will run into trouble if more than + approximately 240 Listen directives are used. This may be + cured by rebuilding your kernel with a higher + FD_SETSIZE.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="freebsd" id="freebsd">FreeBSD 2.2, BSDI 2.1+</a></h2> + + <p>Similar to the BSDI 2.0 case, you should define + <code>FD_SETSIZE</code> and rebuild. But the extra Listen + limitation doesn't exist.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="linux" id="linux">Linux</a></h2> + + <p>By default Linux has a kernel maximum of 256 open + descriptors per process. There are several patches available + for the 2.0.x series which raise this to 1024 and beyond, and + you can find them in the "unofficial patches" section of <a href="http://www.linuxhq.com/">the Linux Information HQ</a>. + None of these patches are perfect, and an entirely different + approach is likely to be taken during the 2.1.x development. + Applying these patches will raise the FD_SETSIZE used to + compile all programs, and unless you rebuild all your + libraries you should avoid running any other program with a + soft descriptor limit above 256. As of this writing the + patches available for increasing the number of descriptors do + not take this into account. On a dedicated webserver you + probably won't run into trouble.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="solaris" id="solaris">Solaris through 2.5.1</a></h2> + + <p>Solaris has a kernel hard limit of 1024 (may be lower in + earlier versions). But it has a limitation that files using + the stdio library cannot have a descriptor above 255. Apache + uses the stdio library for the ErrorLog directive. When you + have more than approximately 110 virtual hosts (with an error + log and an access log each) you will need to build Apache + with <code>-DHIGH_SLACK_LINE=256</code> added to + <code>EXTRA_CFLAGS</code>. You will be limited to + approximately 240 error logs if you do this.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="AIX" id="AIX">AIX</a></h2> + + <p>AIX version 3.2?? appears to have a hard limit of 128 + descriptors. End of story. Version 4.1.5 has a hard limit of + 2000.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="sco" id="sco">SCO OpenServer</a></h2> + + <p>Edit the <code>/etc/conf/cf.d/stune</code> file or use + <code>/etc/conf/cf.d/configure</code> choice 7 (User and + Group configuration) and modify the <code>NOFILES</code> + kernel parameter to a suitably higher value. SCO recommends a + number between 60 and 11000, the default is 110. Relink and + reboot, and the new number of descriptors will be + available.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="tru64" id="tru64">Compaq Tru64 UNIX/Digital UNIX/OSF</a></h2> + + <ol> + <li>Raise <code>open_max_soft</code> and + <code>open_max_hard</code> to 4096 in the proc subsystem. + Do a man on sysconfig, sysconfigdb, and + sysconfigtab.</li> + + <li>Raise <code>max-vnodes</code> to a large number which + is greater than the number of apache processes * 4096 + (Setting it to 250,000 should be good for most people). + Do a man on sysconfig, sysconfigdb, and + sysconfigtab.</li> + + <li>If you are using Tru64 5.0, 5.0A, or 5.1, define + <code>NO_SLACK</code> to work around a bug in the OS. + <code>CFLAGS="-DNO_SLACK" ./configure</code></li> + </ol> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="others" id="others">Others</a></h2> + + <p>If you have details on another operating system, please + submit it through our <a href="http://httpd.apache.org/bug_report.html">Bug Report + Page</a>.</p> + + <p>In addition to the problems described above there are + problems with many libraries that Apache uses. The most common + example is the bind DNS resolver library that is used by pretty + much every unix, which fails if it ends up with a descriptor + above 256. We suspect there are other libraries that similar + limitations. So the code as of 1.2.1 takes a defensive stance + and tries to save descriptors less than 16 for use while + processing each request. This is called the <em>low slack + line</em>.</p> + + <p>Note that this shouldn't waste descriptors. If you really + are pushing the limits and Apache can't get a descriptor above + 16 when it wants it, it will settle for one below 16.</p> + + <p>In extreme situations you may want to lower the low slack + line, but you shouldn't ever need to. For example, lowering it + can increase the limits 240 described above under Solaris and + BSDI 2.0. But you'll play a delicate balancing game with the + descriptors needed to serve a request. Should you want to play + this game, the compile time parameter is + <code>LOW_SLACK_LINE</code> and there's a tiny bit of + documentation in the header file <code>httpd.h</code>.</p> + + <p>Finally, if you suspect that all this slack stuff is causing + you problems, you can disable it. Add <code>-DNO_SLACK</code> + to <code>EXTRA_CFLAGS</code> and rebuild. But please report it + to our <a href="http://httpd.apache.org/bug_report.html">Bug + Report Page</a> so that we can investigate. </p> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/descriptors.html" title="English"> en </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/fin_wait_2.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/fin_wait_2.html new file mode 100644 index 00000000..64957238 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/fin_wait_2.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: fin_wait_2.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/fin_wait_2.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/fin_wait_2.html.en new file mode 100644 index 00000000..60da4b0d --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/fin_wait_2.html.en @@ -0,0 +1,422 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Connections in the FIN_WAIT_2 state and Apache - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Connections in the FIN_WAIT_2 state and Apache</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/fin_wait_2.html" title="English"> en </a></p> +</div> + + + <div class="warning"><h3>Warning:</h3> + <p>This document has not been fully updated + to take into account changes made in the 2.0 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <p>Starting with the Apache 1.2 betas, people are reporting + many more connections in the FIN_WAIT_2 state (as reported + by <code>netstat</code>) than they saw using older + versions. When the server closes a TCP connection, it sends + a packet with the FIN bit set to the client, which then + responds with a packet with the ACK bit set. The client + then sends a packet with the FIN bit set to the server, + which responds with an ACK and the connection is closed. + The state that the connection is in during the period + between when the server gets the ACK from the client and + the server gets the FIN from the client is known as + FIN_WAIT_2. See the <a href="ftp://ds.internic.net/rfc/rfc793.txt">TCP RFC</a> for + the technical details of the state transitions.</p> + + <p>The FIN_WAIT_2 state is somewhat unusual in that there + is no timeout defined in the standard for it. This means + that on many operating systems, a connection in the + FIN_WAIT_2 state will stay around until the system is + rebooted. If the system does not have a timeout and too + many FIN_WAIT_2 connections build up, it can fill up the + space allocated for storing information about the + connections and crash the kernel. The connections in + FIN_WAIT_2 do not tie up an httpd process.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#why">Why Does It Happen?</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#what">What Can I Do About it?</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#appendix">Appendix</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="why" id="why">Why Does It Happen?</a></h2> + + <p>There are numerous reasons for it happening, some of them + may not yet be fully clear. What is known follows.</p> + + <h3><a name="buggy" id="buggy">Buggy Clients and Persistent + Connections</a></h3> + + <p>Several clients have a bug which pops up when dealing with + persistent connections (aka + keepalives). When the connection is idle and the server + closes the connection (based on the <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code>), + the client is programmed so that the client does not send + back a FIN and ACK to the server. This means that the + connection stays in the FIN_WAIT_2 state until one of the + following happens:</p> + + <ul> + <li>The client opens a new connection to the same or a + different site, which causes it to fully close the older + connection on that socket.</li> + + <li>The user exits the client, which on some (most?) + clients causes the OS to fully shutdown the + connection.</li> + + <li>The FIN_WAIT_2 times out, on servers that have a + timeout for this state.</li> + </ul> + + <p>If you are lucky, this means that the buggy client will + fully close the connection and release the resources on + your server. However, there are some cases where the socket + is never fully closed, such as a dialup client + disconnecting from their provider before closing the + client. In addition, a client might sit idle for days + without making another connection, and thus may hold its + end of the socket open for days even though it has no + further use for it. <strong>This is a bug in the browser or + in its operating system's TCP implementation.</strong></p> + + <p>The clients on which this problem has been verified to + exist:</p> + + <ul> + <li>Mozilla/3.01 (X11; I; FreeBSD 2.1.5-RELEASE + i386)</li> + + <li>Mozilla/2.02 (X11; I; FreeBSD 2.1.5-RELEASE + i386)</li> + + <li>Mozilla/3.01Gold (X11; I; SunOS 5.5 sun4m)</li> + + <li>MSIE 3.01 on the Macintosh</li> + + <li>MSIE 3.01 on Windows 95</li> + </ul> + + <p>This does not appear to be a problem on:</p> + + <ul> + <li>Mozilla/3.01 (Win95; I)</li> + </ul> + + <p>It is expected that many other clients have the same + problem. What a client <strong>should do</strong> is + periodically check its open socket(s) to see if they have + been closed by the server, and close their side of the + connection if the server has closed. This check need only + occur once every few seconds, and may even be detected by a + OS signal on some systems (<em>e.g.</em>, Win95 and NT + clients have this capability, but they seem to be ignoring + it).</p> + + <p>Apache <strong>cannot</strong> avoid these FIN_WAIT_2 + states unless it disables persistent connections for the + buggy clients, just like we recommend doing for Navigator + 2.x clients due to other bugs. However, non-persistent + connections increase the total number of connections needed + per client and slow retrieval of an image-laden web page. + Since non-persistent connections have their own resource + consumptions and a short waiting period after each closure, + a busy server may need persistence in order to best serve + its clients.</p> + + <p>As far as we know, the client-caused FIN_WAIT_2 problem + is present for all servers that support persistent + connections, including Apache 1.1.x and 1.2.</p> + + + + <h3><a name="code" id="code">A necessary bit of code + introduced in 1.2</a></h3> + + <p>While the above bug is a problem, it is not the whole + problem. Some users have observed no FIN_WAIT_2 problems + with Apache 1.1.x, but with 1.2b enough connections build + up in the FIN_WAIT_2 state to crash their server. The most + likely source for additional FIN_WAIT_2 states is a + function called <code>lingering_close()</code> which was + added between 1.1 and 1.2. This function is necessary for + the proper handling of persistent connections and any + request which includes content in the message body + (<em>e.g.</em>, PUTs and POSTs). What it does is read any + data sent by the client for a certain time after the server + closes the connection. The exact reasons for doing this are + somewhat complicated, but involve what happens if the + client is making a request at the same time the server + sends a response and closes the connection. Without + lingering, the client might be forced to reset its TCP + input buffer before it has a chance to read the server's + response, and thus understand why the connection has + closed. See the <a href="#appendix">appendix</a> for more + details.</p> + + <p>The code in <code>lingering_close()</code> appears to + cause problems for a number of factors, including the + change in traffic patterns that it causes. The code has + been thoroughly reviewed and we are not aware of any bugs + in it. It is possible that there is some problem in the BSD + TCP stack, aside from the lack of a timeout for the + FIN_WAIT_2 state, exposed by the + <code>lingering_close</code> code that causes the observed + problems.</p> + + + </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 Can I Do About it?</a></h2> + + <p>There are several possible workarounds to the problem, some + of which work better than others.</p> + + <h3><a name="add_timeout" id="add_timeout">Add a timeout for FIN_WAIT_2</a></h3> + + <p>The obvious workaround is to simply have a timeout for the + FIN_WAIT_2 state. This is not specified by the RFC, and + could be claimed to be a violation of the RFC, but it is + widely recognized as being necessary. The following systems + are known to have a timeout:</p> + + <ul> + <li><a href="http://www.freebsd.org/">FreeBSD</a> + versions starting at 2.0 or possibly earlier.</li> + + <li><a href="http://www.netbsd.org/">NetBSD</a> version + 1.2(?)</li> + + <li><a href="http://www.openbsd.org/">OpenBSD</a> all + versions(?)</li> + + <li><a href="http://www.bsdi.com/">BSD/OS</a> 2.1, with + the <a href="ftp://ftp.bsdi.com/bsdi/patches/patches-2.1/K210-027"> + K210-027</a> patch installed.</li> + + <li><a href="http://www.sun.com/">Solaris</a> as of + around version 2.2. The timeout can be tuned by using + <code>ndd</code> to modify + <code>tcp_fin_wait_2_flush_interval</code>, but the + default should be appropriate for most servers and + improper tuning can have negative impacts.</li> + + <li><a href="http://www.linux.org/">Linux</a> 2.0.x and + earlier(?)</li> + + <li><a href="http://www.hp.com/">HP-UX</a> 10.x defaults + to terminating connections in the FIN_WAIT_2 state after + the normal keepalive timeouts. This does not refer to the + persistent connection or HTTP keepalive timeouts, but the + <code>SO_LINGER</code> socket option which is enabled by + Apache. This parameter can be adjusted by using + <code>nettune</code> to modify parameters such as + <code>tcp_keepstart</code> and <code>tcp_keepstop</code>. + In later revisions, there is an explicit timer for + connections in FIN_WAIT_2 that can be modified; contact + HP support for details.</li> + + <li><a href="http://www.sgi.com/">SGI IRIX</a> can be + patched to support a timeout. For IRIX 5.3, 6.2, and 6.3, + use patches 1654, 1703 and 1778 respectively. If you have + trouble locating these patches, please contact your SGI + support channel for help.</li> + + <li><a href="http://www.ncr.com/">NCR's MP RAS Unix</a> + 2.xx and 3.xx both have FIN_WAIT_2 timeouts. In 2.xx it + is non-tunable at 600 seconds, while in 3.xx it defaults + to 600 seconds and is calculated based on the tunable + "max keep alive probes" (default of 8) multiplied by the + "keep alive interval" (default 75 seconds).</li> + + <li><a href="http://www.sequent.com">Sequent's ptx/TCP/IP + for DYNIX/ptx</a> has had a FIN_WAIT_2 timeout since + around release 4.1 in mid-1994.</li> + </ul> + + <p>The following systems are known to not have a + timeout:</p> + + <ul> + <li><a href="http://www.sun.com/">SunOS 4.x</a> does not + and almost certainly never will have one because it as at + the very end of its development cycle for Sun. If you + have kernel source should be easy to patch.</li> + </ul> + + <p>There is a <a href="http://www.apache.org/dist/httpd/contrib/patches/1.2/fin_wait_2.patch"> + patch available</a> for adding a timeout to the FIN_WAIT_2 + state; it was originally intended for BSD/OS, but should be + adaptable to most systems using BSD networking code. You + need kernel source code to be able to use it.</p> + + + + <h3><a name="no_lingering" id="no_lingering">Compile without using + <code>lingering_close()</code></a></h3> + + <p>It is possible to compile Apache 1.2 without using the + <code>lingering_close()</code> function. This will result + in that section of code being similar to that which was in + 1.1. If you do this, be aware that it can cause problems + with PUTs, POSTs and persistent connections, especially if + the client uses pipelining. That said, it is no worse than + on 1.1, and we understand that keeping your server running + is quite important.</p> + + <p>To compile without the <code>lingering_close()</code> + function, add <code>-DNO_LINGCLOSE</code> to the end of the + <code>EXTRA_CFLAGS</code> line in your + <code>Configuration</code> file, rerun + <code class="program"><a href="../programs/Configure.html">Configure</a></code> and rebuild the server.</p> + + + + <h3><a name="so_linger" id="so_linger">Use <code>SO_LINGER</code> as + an alternative to <code>lingering_close()</code></a></h3> + + <p>On most systems, there is an option called + <code>SO_LINGER</code> that can be set with + <code>setsockopt(2)</code>. It does something very similar + to <code>lingering_close()</code>, except that it is broken + on many systems so that it causes far more problems than + <code>lingering_close</code>. On some systems, it could + possibly work better so it may be worth a try if you have + no other alternatives.</p> + + <p>To try it, add <code>-DUSE_SO_LINGER + -DNO_LINGCLOSE</code> to the end of the + <code>EXTRA_CFLAGS</code> line in your + <code>Configuration</code> file, rerun + <code class="program"><a href="../programs/Configure.html">Configure</a></code> and rebuild the server.</p> + + <div class="note"><h3>NOTE</h3>Attempting to use + <code>SO_LINGER</code> and <code>lingering_close()</code> + at the same time is very likely to do very bad things, so + don't.</div> + + + + <h3><a name="increase_mem" id="increase_mem">Increase the amount of memory + used for storing connection state</a></h3> + + <dl> + <dt>BSD based networking code:</dt> + + <dd> + BSD stores network data, such as connection states, in + something called an mbuf. When you get so many + connections that the kernel does not have enough mbufs + to put them all in, your kernel will likely crash. You + can reduce the effects of the problem by increasing the + number of mbufs that are available; this will not + prevent the problem, it will just make the server go + longer before crashing. + + <p>The exact way to increase them may depend on your + OS; look for some reference to the number of "mbufs" or + "mbuf clusters". On many systems, this can be done by + adding the line <code>NMBCLUSTERS="n"</code>, where + <code>n</code> is the number of mbuf clusters you want + to your kernel config file and rebuilding your + kernel.</p> + </dd> + </dl> + + + + <h3><a name="disable" id="disable">Disable KeepAlive</a></h3> + + <p>If you are unable to do any of the above then you + should, as a last resort, disable KeepAlive. Edit your + httpd.conf and change "KeepAlive On" to "KeepAlive + Off".</p> + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="appendix" id="appendix">Appendix</a></h2> + + <p>Below is a message from Roy Fielding, one of the authors + of HTTP/1.1.</p> + + <h3><a name="message" id="message">Why the lingering close + functionality is necessary with HTTP</a></h3> + + <p>The need for a server to linger on a socket after a close + is noted a couple times in the HTTP specs, but not + explained. This explanation is based on discussions between + myself, Henrik Frystyk, Robert S. Thau, Dave Raggett, and + John C. Mallery in the hallways of MIT while I was at W3C.</p> + + <p>If a server closes the input side of the connection + while the client is sending data (or is planning to send + data), then the server's TCP stack will signal an RST + (reset) back to the client. Upon receipt of the RST, the + client will flush its own incoming TCP buffer back to the + un-ACKed packet indicated by the RST packet argument. If + the server has sent a message, usually an error response, + to the client just before the close, and the client + receives the RST packet before its application code has + read the error message from its incoming TCP buffer and + before the server has received the ACK sent by the client + upon receipt of that buffer, then the RST will flush the + error message before the client application has a chance to + see it. The result is that the client is left thinking that + the connection failed for no apparent reason.</p> + + <p>There are two conditions under which this is likely to + occur:</p> + + <ol> + <li>sending POST or PUT data without proper + authorization</li> + + <li>sending multiple requests before each response + (pipelining) and one of the middle requests resulting in + an error or other break-the-connection result.</li> + </ol> + + <p>The solution in all cases is to send the response, close + only the write half of the connection (what shutdown is + supposed to do), and continue reading on the socket until + it is either closed by the client (signifying it has + finally read the response) or a timeout occurs. That is + what the kernel is supposed to do if SO_LINGER is set. + Unfortunately, SO_LINGER has no effect on some systems; on + some other systems, it does not have its own timeout and + thus the TCP memory segments just pile-up until the next + reboot (planned or not).</p> + + <p>Please note that simply removing the linger code will + not solve the problem -- it only moves it to a different + and much harder one to detect.</p> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/fin_wait_2.html" title="English"> en </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html new file mode 100644 index 00000000..23ec1ec0 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html.en new file mode 100644 index 00000000..81445841 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html.en @@ -0,0 +1,121 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache Miscellaneous Documentation - Apache HTTP Server</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 href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page" class="no-sidebar"><div id="page-header"> +<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> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="../"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a></div><div id="page-content"><div id="preamble"><h1>Apache Miscellaneous Documentation</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/" title="English"> en </a> | +<a href="../tr/misc/" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> +</div> + + + <p>Below is a list of additional documentation pages that apply + to the Apache web server development project.</p> + + <div class="warning"><h3>Warning</h3> + <p>Some of the documents below have not been fully updated + to take into account changes made in the 2.0 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <dl> + <dt><a href="custom_errordocs.html">How to use XSSI and + Negotiation for custom ErrorDocuments</a></dt> + + <dd> + <p>Describes a solution which uses XSSI and negotiation to + custom-tailor the Apache ErrorDocuments to taste, adding the + advantage of returning internationalized versions of the + error messages depending on the client's language + preferences.</p> + </dd> + + <dt><a href="descriptors.html">File Descriptor use in + Apache</a></dt> + + <dd> + <p>Describes how Apache uses file descriptors and talks + about various limits imposed on the number of descriptors + available by various operating systems.</p> + </dd> + + <dt><a href="fin_wait_2.html"><code>FIN_WAIT_2</code></a></dt> + + <dd> + <p>A description of the causes of Apache processes going + into the <code>FIN_WAIT_2</code> state, and what you can do + about it.</p> + </dd> + + <dt><a href="known_client_problems.html">Known Client + Problems</a></dt> + + <dd> + <p>A list of problems in HTTP clients which can be mitigated + by Apache.</p> + </dd> + + <dt><a href="perf-tuning.html">Performance Notes - Apache + Tuning</a></dt> + + <dd> + <p>Notes about how to (run-time and compile-time) configure + Apache for highest performance. Notes explaining why Apache + does some things, and why it doesn't do other things (which + make it slower/faster).</p> + </dd> + + <dt><a href="security_tips.html">Security Tips</a></dt> + + <dd> + <p>Some "do"s - and "don't"s - for keeping your Apache web + site secure.</p> + </dd> + + <dt><a href="rewriteguide.html">URL Rewriting Guide</a></dt> + <dd> + <p>This document supplements the <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + <a href="../mod/mod_rewrite.html">reference documentation</a>. + It describes how one can use Apache's <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + to solve typical URL-based problems webmasters are usually confronted + with in practice.</p> + </dd> + + <dt><a href="tutorials.html">Apache Tutorials</a></dt> + + <dd> + <p>A list of external resources which help to accomplish common + tasks with the Apache HTTP server.</p> + </dd> + + <dt><a href="relevant_standards.html">Relevant Standards</a></dt> + + <dd> + <p>This document acts as a reference page for most of the relevant + standards that Apache follows.</p> + </dd> + </dl> + </div> +</div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/" title="English"> en </a> | +<a href="../tr/misc/" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html.tr.utf8 b/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html.tr.utf8 new file mode 100644 index 00000000..e4cb8a26 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/index.html.tr.utf8 @@ -0,0 +1,122 @@ +<?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="tr" xml:lang="tr"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>횉e힊itli Belgeler - Apache HTTP Sunucusu</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 href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page" class="no-sidebar"><div id="page-header"> +<p class="menu"><a href="../mod/">Mod체ller</a> | <a href="../mod/directives.html">Y철nergeler</a> | <a href="../faq/">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas캇</a></p> +<p class="apache">Apache HTTP Sunucusu S체r체m 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="../"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Sunucusu</a> > <a href="http://httpd.apache.org/docs/">Belgeleme</a> > <a href="../">S체r체m 2.0</a></div><div id="page-content"><div id="preamble"><h1>횉e힊itli Belgeler</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/misc/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../tr/misc/" title="T체rk챌e"> tr </a></p> +</div> + + + <p>A힊a휓캇da listelenen belgeler de Apache HTTP sunucusu geli힊tirme projesi + kapsam캇ndad캇r.</p> + + <div class="warning"><h3>Uyar캇</h3> + <p>A힊a휓캇daki belgeler, Apache HTTP Sunucusunun 2.0 s체r체m체nde yap캇lm캇힊 + de휓i힊ikliklere g철re tam olarak g체ncellenmemi힊tir. Hala g체ncel kalm캇힊 + baz캇 bilgiler olabilir, fakat siz yine de bu belgeleri kullan캇rken + dikkatli olun.</p> + </div> + + <dl> + <dt><a href="custom_errordocs.html">Hata belgelerinin 철zelle힊tirilmesi + i챌in XSSI ve i챌erik uzla힊캇m캇n캇n kullan캇m캇</a></dt> + + <dd> + <p>Belgede, istemcinin dil tercihlerine ba휓l캇 olarak hata + iletilerinin yerelle힊tirilmi힊 s체r체mlerini d철nd체rmenin yan캇nda + Apache hata belgelerine bir 챌e힊ni katmak i챌in XSSI ve i챌erik + uzla힊캇m캇n캇n kullan캇m캇yla ilgili bir 챌철z체me yer verilmi힊tir.</p> + </dd> + + <dt><a href="descriptors.html">Apache��셝e dosya tan캇t캇c캇lar캇n캇n + kullan캇m캇</a></dt> + + <dd> + <p>Belgede, Apache��셬in 챌e힊itli i힊letim sistemleri taraf캇ndan + dayat캇lan dosya tan캇t캇c캇 miktarlar캇 i챌in i힊letim sistemleri ile + nas캇l anla힊t캇휓캇 ve bu dosya tan캇t캇c캇lar캇n캇 nas캇l kulland캇휓캇 + a챌캇klanm캇힊t캇r.</p> + </dd> + + <dt><a href="fin_wait_2.html"><code>FIN_WAIT_2</code></a></dt> + + <dd> + <p>Belgede, Apache��셬in <code>FIN_WAIT_2</code> durumuna girme + sebepleri ile bu konuda neler yap캇labilece휓i a챌캇klanm캇힊t캇r.</p> + </dd> + + <dt><a href="known_client_problems.html">Bilinen 캅stemci Sorunlar캇</a> + </dt> + + <dd> + <p>Belgede, HTTP istemcilerinden kaynaklanan baz캇 sorunlar캇n Apache + taraf캇ndan hafifletilebilenlerinin bir listesi yer almaktad캇r.</p> + </dd> + + <dt><a href="perf-tuning.html">Ba힊ar캇m Artt캇rma 캅pu챌lar캇 - Apache��셺e + 캅nce Ayar 횉ekilmesi</a></dt> + + <dd> + <p>Y체ksek ba힊ar캇m elde etmek i챌in Apache yap캇land캇rmas캇nda (챌al캇힊ma + an캇nda ve derleme s캇ras캇nda) yap캇lacaklar ile ilgili baz캇 bilgiler + yan캇nda Apache��셝e baz캇 힊eylerin (bir 힊eyleri h캇zland캇ran ve + yava힊latan 힊eylerin) yap캇lma ve yap캇lmama sebepleri + a챌캇klanm캇힊t캇r.</p> + </dd> + + <dt><a href="security_tips.html">G체venlik 캅pu챌lar캇</a></dt> + + <dd> + <p>Apache HTTP sitenizi g체venli k캇lmak i챌in yap캇lacaklar ve + yap캇lmayacaklar.</p> + </dd> + + <dt><a href="rewriteguide.html">URL Yeniden Yazma Rehberi</a></dt> + + <dd> + <p>Bu belge <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> mod체l체n체n <a href="../mod/mod_rewrite.html">ba힊vuru belgesi</a> yerine ge챌er. + Site y철neticilerinin s캇k챌a kar힊캇la힊t캇klar캇 belli ba힊l캇 URL temelli + sorunlar캇 챌철z체mlemek i챌in Apache��셬in <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + mod체l체n체n nas캇l kullan캇laca휓캇n캇 a챌캇klar.</p> + </dd> + + <dt><a href="tutorials.html">Apache 횜휓reticileri</a></dt> + + <dd> + <p>Apache HTTP Sunucusu ile ilgili g철revlerinizi yerine getirmenize + yard캇mc캇 olacak harici kaynaklar캇n bir listesi.</p> + </dd> + + <dt><a href="relevant_standards.html">캅lgili Standartlar</a></dt> + + <dd> + <p>Bu belge Apache��셬in uyaca휓캇 standartlar캇n bir 챌o휓una at캇fta + bulunmak amac캇yla haz캇rlanm캇힊t캇r.</p> + </dd> + </dl> + + </div> +</div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/misc/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../tr/misc/" title="T체rk챌e"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br /><a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> alt캇nda lisansl캇d캇r.</p> +<p class="menu"><a href="../mod/">Mod체ller</a> | <a href="../mod/directives.html">Y철nergeler</a> | <a href="../faq/">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas캇</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/known_client_problems.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/known_client_problems.html new file mode 100644 index 00000000..9f5b039f --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/known_client_problems.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: known_client_problems.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/known_client_problems.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/known_client_problems.html.en new file mode 100644 index 00000000..cfc02954 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/known_client_problems.html.en @@ -0,0 +1,408 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Known Problems in Clients - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Known Problems in Clients</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/known_client_problems.html" title="English"> en </a></p> +</div> + + + <div class="warning"><h3>Warning:</h3> + <p>This document has not been fully updated + to take into account changes made in the 2.0 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <p>Over time the Apache Group has discovered or been notified + of problems with various clients which we have had to work + around, or explain. This document describes these problems and + the workarounds available. It's not arranged in any particular + order. Some familiarity with the standards is assumed, but not + necessary.</p> + + <p>For brevity, <em>Navigator</em> will refer to Netscape's + Navigator product (which in later versions was renamed + "Communicator" and various other names), and <em>MSIE</em> will + refer to Microsoft's Internet Explorer product. All trademarks + and copyrights belong to their respective companies. We welcome + input from the various client authors to correct + inconsistencies in this paper, or to provide us with exact + version numbers where things are broken/fixed.</p> + + <p>For reference, <a href="ftp://ds.internic.net/rfc/rfc1945.txt">RFC1945</a> + defines HTTP/1.0, and <a href="ftp://ds.internic.net/rfc/rfc2068.txt">RFC2068</a> + defines HTTP/1.1. Apache as of version 1.2 is an HTTP/1.1 + server (with an optional HTTP/1.0 proxy).</p> + + <p>Various of these workarounds are triggered by environment + variables. The admin typically controls which are set, and for + which clients, by using <code>mod_browser</code>. Unless + otherwise noted all of these workarounds exist in versions 1.2 + and later.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#trailing-crlf">Trailing CRLF on POSTs</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#broken-keepalive">Broken KeepAlive</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#force-response-1.0">Incorrect interpretation of + <code>HTTP/1.1</code> in response</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#msie4.0b2">Requests use HTTP/1.1 but + responses must be in HTTP/1.0</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#byte-257">Boundary problems with + header parsing</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#boundary-string">Multipart responses and + Quoted Boundary Strings</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#byterange-requests">Byterange Requests</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#cookie-merge"><code>Set-Cookie</code> header is + unmergeable</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#gif89-expires"><code>Expires</code> headers + and GIF89A animations</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#no-content-length"><code>POST</code> without + <code>Content-Length</code></a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#jdk-12-bugs">JDK 1.2 betas lose + parts of responses.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#content-type-persistent"><code>Content-Type</code> + change is not noticed after reload</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#msie-cookie-y2k">MSIE Cookie + problem with expiry date in the year 2000</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#lynx-negotiate-trans">Lynx incorrectly asking for + transparent content negotiation</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ie40-vary">MSIE 4.0 mishandles Vary + response header</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="trailing-crlf" id="trailing-crlf">Trailing CRLF on POSTs</a></h2> + + <p>This is a legacy issue. The CERN webserver required + <code>POST</code> data to have an extra <code>CRLF</code> + following it. Thus many clients send an extra <code>CRLF</code> + that is not included in the <code>Content-Length</code> of the + request. Apache works around this problem by eating any empty + lines which appear before a request.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="broken-keepalive" id="broken-keepalive">Broken KeepAlive</a></h2> + + <p>Various clients have had broken implementations of + <em>keepalive</em> (persistent connections). In particular the + Windows versions of Navigator 2.0 get very confused when the + server times out an idle connection. The workaround is present + in the default config files:</p> + + <div class="example"><p><code> + BrowserMatch Mozilla/2 nokeepalive + </code></p></div> + + <p>Note that this matches some earlier versions of MSIE, which + began the practice of calling themselves <em>Mozilla</em> in + their user-agent strings just like Navigator.</p> + + <p>MSIE 4.0b2, which claims to support HTTP/1.1, does not + properly support keepalive when it is used on 301 or 302 + (redirect) responses. Unfortunately Apache's + <code>nokeepalive</code> code prior to 1.2.2 would not work + with HTTP/1.1 clients. You must apply <a href="http://www.apache.org/dist/httpd/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch"> + this patch</a> to version 1.2.1. Then add this to your + config:</p> + + <div class="example"><p><code> + BrowserMatch "MSIE 4\.0b2;" nokeepalive + </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="force-response-1.0" id="force-response-1.0">Incorrect interpretation of + <code>HTTP/1.1</code> in response</a></h2> + + <p>To quote from section 3.1 of RFC1945:</p> + + <div class="note"> + HTTP uses a "<MAJOR>.<MINOR>" numbering scheme to + indicate versions of the protocol. The protocol versioning + policy is intended to allow the sender to indicate the format + of a message and its capacity for understanding further HTTP + communication, rather than the features obtained via that + communication. + </div> + + <p>Since Apache is an HTTP/1.1 server, it indicates so as part of + its response. Many client authors mistakenly treat this part of + the response as an indication of the protocol that the response + is in, and then refuse to accept the response.</p> + + <p>The first major indication of this problem was with AOL's + proxy servers. When Apache 1.2 went into beta it was the first + wide-spread HTTP/1.1 server. After some discussion, AOL fixed + their proxies. In anticipation of similar problems, the + <code>force-response-1.0</code> environment variable was added + to Apache. When present Apache will indicate "HTTP/1.0" in + response to an HTTP/1.0 client, but will not in any other way + change the response.</p> + + <p>The pre-1.1 Java Development Kit (JDK) that is used in many + clients (including Navigator 3.x and MSIE 3.x) exhibits this + problem. As do some of the early pre-releases of the 1.1 JDK. + We think it is fixed in the 1.1 JDK release. In any event the + workaround:</p> + + <div class="example"><p><code> + BrowserMatch Java/1.0 force-response-1.0<br /> + BrowserMatch JDK/1.0 force-response-1.0 + </code></p></div> + + <p>RealPlayer 4.0 from Progressive Networks also exhibits this + problem. However they have fixed it in version 4.01 of the + player, but version 4.01 uses the same <code>User-Agent</code> + as version 4.0. The workaround is still:</p> + + <div class="example"><p><code> + BrowserMatch "RealPlayer 4.0" force-response-1.0 + </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="msie4.0b2" id="msie4.0b2">Requests use HTTP/1.1 but + responses must be in HTTP/1.0</a></h2> + + <p>MSIE 4.0b2 has this problem. Its Java VM makes requests in + HTTP/1.1 format but the responses must be in HTTP/1.0 format + (in particular, it does not understand <em>chunked</em> + responses). The workaround is to fool Apache into believing the + request came in HTTP/1.0 format.</p> + + <div class="example"><p><code> + BrowserMatch "MSIE 4\.0b2;" downgrade-1.0 + force-response-1.0 + </code></p></div> + + <p>This workaround is available in 1.2.2, and in a <a href="http://www.apache.org/dist/httpd/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch"> + patch</a> against 1.2.1.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="byte-257" id="byte-257">Boundary problems with + header parsing</a></h2> + + <p>All versions of Navigator from 2.0 through 4.0b2 (and + possibly later) have a problem if the trailing CRLF of the + response header starts at offset 256, 257 or 258 of the + response. A BrowserMatch for this would match on nearly every + hit, so the workaround is enabled automatically on all + responses. The workaround implemented detects when this + condition would occur in a response and adds extra padding to + the header to push the trailing CRLF past offset 258 of the + response.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="boundary-string" id="boundary-string">Multipart responses and + Quoted Boundary Strings</a></h2> + + <p>On multipart responses some clients will not accept quotes + (") around the boundary string. The MIME standard recommends + that such quotes be used. But the clients were probably written + based on one of the examples in RFC2068, which does not include + quotes. Apache does not include quotes on its boundary strings + to workaround this problem.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="byterange-requests" id="byterange-requests">Byterange Requests</a></h2> + + <p>A byterange request is used when the client wishes to + retrieve a portion of an object, not necessarily the entire + object. There was a very old draft which included these + byteranges in the URL. Old clients such as Navigator 2.0b1 and + MSIE 3.0 for the MAC exhibit this behaviour, and it will appear + in the servers' access logs as (failed) attempts to retrieve a + URL with a trailing ";xxx-yyy". Apache does not attempt to + implement this at all.</p> + + <p>A subsequent draft of this standard defines a header + <code>Request-Range</code>, and a response type + <code>multipart/x-byteranges</code>. The HTTP/1.1 standard + includes this draft with a few fixes, and it defines the header + <code>Range</code> and type + <code>multipart/byteranges</code>.</p> + + <p>Navigator (versions 2 and 3) sends both <code>Range</code> + and <code>Request-Range</code> headers (with the same value), + but does not accept a <code>multipart/byteranges</code> + response. The response must be + <code>multipart/x-byteranges</code>. As a workaround, if Apache + receives a <code>Request-Range</code> header it considers it + "higher priority" than a <code>Range</code> header and in + response uses <code>multipart/x-byteranges</code>.</p> + + <p>The Adobe Acrobat Reader plugin makes extensive use of + byteranges and prior to version 3.01 supports only the + <code>multipart/x-byterange</code> response. Unfortunately + there is no clue that it is the plugin making the request. If + the plugin is used with Navigator, the above workaround works + fine. But if the plugin is used with MSIE 3 (on Windows) the + workaround won't work because MSIE 3 doesn't give the + <code>Range-Request</code> clue that Navigator does. To + workaround this, Apache special cases "MSIE 3" in the + <code>User-Agent</code> and serves + <code>multipart/x-byteranges</code>. Note that the necessity + for this with MSIE 3 is actually due to the Acrobat plugin, not + due to the browser.</p> + + <p>Netscape Communicator appears to not issue the non-standard + <code>Request-Range</code> header. When an Acrobat plugin prior + to version 3.01 is used with it, it will not properly + understand byteranges. The user must upgrade their Acrobat + reader to 3.01.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="cookie-merge" id="cookie-merge"><code>Set-Cookie</code> header is + unmergeable</a></h2> + + <p>The HTTP specifications say that it is legal to merge + headers with duplicate names into one (separated by commas). + Some browsers that support Cookies don't like merged headers + and prefer that each <code>Set-Cookie</code> header is sent + separately. When parsing the headers returned by a CGI, Apache + will explicitly avoid merging any <code>Set-Cookie</code> + headers.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="gif89-expires" id="gif89-expires"><code>Expires</code> headers + and GIF89A animations</a></h2> + + <p>Navigator versions 2 through 4 will erroneously re-request + GIF89A animations on each loop of the animation if the first + response included an <code>Expires</code> header. This happens + regardless of how far in the future the expiry time is set. + There is no workaround supplied with Apache, however there are + hacks for <a href="http://www.arctic.org/~dgaudet/patches/apache-1.2-gif89-expires-hack.patch"> + 1.2</a> and for <a href="http://www.arctic.org/~dgaudet/patches/apache-1.3-gif89-expires-hack.patch"> + 1.3</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="no-content-length" id="no-content-length"><code>POST</code> without + <code>Content-Length</code></a></h2> + + <p>In certain situations Navigator 3.01 through 3.03 appear to + incorrectly issue a POST without the request body. There is no + known workaround. It has been fixed in Navigator 3.04, + Netscapes provides some <a href="http://help.netscape.com/kb/client/971014-42.html">information</a>. + There's also <a href="http://www.arctic.org/~dgaudet/apache/no-content-length/"> + some information</a> about the actual problem.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="jdk-12-bugs" id="jdk-12-bugs">JDK 1.2 betas lose + parts of responses.</a></h2> + + <p>The http client in the JDK1.2beta2 and beta3 will throw away + the first part of the response body when both the headers and + the first part of the body are sent in the same network packet + AND keep-alive's are being used. If either condition is not met + then it works fine.</p> + + <p>See also Bug-ID's 4124329 and 4125538 at the java developer + connection.</p> + + <p>If you are seeing this bug yourself, you can add the + following BrowserMatch directive to work around it:</p> + + <div class="example"><p><code> + BrowserMatch "Java1\.2beta[23]" nokeepalive + </code></p></div> + + <p>We don't advocate this though since bending over backwards + for beta software is usually not a good idea; ideally it gets + fixed, new betas or a final release comes out, and no one uses + the broken old software anymore. In theory.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="content-type-persistent" id="content-type-persistent"><code>Content-Type</code> + change is not noticed after reload</a></h2> + + <p>Navigator (all versions?) will cache the + <code>content-type</code> for an object "forever". Using reload + or shift-reload will not cause Navigator to notice a + <code>content-type</code> change. The only work-around is for + the user to flush their caches (memory and disk). By way of an + example, some folks may be using an old <code>mime.types</code> + file which does not map <code>.htm</code> to + <code>text/html</code>, in this case Apache will default to + sending <code>text/plain</code>. If the user requests the page + and it is served as <code>text/plain</code>. After the admin + fixes the server, the user will have to flush their caches + before the object will be shown with the correct + <code>text/html</code> type.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="msie-cookie-y2k" id="msie-cookie-y2k">MSIE Cookie + problem with expiry date in the year 2000</a></h2> + + <p>MSIE versions 3.00 and 3.02 (without the Y2K patch) do not + handle cookie expiry dates in the year 2000 properly. Years + after 2000 and before 2000 work fine. This is fixed in IE4.01 + service pack 1, and in the Y2K patch for IE3.02. Users should + avoid using expiry dates in the year 2000.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="lynx-negotiate-trans" id="lynx-negotiate-trans">Lynx incorrectly asking for + transparent content negotiation</a></h2> + + <p>The Lynx browser versions 2.7 and 2.8 send a "negotiate: + trans" header in their requests, which is an indication the + browser supports transparent content negotiation (TCN). However + the browser does not support TCN. As of version 1.3.4, Apache + supports TCN, and this causes problems with these versions of + Lynx. As a workaround future versions of Apache will ignore + this header when sent by the Lynx client.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="ie40-vary" id="ie40-vary">MSIE 4.0 mishandles Vary + response header</a></h2> + + <p>MSIE 4.0 does not handle a Vary header properly. The Vary + header is generated by mod_rewrite in apache 1.3. The result is + an error from MSIE saying it cannot download the requested + file. There are more details in <a href="http://bugs.apache.org/index/full/4118">PR#4118</a>.</p> + + <p>A workaround is to add the following to your server's + configuration files:</p> + + <div class="example"><p><code> + BrowserMatch "MSIE 4\.0" force-no-vary + </code></p></div> + + <p>(This workaround is only available with releases + <strong>after</strong> 1.3.6 of the Apache Web server.)</p> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/known_client_problems.html" title="English"> en </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html new file mode 100644 index 00000000..84956329 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: perf-tuning.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: perf-tuning.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: perf-tuning.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.en new file mode 100644 index 00000000..2a6bc9d1 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.en @@ -0,0 +1,1058 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache Performance Tuning - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Apache Performance Tuning</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/perf-tuning.html" title="English"> en </a> | +<a href="../ko/misc/perf-tuning.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/perf-tuning.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> +</div> + + + <p>Apache 2.x is a general-purpose webserver, designed to + provide a balance of flexibility, portability, and performance. + Although it has not been designed specifically to set benchmark + records, Apache 2.x is capable of high performance in many + real-world situations.</p> + + <p>Compared to Apache 1.3, release 2.x contains many additional + optimizations to increase throughput and scalability. Most of + these improvements are enabled by default. However, there are + compile-time and run-time configuration choices that can + significantly affect performance. This document describes the + options that a server administrator can configure to tune the + performance of an Apache 2.x installation. Some of these + configuration options enable the httpd to better take advantage + of the capabilities of the hardware and OS, while others allow + the administrator to trade functionality for speed.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#hardware">Hardware and Operating System Issues</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#runtime">Run-Time Configuration Issues</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compiletime">Compile-Time Configuration Issues</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#trace">Appendix: Detailed Analysis of a Trace</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="hardware" id="hardware">Hardware and Operating System Issues</a></h2> + + + + <p>The single biggest hardware issue affecting webserver + performance is RAM. A webserver should never ever have to swap, + as swapping increases the latency of each request beyond a point + that users consider "fast enough". This causes users to hit + stop and reload, further increasing the load. You can, and + should, control the <code class="directive"><a href="../mod/mpm_common.html#maxclients">MaxClients</a></code> setting so that your server + does not spawn so many children it starts swapping. This procedure + for doing this is simple: determine the size of your average Apache + process, by looking at your process list via a tool such as + <code>top</code>, and divide this into your total available memory, + leaving some room for other processes.</p> + + <p>Beyond that the rest is mundane: get a fast enough CPU, a + fast enough network card, and fast enough disks, where "fast + enough" is something that needs to be determined by + experimentation.</p> + + <p>Operating system choice is largely a matter of local + concerns. But some guidelines that have proven generally + useful are:</p> + + <ul> + <li> + <p>Run the latest stable release and patchlevel of the + operating system that you choose. Many OS suppliers have + introduced significant performance improvements to their + TCP stacks and thread libraries in recent years.</p> + </li> + + <li> + <p>If your OS supports a <code>sendfile(2)</code> system + call, make sure you install the release and/or patches + needed to enable it. (With Linux, for example, this means + using Linux 2.4 or later. For early releases of Solaris 8, + you may need to apply a patch.) On systems where it is + available, <code>sendfile</code> enables Apache 2 to deliver + static content faster and with lower CPU utilization.</p> + </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="runtime" id="runtime">Run-Time Configuration Issues</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/mod_dir.html">mod_dir</a></code></li><li><code class="module"><a href="../mod/mpm_common.html">mpm_common</a></code></li><li><code class="module"><a href="../mod/mod_status.html">mod_status</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code></li><li><code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code></li><li><code class="directive"><a href="../mod/core.html#enablemmap">EnableMMAP</a></code></li><li><code class="directive"><a href="../mod/core.html#enablesendfile">EnableSendfile</a></code></li><li><code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code></li><li><code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code></li><li><code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code></li></ul></td></tr></table> + + <h3><a name="dns" id="dns">HostnameLookups and other DNS considerations</a></h3> + + + + <p>Prior to Apache 1.3, <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> defaulted to <code>On</code>. + This adds latency to every request because it requires a + DNS lookup to complete before the request is finished. In + Apache 1.3 this setting defaults to <code>Off</code>. If you need + to have addresses in your log files resolved to hostnames, use the + <code class="program"><a href="../programs/logresolve.html">logresolve</a></code> + program that comes with Apache, or one of the numerous log + reporting packages which are available.</p> + + <p>It is recommended that you do this sort of postprocessing of + your log files on some machine other than the production web + server machine, in order that this activity not adversely affect + server performance.</p> + + <p>If you use any <code><code class="directive"><a href="../mod/mod_access.html#allow">Allow</a></code> + from domain</code> or <code><code class="directive"><a href="../mod/mod_access.html#deny">Deny</a></code> from domain</code> + directives (i.e., using a hostname, or a domain name, rather than + an IP address) then you will pay for + two DNS lookups (a reverse, followed by a forward lookup + to make sure that the reverse is not being spoofed). For best + performance, therefore, use IP addresses, rather than names, when + using these directives, if possible.</p> + + <p>Note that it's possible to scope the directives, such as + within a <code><Location /server-status></code> section. + In this case the DNS lookups are only performed on requests + matching the criteria. Here's an example which disables lookups + except for <code>.html</code> and <code>.cgi</code> files:</p> + + <div class="example"><p><code> + HostnameLookups off<br /> + <Files ~ "\.(html|cgi)$"><br /> + <span class="indent"> + HostnameLookups on<br /> + </span> + </Files> + </code></p></div> + + <p>But even still, if you just need DNS names in some CGIs you + could consider doing the <code>gethostbyname</code> call in the + specific CGIs that need it.</p> + + + + <h3><a name="symlinks" id="symlinks">FollowSymLinks and SymLinksIfOwnerMatch</a></h3> + + + + <p>Wherever in your URL-space you do not have an <code>Options + FollowSymLinks</code>, or you do have an <code>Options + SymLinksIfOwnerMatch</code> Apache will have to issue extra + system calls to check up on symlinks. One extra call per + filename component. For example, if you had:</p> + + <div class="example"><p><code> + DocumentRoot /www/htdocs<br /> + <Directory /><br /> + <span class="indent"> + Options SymLinksIfOwnerMatch<br /> + </span> + </Directory> + </code></p></div> + + <p>and a request is made for the URI <code>/index.html</code>. + Then Apache will perform <code>lstat(2)</code> on + <code>/www</code>, <code>/www/htdocs</code>, and + <code>/www/htdocs/index.html</code>. The results of these + <code>lstats</code> are never cached, so they will occur on + every single request. If you really desire the symlinks + security checking you can do something like this:</p> + + <div class="example"><p><code> + DocumentRoot /www/htdocs<br /> + <Directory /><br /> + <span class="indent"> + Options FollowSymLinks<br /> + </span> + </Directory><br /> + <br /> + <Directory /www/htdocs><br /> + <span class="indent"> + Options -FollowSymLinks +SymLinksIfOwnerMatch<br /> + </span> + </Directory> + </code></p></div> + + <p>This at least avoids the extra checks for the + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> path. + Note that you'll need to add similar sections if you + have any <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code> or + <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> paths + outside of your document root. For highest performance, + and no symlink protection, set <code>FollowSymLinks</code> + everywhere, and never set <code>SymLinksIfOwnerMatch</code>.</p> + + + + <h3><a name="htacess" id="htacess">AllowOverride</a></h3> + + + + <p>Wherever in your URL-space you allow overrides (typically + <code>.htaccess</code> files) Apache will attempt to open + <code>.htaccess</code> for each filename component. For + example,</p> + + <div class="example"><p><code> + DocumentRoot /www/htdocs<br /> + <Directory /><br /> + <span class="indent"> + AllowOverride all<br /> + </span> + </Directory> + </code></p></div> + + <p>and a request is made for the URI <code>/index.html</code>. + Then Apache will attempt to open <code>/.htaccess</code>, + <code>/www/.htaccess</code>, and + <code>/www/htdocs/.htaccess</code>. The solutions are similar + to the previous case of <code>Options FollowSymLinks</code>. + For highest performance use <code>AllowOverride None</code> + everywhere in your filesystem.</p> + + + + <h3><a name="negotiation" id="negotiation">Negotiation</a></h3> + + + + <p>If at all possible, avoid content-negotiation if you're + really interested in every last ounce of performance. In + practice the benefits of negotiation outweigh the performance + penalties. There's one case where you can speed up the server. + Instead of using a wildcard such as:</p> + + <div class="example"><p><code> + DirectoryIndex index + </code></p></div> + + <p>Use a complete list of options:</p> + + <div class="example"><p><code> + DirectoryIndex index.cgi index.pl index.shtml index.html + </code></p></div> + + <p>where you list the most common choice first.</p> + + <p>Also note that explicitly creating a <code>type-map</code> + file provides better performance than using + <code>MultiViews</code>, as the necessary information can be + determined by reading this single file, rather than having to + scan the directory for files.</p> + + <p>If your site needs content negotiation consider using + <code>type-map</code> files, rather than the <code>Options + MultiViews</code> directive to accomplish the negotiation. See the + <a href="../content-negotiation.html">Content Negotiation</a> + documentation for a full discussion of the methods of negotiation, + and instructions for creating <code>type-map</code> files.</p> + + + + <h3>Memory-mapping</h3> + + + + <p>In situations where Apache 2.x needs to look at the contents + of a file being delivered--for example, when doing server-side-include + processing--it normally memory-maps the file if the OS supports + some form of <code>mmap(2)</code>.</p> + + <p>On some platforms, this memory-mapping improves performance. + However, there are cases where memory-mapping can hurt the performance + or even the stability of the httpd:</p> + + <ul> + <li> + <p>On some operating systems, <code>mmap</code> does not scale + as well as <code>read(2)</code> when the number of CPUs increases. + On multiprocessor Solaris servers, for example, Apache 2.x sometimes + delivers server-parsed files faster when <code>mmap</code> is disabled.</p> + </li> + + <li> + <p>If you memory-map a file located on an NFS-mounted filesystem + and a process on another NFS client machine deletes or truncates + the file, your process may get a bus error the next time it tries + to access the mapped file content.</p> + </li> + </ul> + + <p>For installations where either of these factors applies, you + should use <code>EnableMMAP off</code> to disable the memory-mapping + of delivered files. (Note: This directive can be overridden on + a per-directory basis.)</p> + + + + <h3>Sendfile</h3> + + + + <p>In situations where Apache 2.x can ignore the contents of the file + to be delivered -- for example, when serving static file content -- + it normally uses the kernel sendfile support the file if the OS + supports the <code>sendfile(2)</code> operation.</p> + + <p>On most platforms, using sendfile improves performance by eliminating + separate read and send mechanics. However, there are cases where using + sendfile can harm the stability of the httpd:</p> + + <ul> + <li> + <p>Some platforms may have broken sendfile support that the build + system did not detect, especially if the binaries were built on + another box and moved to such a machine with broken sendfile support.</p> + </li> + <li> + <p>With an NFS-mounted files, the kernel may be unable + to reliably serve the network file through it's own cache.</p> + </li> + </ul> + + <p>For installations where either of these factors applies, you + should use <code>EnableSendfile off</code> to disable sendfile + delivery of file contents. (Note: This directive can be overridden + on a per-directory basis.)</p> + + + + <h3><a name="process" id="process">Process Creation</a></h3> + + + + <p>Prior to Apache 1.3 the <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code>, <code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code>, and <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> settings all had drastic effects on + benchmark results. In particular, Apache required a "ramp-up" + period in order to reach a number of children sufficient to serve + the load being applied. After the initial spawning of + <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> children, + only one child per second would be created to satisfy the + <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code> + setting. So a server being accessed by 100 simultaneous + clients, using the default <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> of <code>5</code> would take on + the order 95 seconds to spawn enough children to handle + the load. This works fine in practice on real-life servers, + because they aren't restarted frequently. But does really + poorly on benchmarks which might only run for ten minutes.</p> + + <p>The one-per-second rule was implemented in an effort to + avoid swamping the machine with the startup of new children. If + the machine is busy spawning children it can't service + requests. But it has such a drastic effect on the perceived + performance of Apache that it had to be replaced. As of Apache + 1.3, the code will relax the one-per-second rule. It will spawn + one, wait a second, then spawn two, wait a second, then spawn + four, and it will continue exponentially until it is spawning + 32 children per second. It will stop whenever it satisfies the + <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code> + setting.</p> + + <p>This appears to be responsive enough that it's almost + unnecessary to twiddle the <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code>, <code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code> and <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> knobs. When more than 4 children are + spawned per second, a message will be emitted to the + <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code>. If you + see a lot of these errors then consider tuning these settings. + Use the <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> output as a guide.</p> + + <p>Related to process creation is process death induced by the + <code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> + setting. By default this is <code>0</code>, + which means that there is no limit to the number of requests + handled per child. If your configuration currently has this set + to some very low number, such as <code>30</code>, you may want to bump this + up significantly. If you are running SunOS or an old version of + Solaris, limit this to <code>10000</code> or so because of memory leaks.</p> + + <p>When keep-alives are in use, children will be kept busy + doing nothing waiting for more requests on the already open + connection. The default <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code> of <code>15</code> + seconds attempts to minimize this effect. The tradeoff here is + between network bandwidth and server resources. In no event + should you raise this above about <code>60</code> seconds, as <a href="http://www.research.digital.com/wrl/techreports/abstracts/95.4.html"> + most of the benefits are lost</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="compiletime" id="compiletime">Compile-Time Configuration Issues</a></h2> + + + + <h3>Choosing an MPM</h3> + + + + <p>Apache 2.x supports pluggable concurrency models, called + <a href="../mpm.html">Multi-Processing Modules</a> (MPMs). + When building Apache, you must choose an MPM to use. There + are platform-specific MPMs for some platforms: + <code class="module"><a href="../mod/beos.html">beos</a></code>, <code class="module"><a href="../mod/mpm_netware.html">mpm_netware</a></code>, + <code class="module"><a href="../mod/mpmt_os2.html">mpmt_os2</a></code>, and <code class="module"><a href="../mod/mpm_winnt.html">mpm_winnt</a></code>. For + general Unix-type systems, there are several MPMs from which + to choose. The choice of MPM can affect the speed and scalability + of the httpd:</p> + + <ul> + + <li>The <code class="module"><a href="../mod/worker.html">worker</a></code> MPM uses multiple child + processes with many threads each. Each thread handles + one connection at a time. Worker generally is a good + choice for high-traffic servers because it has a smaller + memory footprint than the prefork MPM.</li> + + <li>The <code class="module"><a href="../mod/prefork.html">prefork</a></code> MPM uses multiple child + processes with one thread each. Each process handles + one connection at a time. On many systems, prefork is + comparable in speed to worker, but it uses more memory. + Prefork's threadless design has advantages over worker + in some situations: it can be used with non-thread-safe + third-party modules, and it is easier to debug on platforms + with poor thread debugging support.</li> + + </ul> + + <p>For more information on these and other MPMs, please + see the MPM <a href="../mpm.html">documentation</a>.</p> + + + + <h3><a name="modules" id="modules">Modules</a></h3> + + + + <p>Since memory usage is such an important consideration in + performance, you should attempt to eliminate modules that you are + not actually using. If you have built the modules as <a href="../dso.html">DSOs</a>, eliminating modules is a simple + matter of commenting out the associated <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> directive for that module. + This allows you to experiment with removing modules, and seeing + if your site still functions in their absense.</p> + + <p>If, on the other hand, you have modules statically linked + into your Apache binary, you will need to recompile Apache in + order to remove unwanted modules.</p> + + <p>An associated question that arises here is, of course, what + modules you need, and which ones you don't. The answer here + will, of course, vary from one web site to another. However, the + <em>minimal</em> list of modules which you can get by with tends + to include <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code>, <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code>, + and <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code>. <code>mod_log_config</code> is, + of course, optional, as you can run a web site without log + files. This is, however, not recommended.</p> + + + + <h3>Atomic Operations</h3> + + + + <p>Some modules, such as <code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code> and + recent development builds of the worker MPM, use APR's + atomic API. This API provides atomic operations that can + be used for lightweight thread synchronization.</p> + + <p>By default, APR implements these operations using the + most efficient mechanism available on each target + OS/CPU platform. Many modern CPUs, for example, have + an instruction that does an atomic compare-and-swap (CAS) + operation in hardware. On some platforms, however, APR + defaults to a slower, mutex-based implementation of the + atomic API in order to ensure compatibility with older + CPU models that lack such instructions. If you are + building Apache for one of these platforms, and you plan + to run only on newer CPUs, you can select a faster atomic + implementation at build time by configuring Apache with + the <code>--enable-nonportable-atomics</code> option:</p> + + <div class="example"><p><code> + ./buildconf<br /> + ./configure --with-mpm=worker --enable-nonportable-atomics=yes + </code></p></div> + + <p>The <code>--enable-nonportable-atomics</code> option is + relevant for the following platforms:</p> + + <ul> + + <li>Solaris on SPARC<br /> + By default, APR uses mutex-based atomics on Solaris/SPARC. + If you configure with <code>--enable-nonportable-atomics</code>, + however, APR generates code that uses a SPARC v8plus opcode for + fast hardware compare-and-swap. If you configure Apache with + this option, the atomic operations will be more efficient + (allowing for lower CPU utilization and higher concurrency), + but the resulting executable will run only on UltraSPARC + chips. + </li> + + <li>Linux on x86<br /> + By default, APR uses mutex-based atomics on Linux. If you + configure with <code>--enable-nonportable-atomics</code>, + however, APR generates code that uses a 486 opcode for fast + hardware compare-and-swap. This will result in more efficient + atomic operations, but the resulting executable will run only + on 486 and later chips (and not on 386). + </li> + + </ul> + + + + <h3>mod_status and ExtendedStatus On</h3> + + + + <p>If you include <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> and you also set + <code>ExtendedStatus On</code> when building and running + Apache, then on every request Apache will perform two calls to + <code>gettimeofday(2)</code> (or <code>times(2)</code> + depending on your operating system), and (pre-1.3) several + extra calls to <code>time(2)</code>. This is all done so that + the status report contains timing indications. For highest + performance, set <code>ExtendedStatus off</code> (which is the + default).</p> + + + + <h3>accept Serialization - multiple sockets</h3> + + + + <div class="warning"><h3>Warning:</h3> + <p>This section has not been fully updated + to take into account changes made in the 2.x version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <p>This discusses a shortcoming in the Unix socket API. Suppose + your web server uses multiple <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> statements to listen on either multiple + ports or multiple addresses. In order to test each socket + to see if a connection is ready Apache uses + <code>select(2)</code>. <code>select(2)</code> indicates that a + socket has <em>zero</em> or <em>at least one</em> connection + waiting on it. Apache's model includes multiple children, and + all the idle ones test for new connections at the same time. A + naive implementation looks something like this (these examples + do not match the code, they're contrived for pedagogical + purposes):</p> + + <div class="example"><p><code> + for (;;) {<br /> + <span class="indent"> + for (;;) {<br /> + <span class="indent"> + fd_set accept_fds;<br /> + <br /> + FD_ZERO (&accept_fds);<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + FD_SET (i, &accept_fds);<br /> + </span> + }<br /> + rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);<br /> + if (rc < 1) continue;<br /> + new_connection = -1;<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + if (FD_ISSET (i, &accept_fds)) {<br /> + <span class="indent"> + new_connection = accept (i, NULL, NULL);<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + </span> + }<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + process the new_connection;<br /> + </span> + } + </code></p></div> + + <p>But this naive implementation has a serious starvation problem. + Recall that multiple children execute this loop at the same + time, and so multiple children will block at + <code>select</code> when they are in between requests. All + those blocked children will awaken and return from + <code>select</code> when a single request appears on any socket + (the number of children which awaken varies depending on the + operating system and timing issues). They will all then fall + down into the loop and try to <code>accept</code> the + connection. But only one will succeed (assuming there's still + only one connection ready), the rest will be <em>blocked</em> + in <code>accept</code>. This effectively locks those children + into serving requests from that one socket and no other + sockets, and they'll be stuck there until enough new requests + appear on that socket to wake them all up. This starvation + problem was first documented in <a href="http://bugs.apache.org/index/full/467">PR#467</a>. There + are at least two solutions.</p> + + <p>One solution is to make the sockets non-blocking. In this + case the <code>accept</code> won't block the children, and they + will be allowed to continue immediately. But this wastes CPU + time. Suppose you have ten idle children in + <code>select</code>, and one connection arrives. Then nine of + those children will wake up, try to <code>accept</code> the + connection, fail, and loop back into <code>select</code>, + accomplishing nothing. Meanwhile none of those children are + servicing requests that occurred on other sockets until they + get back up to the <code>select</code> again. Overall this + solution does not seem very fruitful unless you have as many + idle CPUs (in a multiprocessor box) as you have idle children, + not a very likely situation.</p> + + <p>Another solution, the one used by Apache, is to serialize + entry into the inner loop. The loop looks like this + (differences highlighted):</p> + + <div class="example"><p><code> + for (;;) {<br /> + <span class="indent"> + <strong>accept_mutex_on ();</strong><br /> + for (;;) {<br /> + <span class="indent"> + fd_set accept_fds;<br /> + <br /> + FD_ZERO (&accept_fds);<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + FD_SET (i, &accept_fds);<br /> + </span> + }<br /> + rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);<br /> + if (rc < 1) continue;<br /> + new_connection = -1;<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + if (FD_ISSET (i, &accept_fds)) {<br /> + <span class="indent"> + new_connection = accept (i, NULL, NULL);<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + </span> + }<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + <strong>accept_mutex_off ();</strong><br /> + process the new_connection;<br /> + </span> + } + </code></p></div> + + <p><a id="serialize" name="serialize">The functions</a> + <code>accept_mutex_on</code> and <code>accept_mutex_off</code> + implement a mutual exclusion semaphore. Only one child can have + the mutex at any time. There are several choices for + implementing these mutexes. The choice is defined in + <code>src/conf.h</code> (pre-1.3) or + <code>src/include/ap_config.h</code> (1.3 or later). Some + architectures do not have any locking choice made, on these + architectures it is unsafe to use multiple + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + directives.</p> + + <p>The directive <code class="directive"><a href="../mod/mpm_common.html#acceptmutex">AcceptMutex</a></code> can be used to + change the selected mutex implementation at run-time.</p> + + <dl> + <dt><code>AcceptMutex flock</code></dt> + + <dd> + <p>This method uses the <code>flock(2)</code> system call to + lock a lock file (located by the <code class="directive"><a href="../mod/mpm_common.html#lockfile">LockFile</a></code> directive).</p> + </dd> + + <dt><code>AcceptMutex fcntl</code></dt> + + <dd> + <p>This method uses the <code>fcntl(2)</code> system call to + lock a lock file (located by the <code class="directive"><a href="../mod/mpm_common.html#lockfile">LockFile</a></code> directive).</p> + </dd> + + <dt><code>AcceptMutex sysvsem</code></dt> + + <dd> + <p>(1.3 or later) This method uses SysV-style semaphores to + implement the mutex. Unfortunately SysV-style semaphores have + some bad side-effects. One is that it's possible Apache will + die without cleaning up the semaphore (see the + <code>ipcs(8)</code> man page). The other is that the + semaphore API allows for a denial of service attack by any + CGIs running under the same uid as the webserver + (<em>i.e.</em>, all CGIs, unless you use something like + <code class="program"><a href="../programs/suexec.html">suexec</a></code> or <code>cgiwrapper</code>). For these + reasons this method is not used on any architecture except + IRIX (where the previous two are prohibitively expensive + on most IRIX boxes).</p> + </dd> + + <dt><code>AcceptMutex pthread</code></dt> + + <dd> + <p>(1.3 or later) This method uses POSIX mutexes and should + work on any architecture implementing the full POSIX threads + specification, however appears to only work on Solaris (2.5 + or later), and even then only in certain configurations. If + you experiment with this you should watch out for your server + hanging and not responding. Static content only servers may + work just fine.</p> + </dd> + + <dt><code>AcceptMutex posixsem</code></dt> + + <dd> + <p>(2.0 or later) This method uses POSIX semaphores. The + semaphore ownership is not recovered if a thread in the process + holding the mutex segfaults, resulting in a hang of the web + server.</p> + </dd> + + </dl> + + <p>If your system has another method of serialization which + isn't in the above list then it may be worthwhile adding code + for it to APR.</p> + + <p>Another solution that has been considered but never + implemented is to partially serialize the loop -- that is, let + in a certain number of processes. This would only be of + interest on multiprocessor boxes where it's possible multiple + children could run simultaneously, and the serialization + actually doesn't take advantage of the full bandwidth. This is + a possible area of future investigation, but priority remains + low because highly parallel web servers are not the norm.</p> + + <p>Ideally you should run servers without multiple + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + statements if you want the highest performance. + But read on.</p> + + + + <h3>accept Serialization - single socket</h3> + + + + <p>The above is fine and dandy for multiple socket servers, but + what about single socket servers? In theory they shouldn't + experience any of these same problems because all children can + just block in <code>accept(2)</code> until a connection + arrives, and no starvation results. In practice this hides + almost the same "spinning" behaviour discussed above in the + non-blocking solution. The way that most TCP stacks are + implemented, the kernel actually wakes up all processes blocked + in <code>accept</code> when a single connection arrives. One of + those processes gets the connection and returns to user-space, + the rest spin in the kernel and go back to sleep when they + discover there's no connection for them. This spinning is + hidden from the user-land code, but it's there nonetheless. + This can result in the same load-spiking wasteful behaviour + that a non-blocking solution to the multiple sockets case + can.</p> + + <p>For this reason we have found that many architectures behave + more "nicely" if we serialize even the single socket case. So + this is actually the default in almost all cases. Crude + experiments under Linux (2.0.30 on a dual Pentium pro 166 + w/128Mb RAM) have shown that the serialization of the single + socket case causes less than a 3% decrease in requests per + second over unserialized single-socket. But unserialized + single-socket showed an extra 100ms latency on each request. + This latency is probably a wash on long haul lines, and only an + issue on LANs. If you want to override the single socket + serialization you can define + <code>SINGLE_LISTEN_UNSERIALIZED_ACCEPT</code> and then + single-socket servers will not serialize at all.</p> + + + + <h3>Lingering Close</h3> + + + + <p>As discussed in <a href="http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-connection-00.txt"> + draft-ietf-http-connection-00.txt</a> section 8, in order for + an HTTP server to <strong>reliably</strong> implement the + protocol it needs to shutdown each direction of the + communication independently (recall that a TCP connection is + bi-directional, each half is independent of the other). This + fact is often overlooked by other servers, but is correctly + implemented in Apache as of 1.2.</p> + + <p>When this feature was added to Apache it caused a flurry of + problems on various versions of Unix because of a + shortsightedness. The TCP specification does not state that the + <code>FIN_WAIT_2</code> state has a timeout, but it doesn't prohibit it. + On systems without the timeout, Apache 1.2 induces many sockets + stuck forever in the <code>FIN_WAIT_2</code> state. In many cases this + can be avoided by simply upgrading to the latest TCP/IP patches + supplied by the vendor. In cases where the vendor has never + released patches (<em>i.e.</em>, SunOS4 -- although folks with + a source license can patch it themselves) we have decided to + disable this feature.</p> + + <p>There are two ways of accomplishing this. One is the socket + option <code>SO_LINGER</code>. But as fate would have it, this + has never been implemented properly in most TCP/IP stacks. Even + on those stacks with a proper implementation (<em>i.e.</em>, + Linux 2.0.31) this method proves to be more expensive (cputime) + than the next solution.</p> + + <p>For the most part, Apache implements this in a function + called <code>lingering_close</code> (in + <code>http_main.c</code>). The function looks roughly like + this:</p> + + <div class="example"><p><code> + void lingering_close (int s)<br /> + {<br /> + <span class="indent"> + char junk_buffer[2048];<br /> + <br /> + /* shutdown the sending side */<br /> + shutdown (s, 1);<br /> + <br /> + signal (SIGALRM, lingering_death);<br /> + alarm (30);<br /> + <br /> + for (;;) {<br /> + <span class="indent"> + select (s for reading, 2 second timeout);<br /> + if (error) break;<br /> + if (s is ready for reading) {<br /> + <span class="indent"> + if (read (s, junk_buffer, sizeof (junk_buffer)) <= 0) {<br /> + <span class="indent"> + break;<br /> + </span> + }<br /> + /* just toss away whatever is here */<br /> + </span> + }<br /> + </span> + }<br /> + <br /> + close (s);<br /> + </span> + } + </code></p></div> + + <p>This naturally adds some expense at the end of a connection, + but it is required for a reliable implementation. As HTTP/1.1 + becomes more prevalent, and all connections are persistent, + this expense will be amortized over more requests. If you want + to play with fire and disable this feature you can define + <code>NO_LINGCLOSE</code>, but this is not recommended at all. + In particular, as HTTP/1.1 pipelined persistent connections + come into use <code>lingering_close</code> is an absolute + necessity (and <a href="http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html"> + pipelined connections are faster</a>, so you want to support + them).</p> + + + + <h3>Scoreboard File</h3> + + + + <p>Apache's parent and children communicate with each other + through something called the scoreboard. Ideally this should be + implemented in shared memory. For those operating systems that + we either have access to, or have been given detailed ports + for, it typically is implemented using shared memory. The rest + default to using an on-disk file. The on-disk file is not only + slow, but it is unreliable (and less featured). Peruse the + <code>src/main/conf.h</code> file for your architecture and + look for either <code>USE_MMAP_SCOREBOARD</code> or + <code>USE_SHMGET_SCOREBOARD</code>. Defining one of those two + (as well as their companions <code>HAVE_MMAP</code> and + <code>HAVE_SHMGET</code> respectively) enables the supplied + shared memory code. If your system has another type of shared + memory, edit the file <code>src/main/http_main.c</code> and add + the hooks necessary to use it in Apache. (Send us back a patch + too please.)</p> + + <div class="note">Historical note: The Linux port of Apache didn't start to + use shared memory until version 1.2 of Apache. This oversight + resulted in really poor and unreliable behaviour of earlier + versions of Apache on Linux.</div> + + + + <h3>DYNAMIC_MODULE_LIMIT</h3> + + + + <p>If you have no intention of using dynamically loaded modules + (you probably don't if you're reading this and tuning your + server for every last ounce of performance) then you should add + <code>-DDYNAMIC_MODULE_LIMIT=0</code> when building your + server. This will save RAM that's allocated only for supporting + dynamically loaded modules.</p> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="trace" id="trace">Appendix: Detailed Analysis of a Trace</a></h2> + + + + <p>Here is a system call trace of Apache 2.0.38 with the worker MPM + on Solaris 8. This trace was collected using:</p> + + <div class="example"><p><code> + truss -l -p <var>httpd_child_pid</var>. + </code></p></div> + + <p>The <code>-l</code> option tells truss to log the ID of the + LWP (lightweight process--Solaris's form of kernel-level thread) + that invokes each system call.</p> + + <p>Other systems may have different system call tracing utilities + such as <code>strace</code>, <code>ktrace</code>, or <code>par</code>. + They all produce similar output.</p> + + <p>In this trace, a client has requested a 10KB static file + from the httpd. Traces of non-static requests or requests + with content negotiation look wildly different (and quite ugly + in some cases).</p> + + <div class="example"><pre>/67: accept(3, 0x00200BEC, 0x00200C0C, 1) (sleeping...) +/67: accept(3, 0x00200BEC, 0x00200C0C, 1) = 9</pre></div> + + <p>In this trace, the listener thread is running within LWP #67.</p> + + <div class="note">Note the lack of <code>accept(2)</code> serialization. On this + particular platform, the worker MPM uses an unserialized accept by + default unless it is listening on multiple ports.</div> + + <div class="example"><pre>/65: lwp_park(0x00000000, 0) = 0 +/67: lwp_unpark(65, 1) = 0</pre></div> + + <p>Upon accepting the connection, the listener thread wakes up + a worker thread to do the request processing. In this trace, + the worker thread that handles the request is mapped to LWP #65.</p> + + <div class="example"><pre>/65: getsockname(9, 0x00200BA4, 0x00200BC4, 1) = 0</pre></div> + + <p>In order to implement virtual hosts, Apache needs to know + the local socket address used to accept the connection. It + is possible to eliminate this call in many situations (such + as when there are no virtual hosts, or when + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directives + are used which do not have wildcard addresses). But + no effort has yet been made to do these optimizations. </p> + + <div class="example"><pre>/65: brk(0x002170E8) = 0 +/65: brk(0x002190E8) = 0</pre></div> + + <p>The <code>brk(2)</code> calls allocate memory from the heap. + It is rare to see these in a system call trace, because the httpd + uses custom memory allocators (<code>apr_pool</code> and + <code>apr_bucket_alloc</code>) for most request processing. + In this trace, the httpd has just been started, so it must + call <code>malloc(3)</code> to get the blocks of raw memory + with which to create the custom memory allocators.</p> + + <div class="example"><pre>/65: fcntl(9, F_GETFL, 0x00000000) = 2 +/65: fstat64(9, 0xFAF7B818) = 0 +/65: getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B910, 2190656) = 0 +/65: fstat64(9, 0xFAF7B818) = 0 +/65: getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B914, 2190656) = 0 +/65: setsockopt(9, 65535, 8192, 0xFAF7B918, 4, 2190656) = 0 +/65: fcntl(9, F_SETFL, 0x00000082) = 0</pre></div> + + <p>Next, the worker thread puts the connection to the client (file + descriptor 9) in non-blocking mode. The <code>setsockopt(2)</code> + and <code>getsockopt(2)</code> calls are a side-effect of how + Solaris's libc handles <code>fcntl(2)</code> on sockets.</p> + + <div class="example"><pre>/65: read(9, " G E T / 1 0 k . h t m".., 8000) = 97</pre></div> + + <p>The worker thread reads the request from the client.</p> + + <div class="example"><pre>/65: stat("/var/httpd/apache/httpd-8999/htdocs/10k.html", 0xFAF7B978) = 0 +/65: open("/var/httpd/apache/httpd-8999/htdocs/10k.html", O_RDONLY) = 10</pre></div> + + <p>This httpd has been configured with <code>Options FollowSymLinks</code> + and <code>AllowOverride None</code>. Thus it doesn't need to + <code>lstat(2)</code> each directory in the path leading up to the + requested file, nor check for <code>.htaccess</code> files. + It simply calls <code>stat(2)</code> to verify that the file: + 1) exists, and 2) is a regular file, not a directory.</p> + + <div class="example"><pre>/65: sendfilev(0, 9, 0x00200F90, 2, 0xFAF7B53C) = 10269</pre></div> + + <p>In this example, the httpd is able to send the HTTP response + header and the requested file with a single <code>sendfilev(2)</code> + system call. Sendfile semantics vary among operating systems. On some other + systems, it is necessary to do a <code>write(2)</code> or + <code>writev(2)</code> call to send the headers before calling + <code>sendfile(2)</code>.</p> + + <div class="example"><pre>/65: write(4, " 1 2 7 . 0 . 0 . 1 - ".., 78) = 78</pre></div> + + <p>This <code>write(2)</code> call records the request in the + access log. Note that one thing missing from this trace is a + <code>time(2)</code> call. Unlike Apache 1.3, Apache 2.x uses + <code>gettimeofday(3)</code> to look up the time. On some operating + systems, like Linux or Solaris, <code>gettimeofday</code> has an + optimized implementation that doesn't require as much overhead + as a typical system call.</p> + + <div class="example"><pre>/65: shutdown(9, 1, 1) = 0 +/65: poll(0xFAF7B980, 1, 2000) = 1 +/65: read(9, 0xFAF7BC20, 512) = 0 +/65: close(9) = 0</pre></div> + + <p>The worker thread does a lingering close of the connection.</p> + + <div class="example"><pre>/65: close(10) = 0 +/65: lwp_park(0x00000000, 0) (sleeping...)</pre></div> + + <p>Finally the worker thread closes the file that it has just delivered + and blocks until the listener assigns it another connection.</p> + + <div class="example"><pre>/67: accept(3, 0x001FEB74, 0x001FEB94, 1) (sleeping...)</pre></div> + + <p>Meanwhile, the listener thread is able to accept another connection + as soon as it has dispatched this connection to a worker thread (subject + to some flow-control logic in the worker MPM that throttles the listener + if all the available workers are busy). Though it isn't apparent from + this trace, the next <code>accept(2)</code> can (and usually does, under + high load conditions) occur in parallel with the worker thread's handling + of the just-accepted connection.</p> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/perf-tuning.html" title="English"> en </a> | +<a href="../ko/misc/perf-tuning.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/perf-tuning.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.ko.euc-kr new file mode 100644 index 00000000..b5443b1e --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.ko.euc-kr @@ -0,0 +1,978 @@ +<?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><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>아파치 성능향상 - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>아파치 성능향상</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/misc/perf-tuning.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/perf-tuning.html" title="Korean"> ko </a> | +<a href="../tr/misc/perf-tuning.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate">이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.</div> + + + <p>아파치 2.0은 기능과 포팅가능성과 성능의 균형이 맞도록 + 설계한 범용 웹서버이다. 벤치마크 기록을 세우기위해 설계하지 + 않았지만 아파치 2.0은 실제 많은 경우 높은 성능을 낸다.</p> + + <p>아파치 1.3과 비교해서 2.0 버전은 처리량과 확장성(scalability)을 + 높이기위해 많은 최적화를 했다. 기본값으로 대부분 최적화한 + 값을 사용한다. 그러나 컴파일시 혹은 실행시 설정이 성능에 + 큰 영향을 줄 수 있다. 이 문서는 아파치 2.0의 성능을 향상하기위해 + 서버 관리자가 설정할 수 있는 옵션을 설명한다. 어떤 설정 + 옵션은 웹서버가 하드웨어와 운영체제의 기능을 더 잘 활용하도록 + 하는 반면, 어떤 옵션은 속도를 위해 기능을 희생한다.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#hardware">하드웨어와 운영체제에 대해서</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#runtime">실행시 설정에 대해서</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compiletime">컴파일시 설정에 대해서</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#trace">부록: 시스템호출 기록을 자세히 분석하기</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="hardware" id="hardware">하드웨어와 운영체제에 대해서</a></h2> + + + + <p>웹서버 성능에 가장 큰 영향을 주는 것은 메모리다. 스왑은 + 요청당 지연시간을 사용자가 "충분히 빠르다고" 생각하지 못하게 + 늘리기때문에 웹서버는 스왑을 하면 안된다. 느려지면 사용자는 + 정지하고 다시 접속하여 부하가 계속 증가한다. <code class="directive"><a href="../mod/mpm_common.html#maxclients">MaxClients</a></code> 지시어를 조절하여 + 웹서버가 스왑을 할 정도로 많은 자식을 만들지않도록 해야 + 한다. 방법은 간단하다: <code>top</code>과 같은 도구에서 + 프로세스 목록을 보고 아파치 프로세스의 평균 메모리 사용량을 + 알아낸후, 전체 사용가능한 메모리에서 다른 프로세스들이 사용할 + 공간을 뺀 값에서 나눈다.</p> + + <p>나머지는 평범하다: 충분히 빠른 CPU, 충분히 빠른 네트웍카드, + 충분히 빠른 디스크, 여기서 "충분히 빠른"은 실험을 해서 결정해야 + 한다.</p> + + <p>운영체제는 보통 각자 알아서 선택할 일이다. 그러나 일반적으로 + 유용하다고 판명된 몇가지 지침이 있다:</p> + + <ul> + <li> + <p>선택한 운영체제의 최신 안정 버전과 패치를 실행한다. + 많은 운영체제 제작사는 최근 TCP 스택과 쓰레드 라이브러리에 + 많은 속도향상을 했다.</p> + </li> + + <li> + <p>운영체제가 <code>sendfile(2)</code> 시스템호출을 + 지원한다면, 이를 사용하기위한 버전이나 패치를 설치하였는지 + 확인한다. (예를 들어, 리눅스라면 2.4 이상 버전을 뜻한다. + Solaris 8 초기 버전은 패치가 필요하다.) 지원하는 시스템이라면 + 아파치 2는 <code>sendfile</code>을 사용하여 CPU를 덜 + 사용하며 정적 파일을 더 빨리 전송할 수 잇다.</p> + </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="runtime" id="runtime">실행시 설정에 대해서</a></h2> + + + + <table class="related"><tr><th>관련된 모듈</th><th>관련된 지시어</th></tr><tr><td><ul><li><code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code></li><li><code class="module"><a href="../mod/mpm_common.html">mpm_common</a></code></li><li><code class="module"><a href="../mod/mod_status.html">mod_status</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code></li><li><code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code></li><li><code class="directive"><a href="../mod/core.html#enablemmap">EnableMMAP</a></code></li><li><code class="directive"><a href="../mod/core.html#enablesendfile">EnableSendfile</a></code></li><li><code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code></li><li><code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code></li><li><code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code></li></ul></td></tr></table> + + <h3><a name="dns" id="dns">HostnameLookups와 DNS에 대해 고려할 점들</a></h3> + + + + <p>아파치 1.3 이전에 <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code>의 기본값은 + <code>On</code>이였다. 요청을 마치기전에 DNS 검색이 끝나야 + 하므로 요청마다 지연이 생겼다. 아파치 1.3에서 이 설정의 + 기본값이 <code>Off</code>로 변경되었다. 로그파일의 주소를 + 호스트명으로 변환하려면 여러 로그처리 프로그램중 하나인, + 아파치에 포함된 <a href="../programs/logresolve.html"><code>logresolve</code></a> + 프로그램을 사용하라.</p> + + <p>로그처리 작업이 서버 성능에 악영향을 미치므로 실제 + 사용하는 웹서버가 아닌 다른 컴퓨터에서 로그파일을 후처리하길 + 바란다.</p> + + <p><code><code class="directive"><a href="../mod/mod_access.html#allow">Allow</a></code> + from domain</code>이나 <code><code class="directive"><a href="../mod/mod_access.html#deny">Deny</a></code> from domain</code> + 지시어를 사용한다면 (즉, IP 주소가 아닌 호스트명이나 도메인명을 + 사용한다면) 부득이 중복-역 DNS 검색을 (역검색을 한후 악의로 + 변경되었는지 확인하기위해 다시 검색) 해야 한다. 그러므로 + 성능을 높이기위해 이런 지시어에는 가능하면 이름대신 IP + 주소를 사용한다.</p> + + <p><code><Location /server-status></code> 섹션 등으로 + 지시어의 적용범위를 제한할 수 있음을 기억하라. 이 경우 + 조건에 맞는 요청에만 DNS 조회를 한다. 다음은 + <code>.html</code>과 <code>.cgi</code> 파일만 DNS 검색을 + 하는 예제다:</p> + + <div class="example"><p><code> + HostnameLookups off<br /> + <Files ~ "\.(html|cgi)$"><br /> + <span class="indent"> + HostnameLookups on<br /> + </span> + </Files> + </code></p></div> + + <p>그러나 CGI에서 DNS명이 필요할 뿐이라면, 필요한 특정 + CGI에서만 <code>gethostbyname</code> 호출을 하도록 고려해볼 + 수 있다.</p> + + + + <h3><a name="symlinks" id="symlinks">FollowSymLinks와 SymLinksIfOwnerMatch</a></h3> + + + + <p>URL 공간에서 <code>Options FollowSymLinks</code>를 + 사용하지않고 <code>Options SymLinksIfOwnerMatch</code>를 + 사용하면 아파치는 심볼링크를 검사하기위해 시스템호출을 + 한번 더 해야 한다. 파일명의 각 부분마다 한번씩 더 호출을 + 한다. 예를 들어, 설정이 다음과 같고:</p> + + <div class="example"><p><code> + DocumentRoot /www/htdocs<br /> + <Directory /><br /> + <span class="indent"> + Options SymLinksIfOwnerMatch<br /> + </span> + </Directory> + </code></p></div> + + <p><code>/index.html</code> URI에 대한 요청이 있다고 가정하자. + 그러면 아파치는 <code>/www</code>, <code>/www/htdocs</code>, + <code>/www/htdocs/index.html</code> 각각에 대해 + <code>lstat(2)</code>를 호출한다. <code>lstats</code> + 결과를 캐싱하지 않기때문에 요청이 들어올 때마다 매번 같은 + 작업을 한다. 진짜 심볼링크 보안 검사를 원한다면 다음과 + 같이 할 수 있다:</p> + + <div class="example"><p><code> + DocumentRoot /www/htdocs<br /> + <Directory /><br /> + <span class="indent"> + Options FollowSymLinks<br /> + </span> + </Directory><br /> + <br /> + <Directory /www/htdocs><br /> + <span class="indent"> + Options -FollowSymLinks +SymLinksIfOwnerMatch<br /> + </span> + </Directory> + </code></p></div> + + <p>이 경우 최소한 <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> 경로는 검사하지 + 않는다. DocumentRoot 밖에 있는 경로로 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>나 <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>을 사용한 + 경우에도 위와 비슷한 섹션이 필요하다. 심볼링크 보안을 + 고려하지 않고 최고의 성능을 얻으려면, + <code>FollowSymLinks</code>를 설정하고, + <code>SymLinksIfOwnerMatch</code>는 절대로 안된다.</p> + + + + <h3><a name="htacess" id="htacess">AllowOverride</a></h3> + + + + <p>URL 공간에서 overrides를 허용한다면 (보통 + <code>.htaccess</code> 파일) 아파치는 파일명의 각 부분마다 + <code>.htaccess</code>를 열길 시도한다. 예를 들어,</p> + + <div class="example"><p><code> + DocumentRoot /www/htdocs<br /> + <Directory /><br /> + <span class="indent"> + AllowOverride all<br /> + </span> + </Directory> + </code></p></div> + + <p><code>/index.html</code> URI에 대한 요청이 있다고 가정하자. + 아파치는 <code>/.htaccess</code>, <code>/www/.htaccess</code>, + <code>/www/htdocs/.htaccess</code>를 열려고 시도한다. + 해결책은 앞의 <code>Options FollowSymLinks</code> 경우와 + 비슷하다. 최고의 성능을 얻으려면 파일시스템에 대해서 항상 + <code>AllowOverride None</code>을 사용한다.</p> + + + + <h3><a name="negotiation" id="negotiation">내용협상</a></h3> + + + + <p>가능하고 진짜 조금의 성능향상에도 관심이 있다면 내용협상을 + 막는다. 실제로 협상의 이득은 성능저하보다 작다. 서버를 + 빠르게 할 수 있다. 다음과 같이 와일드카드를 사용하는 대신:</p> + + <div class="example"><p><code> + DirectoryIndex index + </code></p></div> + + <p>완전한 목록을 사용한다:</p> + + <div class="example"><p><code> + DirectoryIndex index.cgi index.pl index.shtml index.html + </code></p></div> + + <p>가장 흔한 것을 앞에 둔다.</p> + + <p>또, 디렉토리에서 파일들을 찾는 <code>MultiViews</code> + 보다는, 한 파일만 읽으면 필요한 정보를 얻을 수 있는 + <code>type-map</code> 파일을 직접 만드는 것이 더 빠름을 + 명심하라.</p> + + <p>사이트에 내용협상이 필요하다면 협상을 위해 <code>Options + MultiViews</code> 지시어를 사용하기보다 <code>type-map</code> + 파일을 고려하라. 협상방법에 대한 자세한 설명과 + <code>type-map</code> 파일을 만드는 방법은 <a href="../content-negotiation.html">내용협상</a> 문서를 참고하라.</p> + + + + <h3>메모리대응 (memory-mapping)</h3> + + + + <p>예를 들어, server-side-include를 처리하는 등 아파치 + 2.0이 전송할 파일을 읽을때 운영체제가 <code>mmap(2)</code> + 등을 지원한다면 파일을 메모리대응한다.</p> + + <p>여러 플래폼에서 메모리대응을 성능을 향상한다. 그러나 + 메모리대응이 서버의 성능을 떨어트리고 심지어 안정성을 + 해치는 경우가 있다:</p> + + <ul> + <li> + <p>어떤 운영체제에서 <code>mmap</code>은 CPU 개수가 + 많아질때 <code>read(2)</code> 만큼 확장성이 좋지 않다. + 예를 들어, 다중프로세서 Solaris 서버에서 아파치 2.0은 + 종종 <code>mmap</code>을 사용하지 않을때 서버가 처리한 + 파일을 더 빨리 전송한다.</p> + </li> + + <li> + <p>NFS 마운트한 파일시스템에 있는 파일을 메모리대응하는 + 도중에 다른 NFS 클라이언트에 있는 프로세스가 파일을 + 지우거나 파일크기를 줄이면, 웹서버 프로세스가 다음 + 번에 메모리대응한 파일내용을 읽을때 bus error가 발생할 + 수 있다.</p> + </li> + </ul> + + <p>위의 조건에 해당하면 전송하는 파일을 메모리대응하지 + 않도록 <code>EnableMMAP off</code>를 사용해야 한다. (주의: + 이 지시어는 디렉토리별로 변경할 수 있다.)</p> + + + + <h3>Sendfile</h3> + + + + <p>아파치는 운영체제가 <code>sendfile(2)</code>을 지원하면 + 커널 sendfile을 사용하여 -- 예를 들어, 정적 파일을 서비스할때 + -- 전송할 파일을 직접 읽지않을 수 있다.</p> + + <p>여러 플래폼에서 sendfile을 사용하면 read와 send를 따로 + 할 필요가 없어서 빨라진다. 그러나 sendfile을 사용하면 + 웹서버의 안정성을 해치게되는 경우가 있다:</p> + + <ul> + <li> + <p>sendfile 지원이 잘못되었고 컴파일 시스템이 이점을 + 발견하지 못하는 플래폼이 있다. 특히 다른 컴퓨터에서 + 실행파일을 컴파일하여 sendfile 지원이 잘못된 컴퓨터로 + 가져온 경우에 가능하다.</p> + </li> + <li> + <p>커널은 자신의 캐쉬를 사용하여 NFS로 마운트한 파일을 + 안정적으로 서비스할 수 없는 경우가 있다.</p> + </li> + </ul> + + <p>위의 조건에 해당하면 파일을 sendfile 전송하지 않도록 + <code>EnableSendfile off</code>를 사용해야 한다. (주의: + 이 지시어는 디렉토리별로 변경할 수 있다.)</p> + + + + <h3><a name="process" id="process">프로세스 생성</a></h3> + + + + <p>아파치 1.3 이전에는 <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code>, <code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code>, <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> 설정이 모두 + 벤치마크 결과에 큰 영향을 미쳤다. 특히 아파치는 작업을 + 서비스하기위해 충분한 자식수에 다다를 때까지 "도달" 기간이 + 필요했다. 처음 <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code>개 자식을 + 만든후, <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code> + 설정값까지 초당 자식을 하나씩 만들었다. 그래서 <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> 기본값이 + <code>5</code>인 서버에 클라이언트 100개가 동시에 접속하면 + 부하를 처리하기에 충분한 자식을 만들기까지 95초가 걸렸다. + 자주 재시작하지 않는 실제 서버에서는 잘 동작하지만, 10분간만 + 실행하는 벤치마크 결과는 매우 나쁘게 나온다.</p> + + <p>초당 한개 규칙은 자식을 새로 시작하면서 서버에 무리를 + 주지 않으려고 정했다. 컴퓨터가 자식을 시작하느라 바쁘면 + 요청을 서비스할 수 없다. 그러나 이 규칙이 아파치의 체감 + 성능에 악영향을 주어 변경하였다. 아파치 1.3에서 초당 한개 + 규칙은 완화되었다. 코드는 자식 한개를 만들고, 1초 쉬고, + 두개를 만들고, 1초 쉬고, 네개를 만들고, 이런 식으로 초당 + 자식을 32개 만들때까지 지수로 증가한다. 자식수가 <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code> 설정에 다다르면 + 증가를 중단한다.</p> + + <p>이 경우 반응속도가 빨라져서 <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code>, <code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code>, <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code>를 거의 설정할 필요가 없다. 일초에 + 자식을 4개 이상 생성하면 <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code>에 기록한다. 이런 오류문이 + 많이 보이면 이 설정들을 조절하길 바란다. + <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> 결과가 도움이 될 것이다.</p> + + <p>프로세스 생성과 관련하여 <code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> 설정은 + 프로세스를 종료한다. 기본값은 자식당 처리할 요청수에 제한이 + 없다는 <code>0</code>이다. 현재 설정이 <code>30</code>과 + 같이 매우 작은 값으로 설정되있다면, 값을 상당히 높힐 필요가 + 있다. SunOS나 오래된 Solaris 버전을 사용한다면, 메모리유출때문에 + 이 값을 <code>10000</code> 정도로 설정하라.</p> + + <p>연결유지(keep-alive)를 사용한다면 자식들은 이미 열린 + 연결에서 추가 요청을 기다리며 아무것도 하지않기때문에 계속 + 바쁘다. <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code>의 + 기본값 <code>15</code> 초는 이런 현상을 최소화한다. 네트웍 + 대역폭과 서버 자원 간의 균형이 맞게 설정한다. <a href="http://www.research.digital.com/wrl/techreports/abstracts/95.4.html"> + 연결유지의 대부분의 이점이 사라지기때문에</a> 어떤 경우에도 + 이 값을 <code>60</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="compiletime" id="compiletime">컴파일시 설정에 대해서</a></h2> + + + + <h3>MPM 선택</h3> + + + + <p>아파치 2.x는 <a href="../mpm.html">다중처리모듈</a> + (MPMs)이라는 교체할 수 있는 동기화 모델을 지원한다. 아파치를 + 컴파일할때 MPM을 선택해야 한다. <code class="module"><a href="../mod/beos.html">beos</a></code>, + <code class="module"><a href="../mod/mpm_netware.html">mpm_netware</a></code>, <code class="module"><a href="../mod/mpmt_os2.html">mpmt_os2</a></code>, + <code class="module"><a href="../mod/mpm_winnt.html">mpm_winnt</a></code>와 같이 특정 플래폼에서만 사용할 + 수 있는 MPM도 있다. 일반적인 유닉스류 시스템은 여러 MPM + 중에 하나를 선택할 수 있다. 웹서버의 속도와 + 확장성(scalability)은 어떤 MPM을 선택했냐에 달렸다:</p> + + <ul> + + <li><code class="module"><a href="../mod/worker.html">worker</a></code> MPM은 여러 자식 프로세스가 + 각각 여러 쓰레드를 사용한다. 각 쓰레드는 한번에 한 연결을 + 담당한다. 일반적으로 worker는 prefork MPM 보다 적은 + 메모리를 사용하므로 통신량이 많은 서버에 적절하다.</li> + + <li><code class="module"><a href="../mod/prefork.html">prefork</a></code> MPM은 쓰레드가 한개인 자식 + 프로세스를 여러개 사용한다. 각 프로세스는 한번에 한 + 연결을 담당한다. 여러 시스템에서 prefork의 속도는 worker와 + 비슷하지만, 더 많은 메모리를 사용한다. 다음과 같은 상황에서 + 쓰레드를 사용하지 않는 prefork 방식이 worker에 비해 + 이점을 가진다: 쓰레드에 안전하지 (thread-safe) 않은 + 제삼자가 만든 모듈을 사용할 수 있고, 쓰레드 디버깅 지원이 + 빈약한 플래폼에서 쉽게 디버깅할 수 있다.</li> + + </ul> + + <p>이 MPM들과 다른 MPM에 대해 더 자세한 정보는 MPM <a href="../mpm.html">문서</a>를 참고하길 바란다.</p> + + + + <h3><a name="modules" id="modules">모듈</a></h3> + + + + <p>메모리 사용량이 성능에서 가장 중요한 요인이기때문에 + 실제로 사용하지 않는 모듈을 제거해보자. 모듈을 <a href="../dso.html">DSO</a>로 컴파일했다면 간단히 그 + 모듈에 대한 <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> 지시어를 주석처리하면 + 된다. 그래서 모듈을 제거하고 실행하여 사이트가 모듈없이도 + 정상적으로 동작하는지 살펴볼 수 있다.</p> + + <p>반대로 모듈이 아파치 실행파일에 정적으로 링크되있다면 + 원하지 않는 모듈을 제거하기위해 아파치를 재컴파일해야 + 한다.</p> + + <p>여기서 당연히 어떤 모듈을 사용하고 사용하지 말지 + 의문이 생긴다. 정답은 웹사이트마다 다르다. 그러나 아마도 + <em>최소한</em> <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code>, + <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code>, <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code> + 모듈은 사용할 것이다. 물론 웹사이트에 로그파일이 필요없다면 + <code>mod_log_config</code>는 없어도 된다. 그러나 추천하지 + 않는다.</p> + + + + <h3>Atomic 명령</h3> + + + + <p><code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code> 같은 모듈과 최근 개발중인 + worker MPM은 APR의 atomic API를 사용한다. 이 API는 경량급 + 쓰레드 동기화를 위할 atomic 명령을 제공한다.</p> + + <p>기본적으로 APR은 각 운영체제/CPU 플래폼에서 가장 효율적인 + 방법을 사용하여 이 명령을 구현한다. 예를 들어, 여러 최신 + CPU에는 하드웨어로 atomic compare-and-swap (CAS) 연산을 + 하는 명령어가 있다. 그러나 어떤 플래폼에서 APR은 이런 + 명령어가 없는 오래된 CPU와 호환성을 위해 더 느린 mutex기반 + 구현을 기본적으로 사용한다. 이런 플래폼에서 아파치를 + 컴파일할때 아파치를 최신 CPU에서만 실행할 계획이라면, + 아파치를 구성할때 <code>--enable-nonportable-atomics</code> + 옵션을 사용하여 더 빠른 atomic 구현을 선택할 수 있다:</p> + + <div class="example"><p><code> + ./buildconf<br /> + ./configure --with-mpm=worker --enable-nonportable-atomics=yes + </code></p></div> + + <p><code>--enable-nonportable-atomics</code> 옵션은 다음과 + 같은 플래폼에 영향이 있다:</p> + + <ul> + + <li>SPARC에서 Solaris<br /> + 기본적으로 APR은 Solaris/SPARC에서 mutex기반 atomic을 + 사용한다. 그러나 구성할때 + <code>--enable-nonportable-atomics</code>를 사용하면 + APR은 빠른 하드웨어 compare-and-swap을 위한 SPARC + v8plus 명령어를 사용한다. 이 옵션을 사용하면 atomic + 명령이 더 효율적이지만 (CPU를 덜 사용하고 더 높은 + 동기화가 가능하다), 컴파일한 실행파일은 UltraSPARC + 칩에서만 실행할 수 있다. + </li> + + <li>Linux on x86<br /> + 기본적으로 APR은 리눅스에서 mutex기반 atomic을 + 사용한다. 그러나 구성할때 + <code>--enable-nonportable-atomics</code>를 사용하면 + APR은 빠른 하드웨어 compare-and-swap을 위한 486 + 명령어를 사용한다. 더 효율적인 atomic 명령이 가능하지만, + 컴파일한 실행파일은 486 이상 칩에서만 (386은 안된다) + 실행할 수 있다. + </li> + + </ul> + + + + <h3>mod_status와 ExtendedStatus On</h3> + + + + <p>아파치를 컴파일할때 <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>를 포함하고 + 실행할때 <code>ExtendedStatus On</code>을 설정하면 아파치는 + 요청을 받을때마다 <code>gettimeofday(2)</code>(혹은 운영체제에 + 따라 <code>times(2)</code>)를 두번 호출하고 (1.3 이전에는) + <code>time(2)</code>도 추가로 여러번 호출한다. 상태 보고서에 + 동작시간이 필요하기 때문이다. 최상의 성능을 얻으려면 + (기본값인) <code>ExtendedStatus off</code>를 설정한다.</p> + + + + <h3>accept 직렬화 - 여러 소켓</h3> + + + + <div class="warning"><h3>주의:</h3> + <p> 아래 문서는 아파치 웹서버 2.0 버전에서 변경된 내용을 + 담고 있지 않다. 아직도 유효한 정보가 있지만, 주의해서 + 사용하길 바란다.</p> + </div> + + <p>유닉스 소켓 API의 단점을 설명한다. 웹서버가 여러 포트 + 혹은 여러 주소를 기다리기위해 여러 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>을 사용한다고 가정하자. + 연결이 가능한지 각 소켓을 검사하기위해 아파치는 + <code>select(2)</code>를 사용한다. <code>select(2)</code>는 + 소켓에 기다리고 있는 연결이 <em>없는지</em> 혹은 <em>최소한 + 한개</em> 있는지 알려준다. 아파치에는 여러 자식이 있고, + 쉬고 있는 모든 자식은 동시에 새로운 연결을 검사한다. 원래 + 구현은 다음과 비슷하다 (이 예는 코드에서 가져오지 않았다. + 단지 설명하기위한 용도로 만들었다.):</p> + + <div class="example"><p><code> + for (;;) {<br /> + <span class="indent"> + for (;;) {<br /> + <span class="indent"> + fd_set accept_fds;<br /> + <br /> + FD_ZERO (&accept_fds);<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + FD_SET (i, &accept_fds);<br /> + </span> + }<br /> + rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);<br /> + if (rc < 1) continue;<br /> + new_connection = -1;<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + if (FD_ISSET (i, &accept_fds)) {<br /> + <span class="indent"> + new_connection = accept (i, NULL, NULL);<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + </span> + }<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + process the new_connection;<br /> + </span> + } + </code></p></div> + + <p>그러나 위의 단순한 구현에는 심각한 고갈(starvation) + 문제가 있다. 여러 자식이 동시에 이 반복문을 실행하면, + 요청을 기다리며 모두 <code>select</code>에서 멈춘다. 이때 + 어떤 소켓에 요청이 하나라도 들어오면 모든 자식이 깨어난다 + (깨어나는 자식의 개수는 운영체제와 타이밍에 따라 다르다). + 이들은 모두 연결을 <code>accept</code>하길 시도한다. 그러나 + (아직도 한 연결만 대기중이라면) 한 자식만 성공하고, 나머지는 + <code>accept</code>에서 <em>멈춘다.</em> 그러면 이 자식들은 + 한 소켓의 요청만을 서비스하도록 묶여서, 그 소켓으로 새로운 + 요청이 충분히 들어와서 모든 자식을 깨울때까지 정지해있다. + 이런 고갈 문제는 <a href="http://bugs.apache.org/index/full/467">PR#467</a>에 + 처음 보고되었다. 최소한 두가지 해결책이 있다.</p> + + <p>한가지는 소켓을 대기하지 않도록 (non-blocking) 만드는 + 방법이다. 이 경우 자식이 <code>accept</code>를 해도 멈추지 + 않고, 즉시 진행할 수 있다. 그러나 CPU 시간을 낭비한다. + <code>select</code>에서 쉬는 자식이 10개 있고, 새로 연결이 + 한개 들어왔다고 가정하자. 그러면 이 자식중 9개는 깨어나서 + 연결을 <code>accept</code>하길 시도하고 실패하면 아무 + 일도 하지 않고 다시 <code>select</code>를 반복한다. 다시 + <code>select</code>로 돌아올 때까지 어떤 자식도 다른 소켓에 + 들어온 요청을 서비스하지 않는다. (다중프로세서 컴퓨터에서) + 쉬는 자식 개수만큼 CPU 개수가 있는 드문 경우가 아니라면 + 이 해결책은 별로 좋아보이지 않는다.</p> + + <p>다른 방법은 아파치가 사용하는 방법으로 내부 반복문에 + 한 자식만을 들여보낸다. 반복문은 다음과 같다 (차이를 + 강조했음):</p> + + <div class="example"><p><code> + for (;;) {<br /> + <span class="indent"> + <strong>accept_mutex_on ();</strong><br /> + for (;;) {<br /> + <span class="indent"> + fd_set accept_fds;<br /> + <br /> + FD_ZERO (&accept_fds);<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + FD_SET (i, &accept_fds);<br /> + </span> + }<br /> + rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);<br /> + if (rc < 1) continue;<br /> + new_connection = -1;<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + if (FD_ISSET (i, &accept_fds)) {<br /> + <span class="indent"> + new_connection = accept (i, NULL, NULL);<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + </span> + }<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + <strong>accept_mutex_off ();</strong><br /> + process the new_connection;<br /> + </span> + } + </code></p></div> + + <p><code>accept_mutex_on</code>과 <code>accept_mutex_off</code> + <a id="serialize" name="serialize">함수</a>는 mutex 세마포어를 + 구현한다. 한번에 오직 한 자식만이 mutex를 가질 수 있다. + mutex를 구현하는 방법은 여러가지이다. 구현 방법은 (1.3 + 이전) <code>src/conf.h</code>나 (1.3과 그 이후) + <code>src/include/ap_config.h</code>에 정의되있다. 어떤 + 아키텍쳐는 잠금(locking) 방법을 선택하지 않기때문에, 이런 + 아키텍쳐에서 여러 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> 지시어를 사용하면 + 위험하다.</p> + + <p>실행시 <code class="directive"><a href="../mod/mpm_common.html#acceptmutex">AcceptMutex</a></code> 지시어를 사용하여 + mutex 구현을 변경할 수 있다.</p> + + <dl> + <dt><code>AcceptMutex flock</code></dt> + + <dd> + <p>이 방법은 잠금파일을 잠그기위해 <code>flock(2)</code> + 시스템호출을 사용한다 (잠금파일 위치는 <code class="directive"><a href="../mod/mpm_common.html#lockfile">LockFile</a></code> 지시어로 지정).</p> + </dd> + + <dt><code>AcceptMutex fcntl</code></dt> + + <dd> + <p>이 방법은 잠금파일을 잠그기위해 <code>fcntl(2)</code> + 시스템호출을 사용한다 (잠금파일 위치는 <code class="directive"><a href="../mod/mpm_common.html#lockfile">LockFile</a></code> 지시어로 지정).</p> + </dd> + + <dt><code>AcceptMutex sysvsem</code></dt> + + <dd> + <p>(1.3과 그 이후) 이 방법을 SysV식 세마포어를 사용하여 + mutex를 구현한다. 불행히도 SysV식 세마포어는 나쁜 + 부작용이 있다. 하나는 아파치가 세마포어를 정리하지 + 않고 죽을 수 있는 점이다 (<code>ipcs(8)</code> manpage + 참고). 다른 하나는 웹서버와 동일한 uid로 실행하는 + CGI가 (<em>즉,</em> <code>suexec</code>나 + <code>cgiwrapper</code>를 사용하지않는 한 모든 CGI) + 세마포어 API를 사용하여 서비스거부공격을 할 수 있는 + 점이다. 이런 이유때문에 IRIX를 제외한 아키텍쳐에서 + 이 방법을 사용하지 않는다 (대부분의 IRIX 컴퓨터에서 + 앞의 두 방법은 지나치게 버겁다).</p> + </dd> + + <dt><code>AcceptMutex pthread</code></dt> + + <dd> + <p>(1.3과 그 이후) 이 방법은 POSIX mutex를 사용하기때문에 + POSIX 쓰레드 규약을 완전히 구현한 아키텍쳐라면 모두 + 사용가능하지만, (2.5 이후) Solaris에서만 그것도 특정 + 구성에서만 동작하는 듯하다. 이 방법을 시도해본다면 + 서버가 멈춰서 응답을 안하는지 살펴봐야 한다. 정적 + 내용만 서비스하는 서버는 잘 동작하는 것 같다.</p> + </dd> + + <dt><code>AcceptMutex posixsem</code></dt> + + <dd> + <p>(2.0과 그 이후) 이 방법은 POSIX 세마포어를 사용한다. + mutex를 가진 프로세스의 쓰레드가 죽는다면(segfault) + 세마포어 소유권이 회복되지 않아서 웹서버가 멈춘다.</p> + </dd> + + </dl> + + <p>시스템에 위 목록에 없는 직렬화(serialization) 방법이 + 있다면 그 방법을 사용하는 코드를 APR에 추가할 가치가 있다.</p> + + <p>고려는 해봤지만 구현하지않은 다른 방법은 부분적으로 + 반복문을 직렬화하는 방법이다. 즉, 프로세서를 몇개만 들여보내는 + 것이다. 이 방법은 여러 자식을 동시에 실행할 수 있어서 + 직렬화때문에 전체 대역폭을 활용하지 못하는 다중프로세서 + 컴퓨터에서만 관심을 가져볼 수 있다. 앞으로 살펴볼 부분이지만, + 매우 병렬화된 웹서버가 흔하지 않아서 우선순위가 낮다.</p> + + <p>최상의 성능을 얻기위해서는 여러 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> 문을 사용하지 않는 + 것이 이상적이다. 그러나 계속 설명한다.</p> + + + + <h3>accept 직렬화 - 소켓 한개</h3> + + + + <p>앞의 설명은 다중소켓 서버에는 좋지만, 소켓이 한개인 + 서버는 어떤가? 연결이 도착할때까지 모든 자식이 + <code>accept(2)</code>에서 멈춰있기때문에 이론상 같은 + 문제가 발생하지 않고, 고갈 문제도 없다. 그러나 실제로는 + 앞에서 말한 대기하지 않는 (non-blocking) 방법에서 발생하는 + "공회전(spinning)" 현상을 감추고 있다. 대부분의 TCP 스택은 + 연결이 도착하면 커널이 <code>accept</code>에서 멈춰있는 + 모든 자식을 깨우도록 구현되있다. 프로세스중 한개가 연결을 + 얻고 사용자영역으로 돌아가고, 나머지는 커널에서 공회전하여 + 연결이 없음을 발견하면 다시 잠을 잔다. 사용자영역 코드에서는 + 이런 공회전을 알 수 없지만, 분명히 존재한다. 그래서 다중소켓의 + 대기하지 않는 방법과 동일하게 부하를 높이는 불필요한 행동이 + 일어난다.</p> + + <p>그래서 우리는 여러 아키텍쳐에서 소켓이 한개인 경우에도 + 직렬화하면 더 "잘" 동작함을 발견했다. 그래서 거의 대부분의 + 경우 기본적으로 직렬화를 사용한다. 리눅스에서 (커널 2.0.30, + 128Mb 메모리에 듀얼 Pentium pro) 실험한 결과 소켓 한개를 + 직렬화하면 하지 않은 경우에 비해 초당 요청이 3% 미만 + 줄어들었다. 그러나 직렬화를 하지 않은 경우 요청당 100ms + 지연이 발생했다. 이 지연은 아마도 LAN에서 발생하는 긴 + 연결선때문일 것이다. 소켓이 한개인 경우 직렬화를 사용하지 + 않으려면 <code>SINGLE_LISTEN_UNSERIALIZED_ACCEPT</code>를 + 정의한다.</p> + + + + <h3>Close 지연(lingering)</h3> + + + + <p><a href="http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-connection-00.txt"> + draft-ietf-http-connection-00.txt</a> 8절에서 설명하듯이 + <strong>안정적인</strong> 웹서버가 되려면, 통신의 양 방향을 + 독립적으로 닫을 수 있어야 한다 (TCP 연결은 쌍방향이고, + 방향은 서로 독립적이다). 이점을 다른 서버에서는 자주 + 간과하지만, 아파치는 1.2부터 정확히 구현해왔다.</p> + + <p>이 기능을 부주의하게 아파치에 추가했을때 여러 유닉스 + 버전에서 많은 문제가 발생했다. TCP 규약은 + <code>FIN_WAIT_2</code>에 타임아웃이 있다고 정하지 않았지만, + 금지하지도 않았다. 타임아웃이 없는 시스템에서 아파치 1.2는 + 많은 소켓을 영원히 <code>FIN_WAIT_2</code> 상태로 만들었다. + 많은 경우 이 문제는 제작사가 제공하는 최신 TCP/IP 패치를 + 적용하여 해결할 수 있다. 그러나 제작사가 패치를 발표하지 + 않는 경우가 (<em>즉,</em> SunOS4 -- 소스 라이선스가 있는 + 사람은 직접 패치할 수 있지만) 있기때문에 이 기능을 사용하지 + 않기로 결정했다.</p> + + <p>방법은 두가지다. 하나는 소켓 옵션 <code>SO_LINGER</code>를 + 사용하는 방법이다. 그러나 불행히도 대부분의 TCP/IP 스택은 + 이 옵션을 올바로 구현하지 않았다. 올바로 구현한 스택에서 + 조차도 (<em>즉,</em> 리눅스 2.0.31) 이 방법은 다음 방법보다 + 더 cpu를 잡아먹는다.</p> + + <p>아파치는 보통 (<code>http_main.c</code>에 있는) + <code>lingering_close</code>라는 함수를 사용한다. 이 함수는 + 대충 다음과 같다:</p> + + <div class="example"><p><code> + void lingering_close (int s)<br /> + {<br /> + <span class="indent"> + char junk_buffer[2048];<br /> + <br /> + /* shutdown the sending side */<br /> + shutdown (s, 1);<br /> + <br /> + signal (SIGALRM, lingering_death);<br /> + alarm (30);<br /> + <br /> + for (;;) {<br /> + <span class="indent"> + select (s for reading, 2 second timeout);<br /> + if (error) break;<br /> + if (s is ready for reading) {<br /> + <span class="indent"> + if (read (s, junk_buffer, sizeof (junk_buffer)) <= 0) {<br /> + <span class="indent"> + break;<br /> + </span> + }<br /> + /* just toss away whatever is here */<br /> + </span> + }<br /> + </span> + }<br /> + <br /> + close (s);<br /> + </span> + } + </code></p></div> + + <p>이 코드는 연결을 닫을때 더 CPU를 사용하지만, 안정적인 + 구현을 위해 필요하다. HTTP/1.1이 더 널리 퍼지고 모든 연결을 + 유지한다면(persistent), 연결을 받는 비용은 여러 요청을 + 처리하면서 상쇄될 것이다. 위험하게도 + <code>NO_LINGCLOSE</code>를 정의하여 이 기능을 사용하지 + 않을 수 있지만, 절대로 권하지 않는다. 특히 HTTP/1.1 + 파이프라인 <span class="transnote">(<em>역주;</em> 연결유지 상태에서 응답을 기다리지 + 않고 여러 요청을 보내는 기술)</span> 연결유지에는 + <code>lingering_close</code>가 필수적이다 (그리고 <a href="http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html"> + 파이프라인 연결이 더 빠르기때문에</a> 사용하길 바랄 것이다).</p> + + + + <h3>Scoreboard 파일</h3> + + + + <p>아파치의 부모와 자식은 scoreboard라는 것을 통해 서로 + 통신한다. 이상적으로는 scoreboard를 공유메모리로 구현해야 + 한다. 우리 개발자가 해당 운영체제에 접근할 수 있거나 상세한 + 포팅 결과를 받은 경우 보통 공유메모리를 사용하여 구현한다. + 나머지는 디스크에 있는 파일을 사용하여 구현한다. 디스크에 + 있는 파일은 느리고 신뢰도가 떨어진다 (기능도 더 적다). + <code>src/main/conf.h</code> 파일에서 사용하는 아키텍쳐를 + 찾아서 <code>USE_MMAP_SCOREBOARD</code> 혹은 + <code>USE_SHMGET_SCOREBOARD</code>인지 확인한다. 둘중 + 하나를 (각각 함께 사용할 <code>HAVE_MMAP</code>이나 + <code>HAVE_SHMGET</code>도 같이) 정의하면 공유메모리 코드를 + 사용한다. 시스템이 다른 종류의 공유메모리를 사용한다면 + <code>src/main/http_main.c</code> 파일을 수정하여 아파치에서 + 공유메모리를 사용할 수 있도록 훅(hook)을 추가하라. (또한 + 패치를 우리에게 보내주길 바란다.)</p> + + <div class="note">역사적 설명: 아파치의 리눅스 버전은 아파치 1.2 버전부터 + 공유메모리를 사용하기 시작했다. 리눅스에서 초기 아파치 + 버전이 느리고 신뢰도가 떨어졌기 때문이다.</div> + + + + <h3>DYNAMIC_MODULE_LIMIT</h3> + + + + <p>모듈을 동적으로 읽어들이지 않는다면 (가능한 조금이라도 + 성능을 높이기위해 이 글을 읽는다면 아마도 모듈을 동적으로 + 읽어들이지 않을 것이다), 서버를 컴파일할때 + <code>-DDYNAMIC_MODULE_LIMIT=0</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="trace" id="trace">부록: 시스템호출 기록을 자세히 분석하기</a></h2> + + + + <p>다음은 Solaris 8에서 worker MPM을 사용한 아파치 2.0.38의 + 시스템호출 기록(trace)이다. 아래 명령어를 사용하여 기록을 + 얻었다:</p> + + <div class="example"><p><code> + truss -l -p <var>httpd_child_pid</var>. + </code></p></div> + + <p><code>-l</code> 옵션을 사용하면 truss는 시스템호출을 + 하는 LWP (lightweight process, 경량급 프로세스--Solaris의 + 커널수준 쓰레드) ID를 같이 기록한다.</p> + + <p>다른 시스템에는 <code>strace</code>, <code>ktrace</code>, + <code>par</code> 같은 시스템호출 추적 도구가 있다. 결과는 + 비슷하다.</p> + + <p>클라이언트는 웹서버에게 크기가 10KB인 정적 파일을 요청한다. + 정적인 파일을 요청하지 않거나 내용협상하는 요청을 한 경우 + 기록이 매우 다르다 (때로는 매우 알아보기 힘들다).</p> + + <div class="example"><pre>/67: accept(3, 0x00200BEC, 0x00200C0C, 1) (sleeping...) +/67: accept(3, 0x00200BEC, 0x00200C0C, 1) = 9</pre></div> + + <p>위에서 연결대기(listener) 쓰레드가 LWP #67에서 실행됨을 + 알 수 있다.</p> + + <div class="note"><code>accept(2)</code> 직렬화를 사용하지 않음을 주목하라. + 여러 포트를 기다리지않는 경우 이 플래폼의 worker MPM은 + 기본적으로 직렬화하지 않은 accept를 사용한다.</div> + + <div class="example"><pre>/65: lwp_park(0x00000000, 0) = 0 +/67: lwp_unpark(65, 1) = 0</pre></div> + + <p>연결은 받아들이고(accept) 연결대기 쓰레드는 + worker 쓰레드를 깨워서 요청을 처리하게 한다. 아래 기록에서 + 요청을 처리하는 worker 쓰레드가 LWP #65임을 알 수 있다.</p> + + <div class="example"><pre>/65: getsockname(9, 0x00200BA4, 0x00200BC4, 1) = 0</pre></div> + + <p>가상호스트를 구현하기위해 아파치는 연결을 받아들인 + 지역(local) 소켓 주소를 알아야 한다. (가상호스트를 사용하지 + 않거나 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + 지시어에 와일드카드 주소를 사용하지 않은 경우 등) 많은 경우 + 이 호출을 없앨 수 있다. 그러나 아직 이런 최적화 작업이 + 안되있다. </p> + + <div class="example"><pre>/65: brk(0x002170E8) = 0 +/65: brk(0x002190E8) = 0</pre></div> + + <p><code>brk(2)</code> 호출은 힙(heap)에서 메모리를 할당한다. + 웹서버는 대부분의 요청 처리시 자체 메모리 + 할당자(<code>apr_pool</code>과 <code>apr_bucket_alloc</code>)를 + 사용하기때문에 시스템호출 기록에서 이 시스템호출을 보기가 + 드물다. 이 기록에서 웹서버는 시작하자마자 자체 메모리 할당자가 + 사용할 메모리블록을 얻기위해 <code>malloc(3)</code>을 호출한다.</p> + + <div class="example"><pre>/65: fcntl(9, F_GETFL, 0x00000000) = 2 +/65: fstat64(9, 0xFAF7B818) = 0 +/65: getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B910, 2190656) = 0 +/65: fstat64(9, 0xFAF7B818) = 0 +/65: getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B914, 2190656) = 0 +/65: setsockopt(9, 65535, 8192, 0xFAF7B918, 4, 2190656) = 0 +/65: fcntl(9, F_SETFL, 0x00000082) = 0</pre></div> + + <p>다음 worker 쓰레드는 클라이언트의 연결(파일기술자 9)을 + 대기안함(non-blocking) 상태로 바꾼다. <code>setsockopt(2)</code>와 + <code>getsockopt(2)</code> 호출은 Solaris의 libc가 소켓에 + 대한 <code>fcntl(2)</code>을 어떻게 처리하는지 보여준다.</p> + + <div class="example"><pre>/65: read(9, " G E T / 1 0 k . h t m".., 8000) = 97</pre></div> + + <p>worker 쓰레드는 클라이언트로 부터 요청을 읽는다.</p> + + <div class="example"><pre>/65: stat("/var/httpd/apache/httpd-8999/htdocs/10k.html", 0xFAF7B978) = 0 +/65: open("/var/httpd/apache/httpd-8999/htdocs/10k.html", O_RDONLY) = 10</pre></div> + + <p>웹서버 설정은 <code>Options FollowSymLinks</code>와 + <code>AllowOverride None</code>이다. 그래서 요청한 파일경로의 + 각 디렉토리에 대해 <code>lstat(2)</code>하거나 + <code>.htaccess</code> 파일을 검사할 필요가 없다. 파일을 + 검사하기위해, 1) 파일이 있는지, 2) 디렉토리가 아닌 일반파일인지, + <code>stat(2)</code> 호출만 하면 된다.</p> + + <div class="example"><pre>/65: sendfilev(0, 9, 0x00200F90, 2, 0xFAF7B53C) = 10269</pre></div> + + <p>이 경우 웹서버는 한번의 <code>sendfilev(2)</code> 시스템호출로 + HTTP 응답헤더와 요청한 파일을 전송할 수 있다. Sendfile 지원여부는 + 운영체제마다 다르다. 다른 시스템이라면 <code>sendfile(2)</code>을 + 호출하기 전에 헤더를 보내기위해 <code>write(2)</code>나 + <code>writev(2)</code> 호출을 한다.</p> + + <div class="example"><pre>/65: write(4, " 1 2 7 . 0 . 0 . 1 - ".., 78) = 78</pre></div> + + <p><code>write(2)</code> 호출은 접근로그(access log)에 요청을 + 기록한다. 이 기록에 <code>time(2)</code> 호출이 없음을 주목하라. + 아파치 1.3과 달리 아파치 2.0은 시간을 알기위해 + <code>gettimeofday(3)</code>를 사용한다. + <code>gettimeofday</code>를 최적화한 리눅스와 Solaris 같은 + 몇몇 운영체제에서는 일반적인 시스템호출 부담이 없다.</p> + + <div class="example"><pre>/65: shutdown(9, 1, 1) = 0 +/65: poll(0xFAF7B980, 1, 2000) = 1 +/65: read(9, 0xFAF7BC20, 512) = 0 +/65: close(9) = 0</pre></div> + + <p>worker 쓰레드는 연결을 지연닫기(lingering close)한다.</p> + + <div class="example"><pre>/65: close(10) = 0 +/65: lwp_park(0x00000000, 0) (sleeping...)</pre></div> + + <p>마지막으로 worker 쓰레드는 방금 전송한 파일을 닫고, + 연결대기(listener) 쓰레드가 다른 연결을 할당할 때까지 + 정지한다.</p> + + <div class="example"><pre>/67: accept(3, 0x001FEB74, 0x001FEB94, 1) (sleeping...)</pre></div> + + <p>그동안 연결대기 쓰레드는 연결을 (모든 worker가 작업중이면 + 연결대기 쓰레드를 멈추는 worker MPM의 흐름제어 기능에 따라) + worker 쓰레드에 할당하자마자 다른 연결을 받아들일 수 있다. + 이 기록에는 나오지 않지만, worker 쓰레드가 방금 받은 연결을 + 처리하는 동안 다음 <code>accept(2)</code>가 (요청이 매우 + 많은 경우 항상) 일어날 수 있다.</p> + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/misc/perf-tuning.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/perf-tuning.html" title="Korean"> ko </a> | +<a href="../tr/misc/perf-tuning.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.tr.utf8 b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.tr.utf8 new file mode 100644 index 00000000..44b6dba2 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/perf-tuning.html.tr.utf8 @@ -0,0 +1,1100 @@ +<?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="tr" xml:lang="tr"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache��셝e Ba힊ar캇m캇n Artt캇r캇lmas캇 - Apache HTTP Sunucusu</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 href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Mod체ller</a> | <a href="../mod/directives.html">Y철nergeler</a> | <a href="../faq/">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas캇</a></p> +<p class="apache">Apache HTTP Sunucusu S체r체m 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Sunucusu</a> > <a href="http://httpd.apache.org/docs/">Belgeleme</a> > <a href="../">S체r체m 2.0</a> > <a href="./">횉e힊itli Belgeler</a></div><div id="page-content"><div id="preamble"><h1>Apache��셝e Ba힊ar캇m캇n Artt캇r캇lmas캇</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/misc/perf-tuning.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/perf-tuning.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/perf-tuning.html" title="T체rk챌e"> tr </a></p> +</div> + + + <p>Apache 2.x, esneklik, ta힊캇nabilirlik ve ba힊ar캇m aras캇nda bir denge + sa휓lamak 체zere tasarlanm캇힊 genel ama챌l캇 bir HTTP sunucusudur. Ba힊ka + sunucularla k캇yaslama denemelerinde 철ne ge챌mek 체zere tasarlanmam캇힊 + olsa da Apache 2.x ger챌ek ya힊amda kar힊캇la힊캇lan pek 챌ok durumda olduk챌a + y체ksek bir ba힊ar캇ma ula힊acak yetenektedir.</p> + + <p>Apache 1.3 ile kar힊캇la힊t캇r캇ld캇휓캇nda 2.x s체r체mleri toplam veri h캇z캇n캇 + ve 철l챌eklenebilirli휓i artt캇rmak i챌in pek 챌ok en iyileme se챌ene휓i + i챌erir. Bu iyile힊tirmelerin pek 챌o휓u zaten 철ntan캇ml캇 olarak etkin + olmakla birlikte derleme ve kullan캇m s캇ras캇nda ba힊ar캇m캇 철nemli 철l챌체de + etkileyebilen yap캇land캇rma se챌enekleri de mevcuttur. Bu belgede, bir + Apache 2.x kurulumunda sunucu y철neticisinin sunucunun ba힊ar캇m캇n캇 + artt캇rmak amac캇yla yap캇land캇rma s캇ras캇nda neler yapabilece휓inden + bahsedilmi힊tir. Bu yap캇land캇rma se챌eneklerinden baz캇lar캇, httpd��셬in + donan캇m캇n ve i힊letim sisteminin olanaklar캇ndan daha iyi + yararlanabilmesini sa휓larken bir k캇sm캇 da daha h캇zl캇 bir sunum i챌in + y철neticinin i힊levsellikten 철d체n verebilmesini olanakl캇 k캇lar.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#hardware">Donan캇m ve 캅힊letim Sistemi ile 캅lgili Konular</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#runtime">횉al캇힊ma An캇 Yap캇land캇rmas캇 ile 캅lgili Konular</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compiletime">Derleme S캇ras캇nda Yap캇land캇rma ile 캅lgili Konular</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#trace">Ek: Bir 챌a휓r캇 izlemesinin ayr캇nt캇l캇 챌철z체mlemesi</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="hardware" id="hardware">Donan캇m ve 캅힊letim Sistemi ile 캅lgili Konular</a></h2> + + + + <p>HTTP sunucusunun ba힊ar캇m캇n캇 etkileyen en 철nemli donan캇m bellektir + (RAM). Bir HTTP sunucusu asla takaslama yapmamal캇d캇r. 횉체nk체 takaslama, + kullan캇c캇n캇n "yeterince h캇z" umdu휓u noktada sunumun gecikmesine sebep + olur. B철yle bir durumda kullan캇c캇lar y체klemeyi durdurup tekrar + ba힊latma e휓ilimindedirler; sonu챌ta y체k daha da artar. <code class="directive"><a href="../mod/mpm_common.html#maxclients">MaxClients</a></code> y철nergesinin de휓erini + de휓i힊tirerek takaslamaya sebep olabilecek kadar 챌ok 챌ocuk s체re챌 + olu힊turulmas캇n캇 engelleyebilirsiniz ve b철yle bir durumda bunu mutlaka + yapmal캇s캇n캇z. Bunun i챌in yapaca휓캇n캇z i힊lem basittir: <code>top</code> + benzeri bir ara챌 체zerinden 챌al캇힊an s체re챌lerinizin bir listesini al캇p + Apache s체re챌lerinizin ortalama b체y체kl체휓체n체 saptay캇p, mevcut bellekten + bir k캇sm캇n캇 di휓er s체re챌ler i챌in ay캇rd캇ktan sonra kalan miktar캇 bu + de휓ere b철lerseniz y철nergeye atayaca휓캇n캇z de휓eri bulmu힊 olursunuz.</p> + + <p>Donan캇m캇n di휓er unsurlar캇 i챌in karar캇 siz verin: Daha h캇zl캇 i힊lemci, + daha h캇zl캇 a휓 kart캇, daha h캇zl캇 disk; daha h캇zl캇n캇n ne kadar h캇zl캇 + olaca휓캇n캇 deneyimlerinize ba휓l캇 olarak tamamen sizin ihtiya챌lar캇n캇z + belirler.</p> + + <p>캅힊letim sistemi se챌imi b체y체k oranda yerel ilgi konusudur. Fakat yine + de, genelde yararl캇l캇휓캇 kan캇tlanm캇힊 baz캇 kurallar bu se챌imde size + yard캇mc캇 olabilir:</p> + + <ul> + <li> + <p>Se챌ti휓iniz i힊letim sisteminin (챌ekirde휓in) en son kararl캇 + s체r체m체n체 챌al캇힊t캇r캇n. Bir 챌ok i힊letim sistemi, son y캇llarda TCP + y캇휓캇tlar캇 ve evre k체t체phaneleri ile ilgili belirgin iyile힊tirmeler + yapm캇힊lar ve yapmaktad캇rlar.</p> + </li> + + <li> + <p>캅힊letim sisteminiz <code>sendfile</code>(2) sistem 챌a휓r캇s캇n캇 + destekliyorsa bunun etkinle힊tirilebildi휓i s체r체m체n kurulu olmas캇 + 철nemlidir. (횜rne휓in, Linux i챌in bu, Linux 2.4 ve sonraki s체r체mler + anlam캇na gelirken, Solaris i챌in Solaris 8��셝en 철nceki s체r체mlerin + yamanmas캇 gerektirdi휓i anlam캇na gelmektedir.) + <code>sendfile</code> i힊levinin desteklendi휓i sistemlerde Apache 2 + duruk i챌eri휓i daha h캇zl캇 teslim etmek ve i힊lemci kullan캇m캇n캇 + d체힊체rmek amac캇yla bu i힊levselli휓i kullanacakt캇r.</p> + </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="runtime" id="runtime">횉al캇힊ma An캇 Yap캇land캇rmas캇 ile 캅lgili Konular</a></h2> + + + + <table class="related"><tr><th>캅lgili Mod체ller</th><th>캅lgili Y철nergeler</th></tr><tr><td><ul><li><code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code></li><li><code class="module"><a href="../mod/mpm_common.html">mpm_common</a></code></li><li><code class="module"><a href="../mod/mod_status.html">mod_status</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code></li><li><code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code></li><li><code class="directive"><a href="../mod/core.html#enablemmap">EnableMMAP</a></code></li><li><code class="directive"><a href="../mod/core.html#enablesendfile">EnableSendfile</a></code></li><li><code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code></li><li><code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code></li><li><code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code></li></ul></td></tr></table> + + <h3><a name="dns" id="dns"><code>HostnameLookups</code> ve DNS ile ilgili di휓er konular</a></h3> + + + + <p>Apache 1.3 철ncesinde, <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> y철nergesinin 철ntan캇ml캇 de휓eri + <code>On</code> idi. 캅stek yerine getirilmeden 철nce bir DNS sorgusu + yap캇lmas캇n캇 gerektirmesi sebebiyle bu ayarlama her istekte bir + miktar gecikmeye sebep olurdu. Apache 1.3��셳en itibaren y철nergenin + 철ntan캇ml캇 de휓eri <code>Off</code> yap캇lm캇힊t캇r. E휓er g체nl체k + dosyalar캇n캇zda konak isimlerinin bulunmas캇n캇 isterseniz, Apache ile + birlikte gelen <code class="program"><a href="../programs/logresolve.html">logresolve</a></code> program캇n캇 + kullanabilece휓iniz gibi g체nl체k raporlar캇n캇 챌철z체mleyen Apache ile + gelmeyen programlardan herhangi birini de kullanabilirsiniz.</p> + + <p>G체nl체k dosyalar캇 체zerindeki bu i힊lemi sunucu makinesi d캇힊캇nda + g체nl체k dosyas캇n캇n bir kopyas캇 체zerinde yapman캇z캇 철neririz. Aksi + takdirde sunucunuzun ba힊ar캇m캇 철nemli 철l챌체de etkilenebilir.</p> + + <p><code class="directive"><a href="../mod/mod_access.html#allow">Allow</a></code> veya + <code class="directive"><a href="../mod/mod_access.html#deny">Deny</a></code> + y철nergelerinde IP adresi yerine bir konak veya alan ismi + belirtirseniz, iki DNS sorguluk bir bedel 철dersiniz (biri normal, + di휓eri IP taklidine kar힊캇 ters DNS sorgusu). Ba힊ar캇m캇 en iyilemek + i챌in bu y철nergelerde m체mk체n oldu휓unca isim yerine IP adreslerini + kullan캇n캇z.</p> + + <p><code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> + y철nergelerinin <code><Location /server-status></code> gibi + b철l체m y철nergelerinin i챌inde de yer alabilece휓ini unutmay캇n. Bu gibi + durumlarda DNS sorgular캇 sadece istek kuralla e힊le힊ti휓i takdirde + yap캇lacakt캇r. A힊a휓캇daki 철rnekte <code>.html</code> ve + <code>.cgi</code> dosyalar캇na yap캇lan istekler hari챌 DNS sorgular캇 + iptal edilmektedir:</p> + + <div class="example"><p><code> + HostnameLookups off<br /> + <Files ~ "\.(html|cgi)$"><br /> + <span class="indent"> + HostnameLookups on<br /> + </span> + </Files> + </code></p></div> + + <p>Yine de baz캇 CGI��셪erin DNS isimlerine ihtiyac캇 olursa bu CGI��셪erin + bu ihtiya챌lar캇na y철nelik olarak <code>gethostbyname</code> 챌a휓r캇lar캇 + yapabilece휓ini g철zard캇 etmeyiniz.</p> + + + + <h3><a name="symlinks" id="symlinks"><code>FollowSymLinks</code> ve + <code>SymLinksIfOwnerMatch</code></a></h3> + + + + <p>URL uzay캇n캇zda ge챌erli olmak 체zere bir <code>Options + FollowSymLinks</code> yoksa veya <code>Options + SymLinksIfOwnerMatch</code> y철nergeleri varsa, Apache her sembolik + ba휓캇n 체zerinde baz캇 s캇namalar yapmak i챌in ek bir sistem 챌a휓r캇s캇ndan + ba힊ka istenen her dosya i챌in de ayr캇 bir 챌a휓r캇 yapacakt캇r.</p> + + <div class="example"><h3>횜rnek:</h3><p><code> + DocumentRoot /siteler/htdocs<br /> + <Directory /><br /> + <span class="indent"> + Options SymLinksIfOwnerMatch<br /> + </span> + </Directory> + </code></p></div> + + <p>Bu durumda <code>/index.html</code> i챌in bir istek yap캇ld캇휓캇nda + Apache, <code>/siteler</code>, <code>/siteler/htdocs</code> ve<br /> + <code>/siteler/htdocs/index.html</code> 체zerinde + <code>lstat</code>(2) 챌a휓r캇lar캇 yapacakt캇r. <code>lstat</code> + sonu챌lar캇 철nbelle휓e kaydedilmedi휓inden bu i힊lem her istekte + yinelenecektir. Amac캇n캇z ger챌ekten sembolik ba휓lar캇 g체venlik + a챌캇s캇ndan s캇namaksa bunu 힊철yle yapabilirsiniz:</p> + + <div class="example"><p><code> + DocumentRoot /siteler/htdocs<br /> + <Directory /><br /> + <span class="indent"> + Options FollowSymLinks<br /> + </span> + </Directory><br /> + <br /> + <Directory /sitem/htdocs><br /> + <span class="indent"> + Options -FollowSymLinks +SymLinksIfOwnerMatch<br /> + </span> + </Directory> + </code></p></div> + + <p>B철ylece <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> alt캇ndaki + dosyalar i챌in fazladan bir 챌a휓r캇 yap캇lmas캇n캇 engellemi힊 olursunuz. + E휓er baz캇 b철l체mlerde <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> gibi y철nergeler 체zerinden belge k철k + dizininizin d캇힊캇nda kalan dosya yollar캇na sahipseniz benzer + i힊lemleri onlar i챌in de yapmal캇s캇n캇z. Sembolik ba휓 korumas캇 yapmamak + suretiyle ba힊ar캇m캇 artt캇rmak isterseniz, <code>FollowSymLinks</code> + se챌ene휓ini her yerde etkin k캇l캇n ve + <code>SymLinksIfOwnerMatch</code> se챌ene휓ini asla + etkinle힊tirmeyin.</p> + + + + <h3><a name="htacess" id="htacess"><code>AllowOverride</code></a></h3> + + + + <p>Genellikle <code>.htaccess</code> dosyalar캇 체zerinden yap캇ld캇휓캇 + gibi URL uzay캇n캇zda ge챌ersizle힊tirmelere izin veriyorsan캇z, Apache + her dosya bile힊eni i챌in bu <code>.htaccess</code> dosyalar캇n캇 a챌maya + 챌al캇힊acakt캇r.</p> + + <div class="example"><h3>횜rnek:</h3><p><code> + DocumentRoot /siteler/htdocs<br /> + <Directory /><br /> + <span class="indent"> + AllowOverride all<br /> + </span> + </Directory> + </code></p></div> + + <p>Bu durumda <code>/index.html</code> sayfas캇na yap캇lan bir istek i챌in + Apache, <code>/.htaccess</code>, <code>/siteler/.htaccess</code> ve + <code>/siteler/htdocs/.htaccess</code> dosyalar캇n캇 a챌maya + 챌al캇힊acakt캇r. 횉철z체m <code>Options FollowSymLinks</code> durumunun + benzeridir; ba힊ar캇m캇 artt캇rmak i챌in dosya sisteminizin her yerinde + <code>AllowOverride None</code> olsun.</p> + + + + <h3><a name="negotiation" id="negotiation">Dil Uzla힊캇m캇</a></h3> + + + + <p>Ba힊ar캇m캇 son k캇r캇nt캇s캇na kadar artt캇rmak istiyorsan캇z, m체mk체nse + i챌erik dili uzla힊캇m캇 da yapmay캇n. Dil uzla힊캇m캇ndan yararlanmak + isterken b체y체k ba힊ar캇m kay캇plar캇na u휓rayabilirsiniz. B철yle bir + durumda sunucunun ba힊ar캇m캇n캇 artt캇rman캇n tek bir yolu vard캇r. </p> + + <div class="example"><p><code> + DirectoryIndex index + </code></p></div> + + <p>Yukar캇daki gibi bir dosya ismi kal캇b캇 kullanmak yerine, a힊a휓캇daki + gibi se챌enekleri tam bir liste halinde belirtin:</p> + + <div class="example"><p><code> + DirectoryIndex index.cgi index.pl index.shtml index.html + </code></p></div> + + <p>Buradaki s캇ralama 철ncelik s캇ras캇n캇 belirler; yani, + 철ncelikli olmas캇n캇 istedi휓iniz se챌ene휓i listenin ba힊캇na + yazmal캇s캇n캇z.</p> + + <p>캅stenen dosya i챌in <code>MultiViews</code> kullanarak dizini + taratmak yerine, gerekli bilgiyi tek bir dosyadan okutmak suretiyle + ba힊ar캇m캇 artt캇rabilirsiniz. Bu ama챌la t체re힊lem + (<code>type-map</code>) dosyalar캇 kullanman캇z yeterli olacakt캇r.</p> + + <p>Sitenizde i챌erik dili uzla힊캇m캇na gerek varsa, bunu <code>Options + MultiViews</code> y철nergesi 체zerinden de휓il, t체re힊lem dosyalar캇 + kullanarak yapmay캇 deneyin. 캅챌erik dili uzla힊캇m캇 ve t체re힊lem + dosyalar캇n캇n olu힊turulmas캇 hakk캇nda daha ayr캇nt캇l캇 bilgi edinmek + i챌in <a href="../content-negotiation.html">캅챌erik Uzla힊캇m캇</a> + belgesine bak캇n캇z.</p> + + + + <h3>Bellek E힊lemleri</h3> + + + + <p>Apache��셬in SSI sayfalar캇nda oldu휓u gibi teslim edilecek dosyan캇n + i챌eri휓ine bakma gere휓i duydu휓u durumlarda, e휓er i힊letim sistemi + <code>mmap</code>(2) ve benzerlerini destekliyorsa 챌ekirdek normal + olarak dosyay캇 belle휓e kopyalayacakt캇r.</p> + + <p>Baz캇 platformlarda bu belle휓e e힊leme i힊lemi ba힊ar캇m캇 artt캇rsa da + ba힊ar캇m캇n veya httpd kararl캇l캇휓캇n캇n zora girdi휓i durumlar + olabilmektedir:</p> + + <ul> + <li> + <p>Baz캇 i힊letim sistemlerinde i힊lemci say캇s캇 art캇힊캇na ba휓l캇 + olarak, <code>mmap</code> i힊levi <code>read</code>(2) kadar iyi + 철l챌eklenmemi힊tir. 횜rne휓in, 챌ok i힊lemcili Solaris sunucularda + <code>mmap</code> iptal edildi휓i takdirde i챌eri휓i sunucu + taraf캇ndan i힊lenen dosyalar 체zerinde bazen daha h캇zl캇 i힊lem + yap캇labilmektedir.</p> + </li> + + <li> + <p>Belle휓e kopyalanacak dosya NFS 체zerinden ba휓lanan bir dosya + sistemindeyse ve dosya ba힊ka bir NFS istemcisi makine taraf캇ndan + silinmi힊 veya dosyan캇n boyutu de휓i힊tirilmi힊se sunucunuz dosyaya + tekrar eri힊meye 챌al캇힊t캇휓캇nda bir hata alabilecektir.</p> + </li> + </ul> + + <p>B철yle durumlar캇n olas캇l캇k dahilinde oldu휓u kurulumlarda i챌eri휓i + sunucu taraf캇ndan i힊lenecek dosyalar캇n belle휓e kopyalanmamas캇 i챌in + yap캇land캇rman캇za <code>EnableMMAP off</code> sat캇r캇n캇 ekleyiniz. + (Dikkat: Bu y철nerge dizin seviyesinde ge챌ersizle힊tirilebilen + y철nergelerdendir.)</p> + + + + <h3><code>sendfile</code></h3> + + + + <p>Apache��셬in duruk dosyalarda oldu휓u gibi teslim edilecek dosyan캇n + i챌eri휓ine bakmad캇휓캇 durumlarda, e휓er i힊letim sistemi + <code>sendfile</code>(2) deste휓ine sahipse 챌ekirdek normal olarak bu + deste휓i kullanacakt캇r.</p> + + <p>Baz캇 platformlarda <code>sendfile</code> kullan캇m캇, okuma ve yazma + i힊lemlerinin ayr캇 ayr캇 yap캇lmamas캇n캇 sa휓lasa da + <code>sendfile</code> kullan캇m캇n캇n httpd kararl캇l캇휓캇n캇 bozdu휓u baz캇 + durumlar s철zkonusudur:</p> + + <ul> + <li> + <p>Baz캇 platformlar derleme sisteminin saptayamad캇휓캇 bozuk bir + <code>sendfile</code> deste휓ine sahip olabilir. 횜zellikle + derleme i힊leminin ba힊ka bir platformda yap캇l캇p + <code>sendfile</code> deste휓i bozuk bir makineye kurulum + yap캇ld캇휓캇 durumlarda bu deste휓in bozuk oldu휓u + saptanamayacakt캇r.</p> + </li> + <li> + <p>횉ekirdek, NFS 체zerinden eri힊ilen a휓 dosyalar캇n캇 kendi 철nbelle휓i + 체zerinden gerekti휓i gibi sunamayabilir.</p> + </li> + </ul> + + <p>B철yle durumlar캇n olas캇l캇k dahilinde oldu휓u kurulumlarda i챌eri휓in + <code>sendfile</code> deste휓iyle teslim edilmemesi i챌in + yap캇land캇rman캇za <code>EnableSendfile off</code> sat캇r캇n캇 ekleyiniz. + (Dikkat: Bu y철nerge dizin seviyesinde ge챌ersizle힊tirilebilen + y철nergelerdendir.)</p> + + + + <h3><a name="process" id="process">S체re챌 Olu힊turma</a></h3> + + + + <p>Apache 1.3 철ncesinde <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code>, <code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code> ve <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> ayarlar캇, ba힊ka sunucularla k캇yaslama + denemelerinde ola휓an체st체 k철t체 sonu챌lar al캇nmas캇na sebep olmaktayd캇. + 횜zellikle uygulanan y체k체 kar힊캇lamaya yetecek say캇da 챌ocuk s체re챌 + olu힊turulmas캇 a힊amas캇nda Apache��셬in elde etti휓i ivme bunlardan + biriydi. Ba힊lang캇챌ta <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> y철nergesiyle belli say캇da s체re챌 + olu힊turulduktan sonra her saniyede bir tane olmak 체zere <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code> say캇da 챌ocuk s체re챌 + olu힊turulmaktayd캇. 횜rne휓in, ayn캇 anda 100 iste휓e yan캇t vermek i챌in + <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> + y철nergesinin 철ntan캇ml캇 de휓eri olarak ba힊ta <code>5</code> s체re챌 + olu힊turuldu휓undan kalan s체re챌ler i챌in 95 saniye ge챌mesi gerekirdi. + S캇k s캇k yeniden ba힊lat캇lmad캇klar캇ndan dolay캇 ger챌ek hayatta + sunucular캇n ba힊캇na gelen de buydu. Ba힊ka sunucularla k캇yaslama + denemelerinde ise i힊lem sadece on dakika s체rmekte ve i챌ler ac캇s캇 + sonu챌lar al캇nmaktayd캇.</p> + + <p>Saniyede bir kural캇, sunucunun yeni 챌ocuklar캇 olu힊turmas캇 s캇ras캇nda + sistemin a힊캇r캇 me힊gul duruma d체힊memesi i챌in al캇nm캇힊 bir 철nlemdi. + Makine 챌ocuk s체re챌 olu힊turmakla me힊gul edildi휓i s체rece isteklere + yan캇t veremeyecektir. B철ylesi bir durum Apache��셬in ba힊ar캇m캇n캇 + k철t체le힊tirmekten ba힊ka i힊e yaramayacakt캇r. Apache 1.3��셳e saniyede + bir kural캇 biraz esnetildi. Yeni ger챌eklenimde art캇k bir s체re챌 + olu힊turduktan bir saniye sonra iki s체re챌, bir saniye sonra d철rt + s체re챌 olu힊turulmakta ve i힊lem, saniyede 32 챌ocuk s체re챌 olu힊turulur + duruma gelene kadar b철yle ivmelenmektedir. 횉ocuk s체re챌 olu힊turma + i힊lemi <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code> + de휓erine ula힊캇l캇nca durmaktad캇r.</p> + + <p>Bu, <code class="directive"><a href="../mod/prefork.html#minspareservers">MinSpareServers</a></code>, + <code class="directive"><a href="../mod/prefork.html#maxspareservers">MaxSpareServers</a></code> ve + <code class="directive"><a href="../mod/mpm_common.html#startservers">StartServers</a></code> ayarlar캇yla + oynamay캇 neredeyse gereksiz k캇lacak kadar iyi sonu챌lar verecek gibi + g철r체nmektedir. Saniyede 4 챌ocuktan fazlas캇 olu힊turulmaya + ba힊land캇휓캇nda hata g체nl체휓체ne baz캇 iletiler d체힊meye ba힊lar. Bu + iletilerin say캇s캇 챌ok artarsa bu ayarlarla oynama vakti gelmi힊 + demektir. Bunun i챌in <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> 챌캇kt캇s캇n캇 bir + k캇lavuz olarak kullanabilirsiniz.</p> + + <p>S체re챌 olu힊turmayla ilgili olarak s체re챌 철l체m체 <code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> de휓eri ile + sa휓lan캇r. Bu de휓er 철ntan캇ml캇 olarak <code>0</code> olup, 챌ocuk s체re챌 + ba힊캇na istek say캇s캇n캇n s캇n캇rs캇z oldu휓u anlam캇na gelir. E휓er + yap캇land캇rman캇zda bu de휓eri <code>30</code> gibi 챌ok d체힊체k bir + de휓ere ayarlarsan캇z bunu hemen kald캇rmak zorunda kalabilirsiniz. + Sunucunuzu SunOS veya Solaris��셢n eski bir s체r체m체 체zerinde + 챌al캇힊t캇r캇yorsan캇z bellek ka챌aklar캇na sebep olmamak i챌in bu de휓eri + <code>10000</code> ile s캇n캇rlay캇n캇z.</p> + + <p>Kal캇c캇 ba휓lant캇 철zelli휓ini kullan캇yorsan캇z, 챌ocuk s체re챌ler zaten + a챌캇k ba휓lant캇lardan istek beklemekte olacaklard캇r. <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code> y철nergesinin 철ntan캇ml캇 + de휓eri <code>15</code> saniye olup bu etkiyi en aza indirmeye y철nelik + s체redir. Burada a휓 band geni힊li휓i ile sunucu kaynaklar캇n캇n kullan캇m캇 + aras캇nda bir se챌im yapmak s철z konusudur. Hi챌bir 힊ey umurunuzda + de휓ilse <a href="http://www.research.digital.com/wrl/techreports/abstracts/95.4.html"> + 챌o휓u ayr캇cal캇휓캇n yitirilmesi pahas캇na</a> bu de휓eri rahat챌a + <code>60</code> saniyenin 체zerine 챌캇karabilirsiniz.</p> + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="compiletime" id="compiletime">Derleme S캇ras캇nda Yap캇land캇rma ile 캅lgili Konular</a></h2> + + + <h3>MPM Se챌imi</h3> + + + <p>Apache 2.x, <a href="../mpm.html">횉ok S체re챌lilik Mod체lleri</a> + (MPM) ad캇 verilen eklemlenebilir 챌ok g철revlilik modellerini + destekler. Apache��셺i derlerken bu MPM��셪erden birini se챌meniz + gerekir. MPM��셪erden baz캇lar캇 platformlara 철zeldir: + <code class="module"><a href="../mod/beos.html">beos</a></code>, <code class="module"><a href="../mod/mpm_netware.html">mpm_netware</a></code>, + <code class="module"><a href="../mod/mpmt_os2.html">mpmt_os2</a></code> ve <code class="module"><a href="../mod/mpm_winnt.html">mpm_winnt</a></code>. Unix + benzeri sistemler i챌in ise se챌ebilece휓iniz mod체l say캇s캇 birden + fazlad캇r. MPM se챌iminin httpd��셬in h캇z캇nda ve 철l챌eklenebilirli휓inde + baz캇 etkileri olabilir:</p> + + <ul> + + <li><code class="module"><a href="../mod/worker.html">worker</a></code> mod체l체 her biri 챌ok evreli 챌ok say캇da + 챌ocuk s체re챌 kullan캇m캇n캇 destekler. Her evre ayn캇 anda tek bir + ba휓lant캇ya hizmet sunar. Ayn캇 hizmeti daha az bellek harcayarak + vermesi nedeniyle y체ksek trafi휓e sahip sunucularda + <code class="module"><a href="../mod/prefork.html">prefork</a></code> mod체l체ne g철re daha iyi bir se챌imdir.</li> + + <li><code class="module"><a href="../mod/prefork.html">prefork</a></code> mod체l체 her biri tek bir evreye sahip + 챌ok say캇da 챌ocuk s체re챌 kullan캇m캇n캇 destekler. Her s체re챌 ayn캇 anda + tek bir ba휓lant캇ya hizmet sunar. 횉o휓u sistemde daha h캇zl캇 olmas캇 + nedeniyle <code class="module"><a href="../mod/worker.html">worker</a></code> mod체l체ne g철re daha iyi bir se챌im + olarak g철r체n체rse de bunu daha fazla bellek kullanarak sa휓lar. + <code class="module"><a href="../mod/prefork.html">prefork</a></code> mod체l체n체n evresiz tasar캇m캇n캇n + <code class="module"><a href="../mod/worker.html">worker</a></code> mod체l체ne g철re baz캇 yararl캇 taraflar캇 + vard캇r: 횉ok evreli sistemlerde g체venilir olmayan 체챌체nc체 parti + mod체lleri kullanabilir ve evrelerde hata ay캇klaman캇n yetersiz + kald캇휓캇 platformlarda hatalar캇n캇 ay캇klamak daha kolayd캇r.</li> + + </ul> + + <p>Bu mod체ller ve di휓erleri hakk캇nda daha ayr캇nt캇l캇 bilgi edinmek i챌in + <a href="../mpm.html">횉ok S체re챌lilik Mod체lleri</a> belgesine + bak캇n캇z.</p> + + + + <h3><a name="modules" id="modules">Mod체ller</a></h3> + + + + <p>Bellek kullan캇m캇 ba힊ar캇m konusunda 철nemli oldu휓undan ger챌ekte + kullanmad캇휓캇n캇z mod체lleri elemeye 챌al캇힊mal캇s캇n캇z. Mod체lleri birer <a href="../dso.html">DSO</a> olarak derlediyseniz <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> y철nergesinin bulundu휓u sat캇r캇 + a챌캇klama haline getirmeniz mod체lden kurtulman캇z i챌in yeterli + olacakt캇r. Mod체lleri bu 힊ekilde kald캇rarak onlar캇n yoklu휓unda + sitenizin hala i힊levlerini yerine getirdi휓ini g철rme 힊ans캇na da + kavu힊mu힊 olursunuz.</p> + + <p>Ancak, e휓er mod체lleri Apache 챌al캇힊t캇r캇labilirinin i챌ine + g철mm체힊seniz istenmeyen mod체lleri kald캇rmak i챌in Apache'yi yeniden + derlemeniz gerekir.</p> + + <p>Bu noktada bir soru akla gelebilir: Hangi mod체ller gerekli, + hangileri de휓il? Bu sorunun yan캇t캇 힊체phesiz siteden siteye de휓i힊ir. + Ancak, olmazsa olmaz mo체ller olarak <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code>, + <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> ve <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code> + mod체llerini sayabiliriz. Bunlardan <code>mod_log_config</code> + olmadan da bir sitenin 챌al캇힊abilece휓inden hareketle bu mod체l체n + varl캇휓캇 iste휓e ba휓l캇 olsa da bu mod체l체 kald캇rman캇z캇 철nermiyoruz.</p> + + + + <h3>Atomik 캅힊lemler</h3> + + + + <p>Worker MPM'nin en son geli힊tirme s체r체mleri ve + <code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code> gibi baz캇 mod체ller APR'nin atomik API'sini + kullan캇rlar. Bu API, d체힊체k ayarl캇 evre e힊zamanlamas캇nda atomik + i힊lemler yapar.</p> + + <p>횜ntan캇ml캇 olarak, APR bu i힊lemleri hedef i힊letim sistemi/i힊lemci + platformunda kullan캇labilecek en verimli mekanizmay캇 kullanarak + ger챌ekle힊tirir. G체n체m체z i힊lemcilerinin 챌o휓u, 철rne휓in, bir atomik + kar힊캇la힊t캇rma ve takas (CAS) i힊lemini donan캇mda ger챌ekle힊tirmektedir. + Baz캇 platformlarda APR'nin atomik i힊lemler i챌in 철ntan캇ml캇 olarak daha + yava힊 olan mutekslere dayal캇 ger챌eklenimi kullanmas캇n캇n sebebi eski + i힊lemcilerde bu t체r makine kodlar캇n캇n yoklu휓udur. Apache'yi bu t체r + platformalarda g체n체m체z i힊lemcileriyde 챌al캇힊t캇rmay캇 d체힊체n체yorsan캇z + Apache'yi derlemek i챌in yap캇land캇r캇rken en h캇zl캇 atomik i힊lemin + se챌ilebilmesi i챌in <code>--enable-nonportable-atomics</code> + se챌ene휓ini kullan캇n:</p> + + <div class="example"><p><code> + ./buildconf<br /> + ./configure --with-mpm=worker --enable-nonportable-atomics=yes + </code></p></div> + + <p><code>--enable-nonportable-atomics</code> se챌ene휓i 힊u platformlar + i챌in uygundur:</p> + + <ul> + + <li>SPARC 체zerinde Solaris<br /> + APR 철ntan캇ml캇 olarak, SPARC/Solaris 체zerinde mutekslere dayal캇 + atomik i힊lemleri kullan캇r. Ancak, + <code>--enable-nonportable-atomics</code> yap캇land캇rmas캇n캇 + kullan캇rsan캇z, donan캇m 체zerinde h캇zl캇 kar힊캇la힊t캇rma ve takas + i챌in uygun SPARC v8plus kodunu kullanacak 힊ekilde kod 체retilir. + Apache'yi bu se챌enekle yap캇land캇r캇rsan캇z atomik i힊lemler daha + verimli olacak fakat derlenen Apache 챌al캇힊t캇r캇labiliri sadece + UltraSPARC k캇rm캇휓캇 체zerinde 챌al캇힊acakt캇r. + </li> + + <li>x86 체zerinde Linux<br /> + APR 철ntan캇ml캇 olarak, Linux 체zerinde mutekslere dayal캇 atomik + i힊lemleri kullan캇r. Ancak, + <code>--enable-nonportable-atomics</code> yap캇land캇rmas캇n캇 + kullan캇rsan캇z, donan캇m 체zerinde h캇zl캇 kar힊캇la힊t캇rma ve takas + i챌in uygun 486 kodunu kullanacak 힊ekilde kod 체retilir. Apache'yi + bu se챌enekle yap캇land캇r캇rsan캇z atomik i힊lemler daha verimli + olacak fakat derlenen Apache 챌al캇힊t캇r캇labiliri (386 체zerinde + de휓il) sadece 486 ve sonras캇 k캇rm캇klarda 챌al캇힊acakt캇r. + </li> + + </ul> + + + + <h3><code>mod_status</code> ve <code>ExtendedStatus On</code> + </h3> + + + + <p><code class="module"><a href="../mod/mod_status.html">mod_status</a></code> mod체l체n체 derlemi힊 ve Apache'yi + yap캇land캇r캇r ve 챌al캇힊t캇r캇rken <code>ExtendedStatus On</code> sat캇r캇n캇 + da kullanm캇힊san캇z Apache her istek 체zerinde + <code>gettimeofday(2)</code> (veya i힊letim sistemine ba휓l캇 olarak + <code>time(2)</code>) 챌a휓r캇s캇ndan ba힊ka (1.3 철ncesinde) fazladan + defalarca <code>time(2)</code> 챌a휓r캇lar캇 yapacakt캇r. Bu 챌a휓r캇larla + durum raporununun zamanlama bilgilerini i챌ermesi sa휓lan캇r. Ba힊ar캇m캇 + artt캇rmak i챌in <code>ExtendedStatus off</code> yap캇n (zaten 철ntan캇ml캇 + b철yledir).</p> + + + + <h3><code>accept</code> dizgilemesi ve 챌ok soketli i힊lem</h3> + + + + <div class="warning"><h3>Uyar캇:</h3> + <p>Bu b철l체m, Apache HTTP sunucusunun 2.x s체r체mlerinde yap캇lan + de휓i힊ikliklere g철re tamamen g체ncellenmemi힊tir. Baz캇 bilgiler hala + ge챌erliyse de l체tfen dikkatli kullan캇n캇z.</p> + </div> + + <p>Burada Unix soket aray체z체 ger챌eklenirken ihmal edilen bir durumdan + bahsedece휓iz. HTTP sunucunuzun 챌ok say캇da adresten 챌ok say캇da portu + dinlemek i챌in 챌ok say캇da <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> y철nergesi kullanmakta oldu휓unu varsayal캇m. Her + soketi 챌al캇힊t캇휓캇n캇 g철rmek i챌in denerken Apache ba휓lant캇 i챌in + <code>select(2)</code> kullanacakt캇r. <code>select(2)</code> 챌a휓r캇s캇 + bu soketin 체zerinde <em>s캇f캇r</em> veya <em>en az캇ndan bir</em> + ba휓lant캇n캇n beklemekte oldu휓u anlam캇na gelir. Apache'nin modeli 챌ok + say캇da 챌ocuk s체re챌 i챌erir ve bo힊ta olanlar캇n t체m체nde ayn캇 anda yeni + ba휓lant캇lar denenebilir. Ger챌ekte 챌al캇힊an kod bu olmasa da meram캇m캇z캇 + anlatmak i챌in kodun 힊철yle bir 힊ey oldu휓unu varsayabiliriz:</p> + + <div class="example"><p><code> + for (;;) {<br /> + <span class="indent"> + for (;;) {<br /> + <span class="indent"> + fd_set accept_fds;<br /> + <br /> + FD_ZERO (&accept_fds);<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + FD_SET (i, &accept_fds);<br /> + </span> + }<br /> + rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);<br /> + if (rc < 1) continue;<br /> + new_connection = -1;<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + if (FD_ISSET (i, &accept_fds)) {<br /> + <span class="indent"> + new_connection = accept (i, NULL, NULL);<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + </span> + }<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + process the new_connection;<br /> + </span> + } + </code></p></div> + + <p>Bu 철zet ger챌eklenim bir tak캇m a챌l캇k sorunlar캇na sebep olur. Bu + d철ng체n체n 챌al캇힊mas캇 s캇ras캇nda ayn캇 anda 챌ok say캇da 챌ocuk s체re챌 yeniden + 챌a휓r캇l캇r ve istekler aras캇nda kalan 챌o휓u 챌ocuk da <code>select</code> + ile engellenir. Engellenen t체m bu 챌ocuklar soketlerden herhangi biri + 체zerinde tek bir istek g철r체nd체휓체nde <code>select</code> taraf캇ndan + uyand캇r캇l캇p i힊leme sokulmak 체zere d철nd체r체l체rler (uyand캇r캇lan 챌ocuk + say캇s캇 i힊letim sistemine ve zamanlama ayarlar캇na g철re de휓i힊iklik + g철sterir). Bunlar캇n hepsi d철ng체ye kat캇l캇p ba휓lant캇 kabul etmeye + (<code>accept</code>) 챌al캇힊캇rlar. Fakat i챌lerinden yaln캇z biri + (sadece bir ba휓lant캇 iste휓inin mevcut oldu휓u varsay캇m캇yla) bunu + ba힊arabilir. Kalan캇n캇n ba휓lant캇 kabul etmesi (<code>accept</code>) + engellenir. Bu durum, bu 챌ocuklar캇 istekleri ba힊ka ba힊ka soketlerden + de휓il mecburen tek bir soketten kabul etmeye kilitler ve bu soket + 체zerinde yeni bir istek belirip uyand캇r캇lana kadar bu durumda + kal캇rlar. Bu a챌l캇k sorunu ilk olarak <a href="http://bugs.apache.org/index/full/467">PR#467</a> say캇l캇 raporla + belgelenmi힊tir. Bu sorunun en az iki 챌철z체m체 vard캇r.</p> + + <p>횉철z체m체n biri engellenmeyen soket kullan캇m캇d캇r. Bu durumda + <code>accept</code> 챌ocuklar캇 engellemeyecek ve yap캇lan bir + ba휓lant캇n캇n ard캇ndan di휓er 챌ocuklar durumlar캇 de휓i힊meksizin ba휓lant캇 + beklemeye devam edeceklerdir. Fakat bu durum i힊lemci zaman캇n캇n bo힊a + harcanmas캇na sebep olur. Se챌ilmi힊 (<code>select</code>) bo힊ta on + 챌ocu휓un oldu휓unu ve bir ba휓lant캇 geldi휓ini varsayal캇m. Kalan dokuz + 챌ocuk i힊ine devam edip ba휓lant캇 kabul etmeyi (<code>accept</code>) + deneyecek, ba힊ar캇zs캇z olacak, d철necek ba힊a, tekrar se챌ilecek + (<code>select</code>) ve b철yle hi챌bir i힊 yapmadan d철n체p duracakt캇r. Bu + arada hizmet sunmakta olanlar da i힊lerini bitirdikten sonra bu + d철ng체deki yerlerini alacaklard캇r. Ayn캇 kutunun i챌inde bo힊ta bir s체r체 + i힊lemciniz (챌ok i힊lemcili sistemler) yoksa bu 챌철z체m pek verimli + olmayacakt캇r.</p> + + <p>Di휓er 챌철z체m ise Apache taraf캇ndan kullan캇lan 챌철z체m olup, girdiyi + bir i챌 d철ng체de s캇raya sokmakt캇r. D철ng체 a힊a휓캇da 철rneklenmi힊tir (farklar + vurgulanm캇힊t캇r):</p> + + <div class="example"><p><code> + for (;;) {<br /> + <span class="indent"> + <strong>accept_mutex_on ();</strong><br /> + for (;;) {<br /> + <span class="indent"> + fd_set accept_fds;<br /> + <br /> + FD_ZERO (&accept_fds);<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + FD_SET (i, &accept_fds);<br /> + </span> + }<br /> + rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);<br /> + if (rc < 1) continue;<br /> + new_connection = -1;<br /> + for (i = first_socket; i <= last_socket; ++i) {<br /> + <span class="indent"> + if (FD_ISSET (i, &accept_fds)) {<br /> + <span class="indent"> + new_connection = accept (i, NULL, NULL);<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + </span> + }<br /> + if (new_connection != -1) break;<br /> + </span> + }<br /> + <strong>accept_mutex_off ();</strong><br /> + process the new_connection;<br /> + </span> + } + </code></p></div> + + <p><code>accept_mutex_on</code> ve <code>accept_mutex_off</code> <a id="serialize" name="serialize">i힊levleri</a> bir kar힊캇l캇kl캇 red + semoforu olu힊tururlar. Mutekse ayn캇 anda sadece bir 챌ocuk sahip + olabilir. Bu muteksleri ger챌eklemek i챌in 챌e힊itli se챌enekler vard캇r. + Se챌im, <code>src/conf.h</code> (1.3 철ncesi) veya + <code>src/include/ap_config.h</code> (1.3 ve sonras캇) dosyas캇nda + tan캇mlanm캇힊t캇r. Baz캇 mimariler bir kilitleme se챌ene휓ine sahip + de휓ildir. B철yle mimarilerde 챌ok say캇da <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> y철nergesi kullanmak g체venilir + olmayacakt캇r.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#acceptmutex">AcceptMutex</a></code> y철nergesi, + se챌ilen muteks ger챌eklenimini 챌al캇힊ma an캇nda de휓i힊tirmek i챌in + kullan캇labilir.</p> + + <dl> + <dt><code>AcceptMutex flock</code></dt> + + <dd> + <p>Bu y철ntem, bir kilit dosyas캇n캇 kilitlemek i챌in + <code>flock(2)</code> sistem 챌a휓r캇s캇n캇 kullan캇r (Kilit dosyas캇n캇n + yeri <code class="directive"><a href="../mod/mpm_common.html#lockfile">LockFile</a></code> + y철nergesiyle belirtilir).</p> + </dd> + + <dt><code>AcceptMutex fcntl</code></dt> + + <dd> + <p>Bu y철ntem, bir kilit dosyas캇n캇 kilitlemek i챌in + <code>fcntl(2)</code> sistem 챌a휓r캇s캇n캇 kullan캇r (Kilit dosyas캇n캇n + yeri <code class="directive"><a href="../mod/mpm_common.html#lockfile">LockFile</a></code> + y철nergesiyle belirtilir).</p> + </dd> + + <dt><code>AcceptMutex sysvsem</code></dt> + + <dd> + <p>(1.3 ve sonras캇) Bu y철ntem muteksi ger챌eklemek i챌in SysV tarz캇 + semaforlar캇 kullan캇r. Maalesef, SysV tarz캇 semaforlar캇n baz캇 yan + etkileri vard캇r. Bunlardan biri Apache'nin semaforu temizlemeden + 철lme ihtimalidir (<code>ipcs(8)</code> k캇lavuz sayfas캇na bak캇n캇z). + Di휓er biri, CGI'lerin sunucu ile ayn캇 kullan캇c캇 kimli휓ini + kullanmalar캇 nedeniyle semafor aray체z체n체n hizmet reddi + sald캇r캇lar캇na a챌캇k olmas캇d캇r (<code class="program"><a href="../programs/suexec.html">suexec</a></code> veya + <code>cgiwrapper</code> gibi bir 힊eyler kullanmad캇k챌a b체t체n + CGI'ler i챌in s철z konusudur). Bu sebeple bu y철ntem IRIX haricinde + hi챌bir mimaride kullan캇lmaz (철nceki ikisi 챌o휓u IRIX makine i챌in + elde edilmesi imkans캇z derecede pahal캇 oldu휓undan).</p> + </dd> + + <dt><code>AcceptMutex pthread</code></dt> + + <dd> + <p>(1.3 ve sonras캇) Bu y철ntem POSIX mutekslerini kullan캇r ve POSIX + evreleri belirtiminin tamamen ger챌eklendi휓i mimarilerde 챌al캇힊mas캇 + gerekirse de sadece Solaris (2.5 ve sonras캇) 체zerinde ve sadece + belli yap캇land캇rmalarla 챌al캇힊makta gibi g철r체nmektedir. Bunu + denemi힊seniz sunucunuzun 챌철kt체휓체n체 ve yan캇t vermedi휓ini + g철rm체힊s체n체zd체r. Sadece duruk i챌erikli sunucular iyi + 챌al캇힊maktad캇r.</p> + </dd> + + <dt><code>AcceptMutex posixsem</code></dt> + + <dd> + <p>(2.0 ve sonras캇) Bu y철ntem POSIX semaforlar캇n캇 kullan캇r. E휓er + i힊lem s캇ras캇nda bir evre muteks kaynakl캇 par챌alama ar캇zalar캇yla + kar힊캇 kar힊캇ya kal캇rsa HTTP sunucusunun 챌철kmesiyle semaforun sahibi + kurtar캇lamaz.</p> + </dd> + + </dl> + + <p>E휓er sisteminiz yukar캇da bahsedilenler d캇힊캇nda ba힊ka bir dizgileme + y철ntemi kullan캇yorsa bununla ilgili kodun APR'ye eklenmesi girilen + zahmete de휓ecektir.</p> + + <p>Ba힊ka bir 챌철z체m daha vard캇r ancak d철ng체 k캇smen dizgilenmeyece휓inden + (yani belli say캇da s체rece izin verilemeyece휓inden) asla + ger챌eklenmemi힊tir. Bu sadece, ayn캇 anda 챌ok say캇da 챌ocuk s체recin + 챌al캇힊abilece휓i ve dolay캇s캇yla band geni힊li휓inin t체m y철nleriyle + kullan캇labilece휓i 챌ok i힊lemcili sistemlerde ilgin챌 olabilirdi. Bu + gelecekte incelenmeye de휓er bir konu olmakla beraber 챌ok say캇da HTTP + sunucusunun ayn캇 anda ayn캇 amaca hizmet edecek 힊ekilde 챌al캇힊mas캇 + standart olarak pek m체mk체n g철r체lmedi휓inden bu olas캇l캇k 챌ok + d체힊체kt체r.</p> + + <p>En y체ksek ba힊ar캇m캇 elde etmek i챌in ideal olan캇 sunucular캇 + 챌al캇힊t캇r캇rken 챌ok say캇da <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> y철nergesi kullanmamakt캇r. Fakat siz yine de + okumaya devam edin.</p> + + + + <h3><code>accept</code> dizgilemesi - tek soket</h3> + + + + <p>횉ok soketli sunucular i챌in yukar캇da a챌캇klananlar iyi g체zel de tek + soketli sunucularda durum ne? Kuramsal olarak, bunlar캇n hi챌biriyle bir + sorunlar캇 olmamas캇 gerekir. 횉체nk체 yeni bir ba휓lant캇 gelene kadar t체m + 챌ocuklar <code>accept(2)</code> ile engellenirler dolay캇s캇yla hi챌bir + a챌l캇k sorununun ortaya 챌캇kmamas캇 gerekir. Uygulamada ise son + kullan캇c캇dan gizli olarak, yukar캇da engellenmeyen 챌ocuklar 챌철z체m체nde + bahsedilenle hemen hemen ayn캇 "bo힊a d철n체p durma" davran캇힊캇 mevcuttur. + 횉o휓u TCP y캇휓캇t캇 bu yolu ger챌eklemi힊tir. 횉ekirdek, yeni bir ba휓lant캇 + ortaya 챌캇kt캇휓캇nda <code>accept</code> ile engellenen t체m s체re챌leri + uyand캇r캇r. Bu s체re챌lerden ba휓lant캇y캇 alan kullan캇c캇 b철lgesine ge챌erken + 챌ekirdek i챌inde d철ng체de olan di휓erleri de yeni ba휓lant캇 ke힊fedilene + kadar uykular캇na geri d철nerler. Bu 챌ekirdek i챌i d철ng체, kullan캇c캇 + b철lgesindeki kodlara g철r체n체r de휓ildir ama bu olmad캇klar캇 anlam캇na + gelmez. Bu durum, 챌ok soketli engellenmeyen 챌ocuklar 챌철z체m체ndeki bo힊a + d철ng체n체n sebep oldu휓u gereksiz i힊lemci y체k체 sorununu i챌inde + bar캇nd캇r캇r.</p> + + <p>Bununla birlikte, tek soketli durumda bile bundan daha verimli bir + davran캇힊 sergileyen bir 챌ok mimari bulduk. Bu asl캇nda hemen hemen her + durumda 철ntan캇ml캇 olarak b철yledir. Linux alt캇nda yap캇lan 체st체nk철r체 + denemelerde (128MB bellekli 챌ift Pentium pro 166 i힊lemcili makinede + Linux 2.0.30) tek sokette dizgilemenin dizgilenmemi힊 duruma g철re + saniyede %3 daha az istekle sonu챌land캇휓캇 g철sterilmi힊tir. Fakat + dizgilenmemi힊 tek soket durumunda her istekte 100ms'lik ek bir gecikme + oldu휓u g철r체lm체힊t체r. Bu gecikmenin sebebi muhtemelen uzun mesafeli + hatlar olup sadece yerel a휓larda s철z konusudur. Tek soketli + dizgilemeyi ge챌ersiz k캇lmak i챌in + <code>SINGLE_LISTEN_UNSERIALIZED_ACCEPT</code> tan캇mlarsan캇z tek + soketli sunucularda art캇k dizgileme yap캇lmayacakt캇r.</p> + + + + <h3>Kapatmay캇 zamana yaymak</h3> + + + + <p><a href="http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-connection-00.txt">draft-ietf-http-connection-00.txt</a> tasla휓캇n캇n 8. b철l체m체nde + bahsedildi휓i gibi, bir HTTP sunucusunun protokol체 <strong>g체venilir + 힊ekilde</strong> ger챌eklemesi i챌in her iki y철ndeki ileti힊imi + birbirinden ba휓캇ms캇z olarak (iki y철nl체 bir TCP ba휓lant캇s캇n캇n her + yar캇s캇n캇 di휓erinden ba휓캇ms캇z olarak) kapatmas캇 gerekir. Bu olgu ba힊ka + sunucular taraf캇ndan 챌o휓unlukla dikkate al캇nmaz fakat Apache'nin 1.2 + s체r체m체nden beri gerekti휓i gibi ger챌eklenmektedir.</p> + + <p>Bu 철zellik Apache'ye eklendi휓inde Unix'in 챌e힊itli s체r체mlerinde + uzg철r체s체zl체kten dolay캇 bir tak캇m ge챌ici tela힊 sorunlar캇na sebep oldu. + TCP belirtimi <code>FIN_WAIT_2</code> durumunda bir zaman a힊캇m캇ndan + bahsetmez ama yasaklamaz da. Zaman a힊캇m캇 olmayan sistemlerde, Apache + 1.2 챌o휓u soketin sonsuza kadar <code>FIN_WAIT_2</code> durumunda + tak캇l캇p kalmas캇na sebep olur. 횉o휓u durumda, sat캇c캇dan sa휓lanan en son + TCP/IP yamalar캇n캇 uygulanarak bu 철nlenebilir. Sat캇c캇n캇n hi챌bir yeni + yama da휓캇tmad캇휓캇 durumlarda (철rne휓in, SunOS4 -- bir kaynak lisans캇 ile + insanlar bunu kendileri yamayabilirse de) bu 철zelli휓i devre d캇힊캇 + b캇rakmaya karar verdik.</p> + + <p>Bunun 체stesinden gelmenin iki yolu vard캇r. Bunlardan biri + <code>SO_LINGER</code> soket se챌ene휓idir. Bu i힊in kaderi buymu힊 gibi + g철r체n체rse de 챌o휓u TCP/IP y캇휓캇t캇nda bu gerekti휓i gibi + ger챌eklenmemi힊tir. Bu y캇휓캇tlar 체zerinde, bu y철ntemin, do휓ru bir + ger챌eklenimle bile (철rne휓in, Linux 2.0.31) sonraki 챌철z체mden daha + pahal캇 oldu휓u ortaya 챌캇km캇힊t캇r.</p> + + <p>횉o휓unlukla, Apache bunu (<code>http_main.c</code> i챌indeki) + <code>lingering_close</code> ad캇nda bir i힊levle ger챌ekler. Bu i힊lev + kabaca 힊철yle g철r체n체r:</p> + + <div class="example"><p><code> + void lingering_close (int s)<br /> + {<br /> + <span class="indent"> + char junk_buffer[2048];<br /> + <br /> + /* g철nderen taraf캇 kapat */<br /> + shutdown (s, 1);<br /> + <br /> + signal (SIGALRM, lingering_death);<br /> + alarm (30);<br /> + <br /> + for (;;) {<br /> + <span class="indent"> + /* s'i okumak i챌in, 2 saniyelik zaman a힊캇m캇 ile se챌 */<br /> + select (s for reading, 2 second timeout);<br /> + /* Hata olu힊mu힊sa d철ng체den 챌캇k */<br /> + if (error) break;<br /> + /* s okumak i챌in haz캇rsa */<br /> + if (s is ready for reading) {<br /> + <span class="indent"> + if (read (s, junk_buffer, sizeof (junk_buffer)) <= 0) {<br /> + <span class="indent"> + break;<br /> + </span> + }<br /> + /* geri kalan her힊ey burada */<br /> + </span> + }<br /> + </span> + }<br /> + <br /> + close (s);<br /> + </span> + } + </code></p></div> + + <p>Ba휓lant캇 sonunda bu do휓al olarak biraz daha masrafa yol a챌ar, fakat + g체venilir bir ger챌eklenim i챌in bu gereklidir. HTTP/1.1'in daha yayg캇n + kullan캇lmaya ba힊lanmas캇 ve t체m ba휓lant캇lar캇n kal캇c캇 hale gelmesiyle bu + ger챌eklenim daha fazla istek 체zerinden kendi masraf캇n캇 + kar힊캇layacakt캇r. Ate힊le oynamak ve bu 철zelli휓i devre d캇힊캇 b캇rakmak + isterseniz <code>NO_LINGCLOSE</code>'u tan캇mlayabilirsiniz, fakat bu + asla 철nerilmez. 횜zellikle, HTTP/1.1'den itibaren boruhatl캇 kal캇c캇 + ba휓lant캇lar캇n <code>lingering_close</code> kullanmaya ba힊lamas캇 mutlak + bir gerekliliktir (ve <a href="http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html"> + boruhatl캇 ba휓lant캇lar캇n daha h캇zl캇</a> olmas캇 nedeniyle bu + ba휓lant캇lar캇 desteklemek isteyebilirsiniz).</p> + + + + <h3>횉etele Dosyas캇</h3> + + + + <p>Apache'nin ana ve alt s체re챌leri birbirleriyle 챌etele denen bir힊ey + 체zerinden haberle힊irler. Bunun en m체kemmel 힊ekilde payla힊캇ml캇 bellekte + ger챌eklenmesi gerekir. Eri힊ti휓imiz veya portlar캇n캇 ayr캇nt캇l캇 olarak + belirtti휓imiz i힊letim sistemleri i챌in bu, genellikle payla힊캇ml캇 bellek + kullan캇larak ger챌eklenir. Geri kalanlar, 철ntan캇ml캇 olarak bunu bir + disk dosyas캇 kullanarak ger챌ekler. Bir disk dosya캇 yava힊 olman캇n yan캇 + s캇ra g체venilir de de휓ildir (ve daha az 철zelli휓e sahiptir). Mimarinizin + <code>src/main/conf.h</code> dosyas캇n캇 inceleyin ve + <code>USE_MMAP_SCOREBOARD</code> veya + <code>USE_SHMGET_SCOREBOARD</code>'a bak캇n. Bu ikisinden birinin (ve + yan캇 s캇ra s캇ras캇yla <code>HAVE_MMAP</code> veya + <code>HAVE_SHMGET</code>'in) tan캇mlanm캇힊 olmas캇, sa휓lanan payla힊캇ml캇 + bellek kodunu etkinle힊tirir. E휓er sisteminiz di휓er t체rdeki payla힊캇ml캇 + belle휓e sahipse, <code>src/main/http_main.c</code> dosyas캇n캇 a챌캇p, + Apache'de bu belle휓i kullanmas캇 gereken kanca i힊levleri ekleyin (Bize + de bir yama yollay캇n, l체tfen).</p> + + <div class="note">Tarihsel bilgi: Apache'nin Linux uyarlamas캇, Apache'nin 1.2 + s체r체m체ne kadar payla힊캇ml캇 belle휓i kullanmaya ba힊lamam캇힊t캇. Bu kusur, + Apache'nin Linux 체zerindeki erken d철nem s체r체mlerinin davran캇힊lar캇n캇n + zay캇f ve g체venilmez olmas캇na yol a챌m캇힊t캇.</div> + + + + <h3>DYNAMIC_MODULE_LIMIT</h3> + + + + <p>Devingen olarak y체klenen mod체lleri kullanmamak niyetindeyseniz + (buray캇 okuyan ve sunucunuzun ba힊ar캇m캇n캇 son k캇r캇nt캇s캇na kadar + artt캇rmakla ilgilenen biriyseniz bunu d체힊체nmezsiniz), sunucunuzu + derlerken se챌enekler aras캇na <code>-DDYNAMIC_MODULE_LIMIT=0</code> + se챌ene휓ini de ekleyin. Bu suretle, sadece, devingen olarak y체klenen + mod체ller i챌in ayr캇lacak belle휓i kazanm캇힊 olacaks캇n캇z.</p> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="trace" id="trace">Ek: Bir 챌a휓r캇 izlemesinin ayr캇nt캇l캇 챌철z체mlemesi</a></h2> + + + + <p>Burada, Solaris 8 체zerinde worker MPM'li Apache 2.0.38'in bir sistem + 챌a휓r캇s캇 izlenmektedir. Bu izleme 힊u komutla elde edilmi힊tir:</p> + + <div class="example"><p><code> + truss -l -p <var>httpd_챌ocuk_pidi</var>. + </code></p></div> + + <p><code>-l</code> se챌ene휓i, truss'a hafif bir s체recin yapt캇휓캇 her + sistem 챌a휓r캇s캇n캇 (hafif s체re챌 -- HS -- Solaris'in bir 챌ekirdek seviyesi + evreleme bi챌imi) g체nl체휓e yazmas캇n캇 s철yler.</p> + + <p>Di휓er sistemlerin sistem 챌a휓r캇lar캇n캇 izleyen farkl캇 ara챌lar캇 vard캇r + (<code>strace</code>, <code>ktrace</code>, <code>par</code> gibi). + Bunlar da benzer 챌캇kt캇lar 체retirler.</p> + + <p>Bu izleme s캇ras캇nda, bir istemci httpd'den 10 KB'l캇k duruk bir dosya + talebinde bulunmu힊tur. Duruk olmayan veya i챌erik uzla힊캇ml캇 isteklerin + izleme kay캇tlar캇 vah힊ice (baz캇 durumlarda epey 챌irkince) farkl캇 + g철r체n체r.</p> + + <div class="example"><p><code> + /67: accept(3, 0x00200BEC, 0x00200C0C, 1) (uykuda...)<br /> + /67: accept(3, 0x00200BEC, 0x00200C0C, 1) = 9 + </code></p></div> + + <p>Bu izlemede, dinleyen evre HS #67 i챌inde 챌al캇힊maktad캇r.</p> + + <div class="note"><code>accept(2)</code> dizgelemesinin olmay캇힊캇na dikkat edin. + 횜zellikle bu platformda worker MPM, 챌ok say캇da portu dinlemedik챌e, + 철ntan캇ml캇 olarak dizgele힊tirilmemi힊 bir accept 챌a휓r캇s캇 kullan캇r.</div> + + <div class="example"><p><code> + /65: lwp_park(0x00000000, 0) = 0<br /> + /67: lwp_unpark(65, 1) = 0 + </code></p></div> + + <p>Ba휓lant캇n캇n kabul edilmesiyle, dinleyici evre iste휓i yerine getirmek + 체zere bir worker evresini uyand캇r캇r. Bu izlemede, iste휓i yerine getiren + worker evresi HS #65'e aittir.</p> + + <div class="example"><p><code> + /65: getsockname(9, 0x00200BA4, 0x00200BC4, 1) = 0 + </code></p></div> + + <p>Sanal konaklar캇n ger챌eklenimi s캇ras캇nda, Apache'nin, ba휓lant캇lar캇 + kabul etmek i챌in kullan캇lan yerel soket adreslerini bilmesi gerekir. + 횉o휓u durumda bu 챌a휓r캇y캇 bertaraf etmek m체mk체nd체r (hi챌 sanal kona휓캇n + olmad캇휓캇 veya <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + y철nergelerinin mutlak adreslerle kullan캇ld캇휓캇 durumlarda). Fakat bu en + iyilemeleri yapmak i챌in hen체z bir 챌aba harcanmam캇힊t캇r.</p> + + <div class="example"><p><code> + /65: brk(0x002170E8) = 0<br /> + /65: brk(0x002190E8) = 0 + </code></p></div> + + <p><code>brk(2)</code> 챌a휓r캇lar캇 devingen bellekten bellek ay캇r캇r. httpd + 챌o휓u iste휓i yerine getirirken 철zel bellek ay캇r캇c캇lar + (<code>apr_pool</code> ve <code>apr_bucket_alloc</code>) kulland캇휓캇ndan + bunlar bir sistem 챌a휓r캇s캇 izlemesinde nadiren g철r체n체r. Bu izlemede, + httpd hen체z yeni ba힊lat캇ld캇휓캇ndan, 철zel bellek ay캇r캇c캇lar캇 olu힊turmak + i챌in ham bellek bloklar캇n캇 ay캇rmak amac캇yla <code>malloc(3)</code> + 챌a휓r캇lar캇 yapmas캇 gerekir.</p> + + <div class="example"><p><code> +/65: fcntl(9, F_GETFL, 0x00000000) = 2<br /> +/65: fstat64(9, 0xFAF7B818) = 0<br /> +/65: getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B910, 2190656) = 0<br /> +/65: fstat64(9, 0xFAF7B818) = 0<br /> +/65: getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B914, 2190656) = 0<br /> +/65: setsockopt(9, 65535, 8192, 0xFAF7B918, 4, 2190656) = 0<br /> +/65: fcntl(9, F_SETFL, 0x00000082) = 0 + </code></p></div> + + <p>Ard캇ndan, worker evresi istemciye (dosya tan캇t캇c캇s캇 9) engellenmeyen + kipte bir ba휓lant캇 a챌ar. <code>setsockopt(2)</code> + ve <code>getsockopt(2)</code> 챌a휓r캇lar캇, Solaris libc'sinin soketler + 체zerindeki <code>fcntl(2)</code> 챌a휓r캇s캇 yan캇nda birer yan etkiden + ibarettirler.</p> + + <div class="example"><p><code> + /65: read(9, " G E T / 1 0 k . h t m".., 8000) = 97 + </code></p></div> + + <p>Worker evresi istemciden iste휓i okur.</p> + + <div class="example"><p><code> +/65: stat("/var/httpd/apache/httpd-8999/htdocs/10k.html", 0xFAF7B978) = 0<br /> +/65: open("/var/httpd/apache/httpd-8999/htdocs/10k.html", O_RDONLY) = 10 + </code></p></div> + + <p>Bu httpd <code>Options FollowSymLinks</code> ve <code>AllowOverride + None</code> ile yap캇land캇r캇lm캇힊t캇r. Bu bak캇mdan, ne istenen dosya ile + sonu챌lanan yol 체zerindeki her dizinde <code>lstat(2)</code> 챌a휓r캇s캇na ne + de <code>.htaccess</code> dosyalar캇na bak캇lmas캇na gerek vard캇r. + <code>stat(2)</code> 챌a휓r캇s캇 basit챌e dosya i챌in 힊unlar캇 do휓rulamak + amac캇yla yap캇l캇r: 1) dosya mevcuttur ve 2) bir dizin de휓il normal bir + dosyad캇r.</p> + + <div class="example"><p><code> + /65: sendfilev(0, 9, 0x00200F90, 2, 0xFAF7B53C) = 10269 + </code></p></div> + + <p>Bu 철rnekte, httpd, istenen dosyay캇 ve HTTP yan캇t ba힊l캇휓캇n캇 tek bir + <code>sendfilev(2)</code> sistem 챌a휓r캇s캇 ile g철ndermektedir. Dosya + g철nderim i힊leminin anlam캇 sistemden sisteme de휓i힊iklik g철sterir. Baz캇 + sistemlerde, <code>sendfile(2)</code> 챌a휓r캇s캇ndan 철nce ba힊l캇klar캇 + g철ndermek i챌in <code>write(2)</code> veya <code>writev(2)</code> + 챌a휓r캇s캇 yapmak gerekir.</p> + + <div class="example"><p><code> + /65: write(4, " 1 2 7 . 0 . 0 . 1 - ".., 78) = 78 + </code></p></div> + + <p>Bu <code>write(2)</code> 챌a휓r캇s캇 iste휓i eri힊im g체nl체휓체ne kaydeder. Bu + izlemede eksik olan tek 힊ey, <code>time(2)</code> 챌a휓r캇s캇d캇r. Apache + 1.3'체n aksine, Apache 2.x zamana bakmak i챌in + <code>gettimeofday(3)</code> 챌a휓캇r캇s캇n캇 kullan캇r. Linux ve Solaris gibi + baz캇 i힊letim sistemleri, <code>gettimeofday</code> i힊levinin, s캇radan + bir sistem 챌a휓r캇s캇ndan daha fazla g철t체r체s체 olmayan en iyilenmi힊 bir + ger챌eklenimine sahiptir.</p> + + <div class="example"><p><code> + /65: shutdown(9, 1, 1) = 0<br /> + /65: poll(0xFAF7B980, 1, 2000) = 1<br /> + /65: read(9, 0xFAF7BC20, 512) = 0<br /> + /65: close(9) = 0 + </code></p></div> + + <p>Burada worker evresi ba휓lant캇y캇 zamana yaymaktad캇r.</p> + + <div class="example"><p><code> + /65: close(10) = 0<br /> + /65: lwp_park(0x00000000, 0) (uykuda...) + </code></p></div> + + <p>Son olarak, worker evresi teslim edilen dosyay캇 kapatt캇ktan sonra + dinleyici evre taraf캇ndan ba힊ka bir ba휓lant캇 atan캇ncaya kadar beklemeye + al캇n캇r.</p> + + <div class="example"><p><code> + /67: accept(3, 0x001FEB74, 0x001FEB94, 1) (uykuda...) + </code></p></div> + + <p>Bu arada, dinleyici evre ba휓lant캇y캇 bir worker evresine atar atamaz + ba힊ka bir ba휓lant캇y캇 beklemeye ba힊lar (Mevcut t체m evreler me힊gulse + dinleyici evreyi bask캇layan worker MPM'nin ak캇힊 denetim 힊emas캇na konu + olur). Bu izlemede g철r체nm체yor olsa da sonraki <code>accept(2)</code> + 챌a휓r캇s캇, yeni ba휓lant캇 kabul eden worker evresine paralel olarak + yap캇labilir (a힊캇r캇 y체k durumlar캇nda normal olarak, bu yap캇l캇r).</p> + + </div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/misc/perf-tuning.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/perf-tuning.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/perf-tuning.html" title="T체rk챌e"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br /><a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> alt캇nda lisansl캇d캇r.</p> +<p class="menu"><a href="../mod/">Mod체ller</a> | <a href="../mod/directives.html">Y철nergeler</a> | <a href="../faq/">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas캇</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html new file mode 100644 index 00000000..0890a9e4 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: relevant_standards.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: relevant_standards.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html.en new file mode 100644 index 00000000..2924d461 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html.en @@ -0,0 +1,199 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Relevant Standards - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Relevant Standards</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/relevant_standards.html" title="English"> en </a> | +<a href="../ko/misc/relevant_standards.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + <p>This page documents all the relevant standards that the + Apache HTTP Server follows, along with brief descriptions.</p> + + <p>In addition to the information listed below, the following resources + should be consulted:</p> + + <ul> + <li> + <a href="http://purl.org/NET/http-errata"> + http://purl.org/NET/http-errata</a> - HTTP/1.1 Specification Errata + </li> + <li> + <a href="http://www.rfc-editor.org/errata.html"> + http://www.rfc-editor.org/errata.html</a> - RFC Errata + </li> + <li> + <a href="http://ftp.ics.uci.edu/pub/ietf/http/#RFC"> + http://ftp.ics.uci.edu/pub/ietf/http/#RFC</a> - A pre-compiled list + of HTTP related RFCs + </li> + </ul> + + <div class="warning"><h3>Notice</h3> + <p>This document is not yet complete.</p> + </div> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#http_recommendations">HTTP Recommendations</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#html_recommendations">HTML Recommendations</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#authentication">Authentication</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#language_country_codes">Language/Country Codes</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="http_recommendations" id="http_recommendations">HTTP Recommendations</a></h2> + + <p>Regardless of what modules are compiled and used, Apache as a + basic web server complies with the following IETF recommendations:</p> + + <dl> + <dt><a href="http://www.rfc-editor.org/rfc/rfc1945.txt">RFC 1945</a> + (Informational)</dt> + + <dd>The Hypertext Transfer Protocol (HTTP) is an application-level + protocol with the lightness and speed necessary for distributed, + collaborative, hypermedia information systems. This documents + HTTP/1.0.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/rfc2616.txt">RFC 2616</a> + (Standards Track)</dt> + + <dd>The Hypertext Transfer Protocol (HTTP) is an + application-level protocol for distributed, collaborative, + hypermedia information systems. This documents HTTP/1.1.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/rfc2396.txt">RFC 2396</a> + (Standards Track)</dt> + + <dd>A Uniform Resource Identifier (URI) is a compact string of + characters for identifying an abstract or physical resource.</dd> + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="html_recommendations" id="html_recommendations">HTML Recommendations</a></h2> + + <p>Regarding the Hypertext Markup Language, Apache complies with + the following IETF and W3C recommendations:</p> + + <dl> + <dt><a href="http://www.rfc-editor.org/rfc/rfc2854.txt">RFC 2854</a> + (Informational)</dt> + + <dd>This document summarizes the history of HTML development, + and defines the "text/html" MIME type by pointing to the relevant + W3C recommendations.</dd> + + <dt><a href="http://www.w3.org/TR/html401">HTML 4.01 Specification</a> + (<a href="http://www.w3.org/MarkUp/html4-updates/errata">Errata</a>) + </dt> + + <dd>This specification defines the HyperText Markup Language (HTML), + the publishing language of the World Wide Web. This specification + defines HTML 4.01, which is a subversion of HTML 4.</dd> + + <dt><a href="http://www.w3.org/TR/REC-html32">HTML 3.2 Reference + Specification</a></dt> + + <dd>The HyperText Markup Language (HTML) is a simple markup language + used to create hypertext documents that are portable from one + platform to another. HTML documents are SGML documents.</dd> + + <dt><a href="http://www.w3.org/TR/xhtml11/">XHTML 1.1 - + Module-based XHTML</a> + (<a href="http://www.w3.org/2001/04/REC-xhtml-modularization-20010410-errata">Errata</a>) + </dt> + + <dd>This Recommendation defines a new XHTML document type + that is based upon the module framework and modules defined in + Modularization of XHTML.</dd> + + <dt><a href="http://www.w3.org/TR/xhtml1">XHTML 1.0 The + Extensible HyperText Markup Language (Second Edition)</a> + (<a href="http://www.w3.org/2002/08/REC-xhtml1-20020801-errata">Errata</a>) + </dt> + + <dd>This specification defines the Second Edition of XHTML 1.0, + a reformulation of HTML 4 as an XML 1.0 application, and three + DTDs corresponding to the ones defined by HTML 4.</dd> + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="authentication" id="authentication">Authentication</a></h2> + + <p>Concerning the different methods of authentication, Apache + follows the following IETF recommendations:</p> + + <dl> + <dt><a href="http://www.rfc-editor.org/rfc/rfc2617.txt">RFC 2617</a> + (Draft standard)</dt> + + <dd>"HTTP/1.0", includes the specification for a Basic + Access Authentication scheme.</dd> + + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="language_country_codes" id="language_country_codes">Language/Country Codes</a></h2> + + <p>The following links document ISO and other language and country + code information:</p> + + <dl> + <dt><a href="http://www.loc.gov/standards/iso639-2/">ISO 639-2</a></dt> + + <dd>ISO 639 provides two sets of language codes, one as a two-letter + code set (639-1) and another as a three-letter code set (this part + of ISO 639) for the representation of names of languages.</dd> + + <dt><a href="http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/index.html"> + ISO 3166-1</a></dt> + + <dd>These pages document the country names (official short names + in English) in alphabetical order as given in ISO 3166-1 and the + corresponding ISO 3166-1-alpha-2 code elements.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">BCP 47</a> + (Best Current Practice), + <a href="http://www.rfc-editor.org/rfc/rfc3066.txt">RFC 3066</a></dt> + + <dd>This document describes a language tag for use in cases where + it is desired to indicate the language used in an information + object, how to register values for use in this language tag, + and a construct for matching such language tags.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/rfc3282.txt">RFC 3282</a> + (Standards Track)</dt> + + <dd>This document defines a "Content-language:" header, for use in + cases where one desires to indicate the language of something that + has RFC 822-like headers, like MIME body parts or Web documents, + and an "Accept-Language:" header for use in cases where one wishes + to indicate one's preferences with regard to language.</dd> + </dl> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/relevant_standards.html" title="English"> en </a> | +<a href="../ko/misc/relevant_standards.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html.ko.euc-kr new file mode 100644 index 00000000..acbccb9d --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/relevant_standards.html.ko.euc-kr @@ -0,0 +1,191 @@ +<?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><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>관련 표준 - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>관련 표준</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/misc/relevant_standards.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/relevant_standards.html" title="Korean"> ko </a></p> +</div> + + <p>이 문서에는 간단한 설명과 함께 아파치 웹서버가 따르는 + 모든 관련 표준을 열거한다.</p> + + <p>아래 정보에 더하여 다음 자료도 살펴봐야 한다:</p> + + <ul> + <li> + <a href="http://purl.org/NET/http-errata"> + http://purl.org/NET/http-errata</a> - HTTP/1.1 규약 + 정오표 + </li> + <li> + <a href="http://www.rfc-editor.org/errata.html"> + http://www.rfc-editor.org/errata.html</a> - RFC 정오표 + </li> + <li> + <a href="http://ftp.ics.uci.edu/pub/ietf/http/#RFC"> + http://ftp.ics.uci.edu/pub/ietf/http/#RFC</a> - HTTP + 관련 RFC 목록 + </li> + </ul> + + <div class="warning"><h3>주의</h3> + <p>이 문서는 아직 완전하지 않다.</p> + </div> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#http_recommendations">HTTP 권고</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#html_recommendations">HTML 권고</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#authentication">인증</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#language_country_codes">언어/국가 코드</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="http_recommendations" id="http_recommendations">HTTP 권고</a></h2> + + <p>어떤 모듈을 컴파일하고 사용하는지와 관계없이 기본적으로 + 웹서버인 아파치는 다음 IETF 권고(recommendation)를 따른다:</p> + + <dl> + <dt><a href="http://www.rfc-editor.org/rfc/rfc1945.txt">RFC 1945</a> + (Informational)</dt> + + <dd>하이퍼텍스트 전송 프로토콜 (Hypertext Transfer Protocol, + HTTP)은 분산, 협동, 하이퍼매체 정보 시스템에 필요한 빠르고 + 가벼운 어플리케이션 수준(application-level) 프로토콜이다. + 이 문서는 HTTP/1.0을 설명한다.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/rfc2616.txt">RFC 2616</a> + (Standards Track)</dt> + + <dd>하이퍼텍스트 전송 프로토콜 (Hypertext Transfer Protocol, + HTTP)은 분산, 협동, 하이퍼매체 정보 시스템을 위한 어플리케이션 + 수준 프로토콜이다. 이 문서는 HTTP/1.1을 설명한다.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/rfc2396.txt">RFC 2396</a> + (Standards Track)</dt> + + <dd>표준 자원 식별자 (Uniform Resource Identifier, URI)는 + 추상적 혹은 물리적 자원을 식별하기위한 짧은 문자열이다.</dd> + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="html_recommendations" id="html_recommendations">HTML 권고</a></h2> + + <p>하이퍼텍스트 마크업 언어 (Hypertext Markup Language, + HTML)와 관련하여 아파치는 다음 IETF 권고와 W3C 권고를 따른다:</p> + + <dl> + <dt><a href="http://www.rfc-editor.org/rfc/rfc2854.txt">RFC 2854</a> + (Informational)</dt> + + <dd>이 문서는 HTML 개발과정을 요약하고, 관련 W3C 권고를 + 기반으로 "text/html" MIME type을 정의한다.</dd> + + <dt><a href="http://www.w3.org/TR/html401">HTML 4.01 규약</a> + (<a href="http://www.w3.org/MarkUp/html4-updates/errata">Errata</a>) + </dt> + + <dd>이 규약은 월드와이드웹의 출판언어인 하이퍼텍스트 마크업 + 언어 (Hypertext Markup Language, HTML)를 정의한다. 이 + 규약은 HTML 4의 하위버전인 HTML 4.01을 정의한다.</dd> + + <dt><a href="http://www.w3.org/TR/REC-html32">HTML 3.2 참고 규약</a></dt> + + <dd>하이퍼텍스트 마크업 언어 (Hypertext Markup Language, + HTML)는 플래폼과 무관한 하이퍼텍스트 문서를 위한 간단한 + 마크업 언어이다. HTML 문서는 SGML 문서이기도 하다.</dd> + + <dt><a href="http://www.w3.org/TR/xhtml11/">XHTML 1.1 - + 모듈기반 XHTML</a> + (<a href="http://www.w3.org/2001/04/REC-xhtml-modularization-20010410-errata">정오표</a>) + </dt> + + <dd>이 권고는 Modularization of XHTML에서 정의한 모듈 + 플레임워크와 모듈들을 기반으로 새로운 XHTML document type을 + 정의한다.</dd> + + <dt><a href="http://www.w3.org/TR/xhtml1">XHTML 1.0 + 확장 하이퍼텍스트 마크업 언어 (Extensible HyperText Markup + Language) (Second Edition)</a> + (<a href="http://www.w3.org/2002/08/REC-xhtml1-20020801-errata">정오표</a>) + </dt> + + <dd>이 문서는 HTML 4를 XML 1.0으로 재구성한 XHTML 1.0의 + 두번째 버전과 HTML 4에 해당하는 세가지 DTD를 정의한다.</dd> + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="authentication" id="authentication">인증</a></h2> + + <p>인증방법에 대해 아파치는 다음 IETF 권고를 따른다:</p> + + <dl> + <dt><a href="http://www.rfc-editor.org/rfc/rfc2617.txt">RFC 2617</a> + (Draft standard)</dt> + + <dd>Basic Access Authentication 규약을 포함한 "HTTP/1.0".</dd> + + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="language_country_codes" id="language_country_codes">언어/국가 코드</a></h2> + + <p>아래 링크에 ISO와 다른 언어/국가 코드 정보가 있다:</p> + + <dl> + <dt><a href="http://www.loc.gov/standards/iso639-2/">ISO 639-2</a></dt> + + <dd>ISO 639는 언어의 이름을 나타내는 두가지 언어 코드를 + 제공한다. 하나는 (639-1) 두 글자 코드이고 다른 하나는 + (이 문서) 세 글자 코드이다.</dd> + + <dt><a href="http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/index.html"> + ISO 3166-1</a></dt> + + <dd>이 문서는 ISO 3166-1과 ISO 3166-1-alpha-2 코드에 따라 + 알파벳 순서로 (영어로 짧은 공식이름) 국가명을 열거한다.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">BCP 47</a> + (Best Current Practice), + <a href="http://www.rfc-editor.org/rfc/rfc3066.txt">RFC 3066</a></dt> + + <dd>이 문서는 정보 객체에 사용한 언어를 알리기위해 사용할 + 언어 태그와 언어 태그에 사용할 값을 등록하는 방법, 언어 + 태그를 찾는 방식을 설명한다.</dd> + + <dt><a href="http://www.rfc-editor.org/rfc/rfc3282.txt">RFC 3282</a> + (Standards Track)</dt> + + <dd>이 문서는 MIME 내용 부분과 웹 문서와 같은 RFC 822식 + 헤더가 있는 정보의 언어를 알리기위한 "Content-language:" + 헤더와, 선호하는 언어를 나타내는 "Accept-Language:" 헤더를 + 정의한다.</dd> + </dl> + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/misc/relevant_standards.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/relevant_standards.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html new file mode 100644 index 00000000..e58a64eb --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: rewriteguide.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: rewriteguide.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html.en new file mode 100644 index 00000000..733f48bd --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html.en @@ -0,0 +1,2110 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>URL Rewriting Guide - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>URL Rewriting Guide</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/rewriteguide.html" title="English"> en </a> | +<a href="../ko/misc/rewriteguide.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + <div class="note"> + <p>Originally written by<br /> + <cite>Ralf S. Engelschall <rse@apache.org></cite><br /> + December 1997</p> + </div> + + <p>This document supplements the <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + <a href="../mod/mod_rewrite.html">reference documentation</a>. + It describes how one can use Apache's <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + to solve typical URL-based problems with which webmasters are + commonony confronted. We give detailed descriptions on how to + solve each problem by configuring URL rewriting rulesets.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#ToC1">Introduction to <code>mod_rewrite</code></a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ToC2">Practical Solutions</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#url">URL Layout</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#content">Content Handling</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#access">Access Restriction</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#other">Other</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="ToC1" id="ToC1">Introduction to <code>mod_rewrite</code></a></h2> + + + + <p>The Apache module <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> is a killer + one, i.e. it is a really sophisticated module which provides + a powerful way to do URL manipulations. With it you can do nearly + all types of URL manipulations you ever dreamed about. + The price you have to pay is to accept complexity, because + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>'s major drawback is that it is + not easy to understand and use for the beginner. And even + Apache experts sometimes discover new aspects where + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> can help.</p> + + <p>In other words: With <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> you either + shoot yourself in the foot the first time and never use it again + or love it for the rest of your life because of its power. + This paper tries to give you a few initial success events to + avoid the first case by presenting already invented solutions + to you.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="ToC2" id="ToC2">Practical Solutions</a></h2> + + + + <p>Here come a lot of practical solutions I've either invented + myself or collected from other people's solutions in the past. + Feel free to learn the black magic of URL rewriting from + these examples.</p> + + <div class="warning">ATTENTION: Depending on your server-configuration + it can be necessary to slightly change the examples for your + situation, e.g. adding the <code>[PT]</code> flag when + additionally using <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> and + <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code>, etc. Or rewriting a ruleset + to fit in <code>.htaccess</code> context instead + of per-server context. Always try to understand what a + particular ruleset really does before you use it. It + avoid problems.</div> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="url" id="url">URL Layout</a></h2> + + + + <h3>Canonical URLs</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>On some webservers there are more than one URL for a + resource. Usually there are canonical URLs (which should be + actually used and distributed) and those which are just + shortcuts, internal ones, etc. Independent of which URL the + user supplied with the request he should finally see the + canonical one only.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We do an external HTTP redirect for all non-canonical + URLs to fix them in the location view of the Browser and + for all subsequent requests. In the example ruleset below + we replace <code>/~user</code> by the canonical + <code>/u/user</code> and fix a missing trailing slash for + <code>/u/user</code>.</p> + +<div class="example"><pre> +RewriteRule ^/<strong>~</strong>([^/]+)/?(.*) /<strong>u</strong>/$1/$2 [<strong>R</strong>] +RewriteRule ^/([uge])/(<strong>[^/]+</strong>)$ /$1/$2<strong>/</strong> [<strong>R</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Canonical Hostnames</h3> + + + + <dl> + <dt>Description:</dt> + + <dd>The goal of this rule is to force the use of a particular + hostname, in preference to other hostnames which may be used to + reach the same site. For example, if you wish to force the use + of <strong>www.example.com</strong> instead of + <strong>example.com</strong>, you might use a variant of the + following recipe.</dd> + + <dt>Solution:</dt> + + <dd> +<div class="example"><pre> +# For sites running on a port other than 80 +RewriteCond %{HTTP_HOST} !^www\.example\.com [NC] +RewriteCond %{HTTP_HOST} !^$ +RewriteCond %{SERVER_PORT} !^80$ +RewriteRule ^/(.*) http://www.example.com:%{SERVER_PORT}/$1 [L,R] + +# And for a site running on port 80 +RewriteCond %{HTTP_HOST} !^www\.example\.com [NC] +RewriteCond %{HTTP_HOST} !^$ +RewriteRule ^/(.*) http://www.example.com/$1 [L,R] +</pre></div> + </dd> + </dl> + + + + <h3>Moved <code>DocumentRoot</code></h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Usually the <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + of the webserver directly relates to the URL "<code>/</code>". + But often this data is not really of top-level priority, it is + perhaps just one entity of a lot of data pools. For instance at + our Intranet sites there are <code>/e/www/</code> + (the homepage for WWW), <code>/e/sww/</code> (the homepage for + the Intranet) etc. Now because the data of the <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> stays at <code>/e/www/</code> we had + to make sure that all inlined images and other stuff inside this + data pool work for subsequent requests.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We redirect the URL <code>/</code> to + <code>/e/www/</code>: + </p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule <strong>^/$</strong> /e/www/ [<strong>R</strong>] +</pre></div> + + <p>Note that this can also be handled using the <code class="directive"><a href="../mod/mod_alias.html#redirectmatch">RedirectMatch</a></code> directive:</p> + + <div class="example"><p><code> + RedirectMatch ^/$ http://example.com/e/www/ + </code></p></div> + </dd> + </dl> + + + + <h3>Trailing Slash Problem</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Every webmaster can sing a song about the problem of + the trailing slash on URLs referencing directories. If they + are missing, the server dumps an error, because if you say + <code>/~quux/foo</code> instead of <code>/~quux/foo/</code> + then the server searches for a <em>file</em> named + <code>foo</code>. And because this file is a directory it + complains. Actually it tries to fix it itself in most of + the cases, but sometimes this mechanism need to be emulated + by you. For instance after you have done a lot of + complicated URL rewritings to CGI scripts etc.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>The solution to this subtle problem is to let the server + add the trailing slash automatically. To do this + correctly we have to use an external redirect, so the + browser correctly requests subsequent images etc. If we + only did a internal rewrite, this would only work for the + directory page, but would go wrong when any images are + included into this page with relative URLs, because the + browser would request an in-lined object. For instance, a + request for <code>image.gif</code> in + <code>/~quux/foo/index.html</code> would become + <code>/~quux/image.gif</code> without the external + redirect!</p> + + <p>So, to do this trick we write:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^foo<strong>$</strong> foo<strong>/</strong> [<strong>R</strong>] +</pre></div> + + <p>The crazy and lazy can even do the following in the + top-level <code>.htaccess</code> file of their homedir. + But notice that this creates some processing + overhead.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteCond %{REQUEST_FILENAME} <strong>-d</strong> +RewriteRule ^(.+<strong>[^/]</strong>)$ $1<strong>/</strong> [R] +</pre></div> + </dd> + </dl> + + + + <h3>Webcluster through Homogeneous URL Layout</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>We want to create a homogeneous and consistent URL + layout over all WWW servers on a Intranet webcluster, i.e. + all URLs (per definition server local and thus server + dependent!) become actually server <em>independent</em>! + What we want is to give the WWW namespace a consistent + server-independent layout: no URL should have to include + any physically correct target server. The cluster itself + should drive us automatically to the physical target + host.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>First, the knowledge of the target servers come from + (distributed) external maps which contain information + where our users, groups and entities stay. The have the + form</p> + +<div class="example"><pre> +user1 server_of_user1 +user2 server_of_user2 +: : +</pre></div> + + <p>We put them into files <code>map.xxx-to-host</code>. + Second we need to instruct all servers to redirect URLs + of the forms</p> + +<div class="example"><pre> +/u/user/anypath +/g/group/anypath +/e/entity/anypath +</pre></div> + + <p>to</p> + +<div class="example"><pre> +http://physical-host/u/user/anypath +http://physical-host/g/group/anypath +http://physical-host/e/entity/anypath +</pre></div> + + <p>when the URL is not locally valid to a server. The + following ruleset does this for us by the help of the map + files (assuming that server0 is a default server which + will be used if a user has no entry in the map):</p> + +<div class="example"><pre> +RewriteEngine on + +RewriteMap user-to-host txt:/path/to/map.user-to-host +RewriteMap group-to-host txt:/path/to/map.group-to-host +RewriteMap entity-to-host txt:/path/to/map.entity-to-host + +RewriteRule ^/u/<strong>([^/]+)</strong>/?(.*) http://<strong>${user-to-host:$1|server0}</strong>/u/$1/$2 +RewriteRule ^/g/<strong>([^/]+)</strong>/?(.*) http://<strong>${group-to-host:$1|server0}</strong>/g/$1/$2 +RewriteRule ^/e/<strong>([^/]+)</strong>/?(.*) http://<strong>${entity-to-host:$1|server0}</strong>/e/$1/$2 + +RewriteRule ^/([uge])/([^/]+)/?$ /$1/$2/.www/ +RewriteRule ^/([uge])/([^/]+)/([^.]+.+) /$1/$2/.www/$3\ +</pre></div> + </dd> + </dl> + + + + <h3>Move Homedirs to Different Webserver</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Many webmasters have asked for a solution to the + following situation: They wanted to redirect just all + homedirs on a webserver to another webserver. They usually + need such things when establishing a newer webserver which + will replace the old one over time.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>The solution is trivial with <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. + On the old webserver we just redirect all + <code>/~user/anypath</code> URLs to + <code>http://newserver/~user/anypath</code>.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^/~(.+) http://<strong>newserver</strong>/~$1 [R,L] +</pre></div> + </dd> + </dl> + + + + <h3>Structured Homedirs</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Some sites with thousands of users usually use a + structured homedir layout, i.e. each homedir is in a + subdirectory which begins for instance with the first + character of the username. So, <code>/~foo/anypath</code> + is <code>/home/<strong>f</strong>/foo/.www/anypath</code> + while <code>/~bar/anypath</code> is + <code>/home/<strong>b</strong>/bar/.www/anypath</code>.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We use the following ruleset to expand the tilde URLs + into exactly the above layout.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*) /home/<strong>$2</strong>/$1/.www$3 +</pre></div> + </dd> + </dl> + + + + <h3>Filesystem Reorganization</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>This really is a hardcore example: a killer application + which heavily uses per-directory + <code>RewriteRules</code> to get a smooth look and feel + on the Web while its data structure is never touched or + adjusted. Background: <strong><em>net.sw</em></strong> is + my archive of freely available Unix software packages, + which I started to collect in 1992. It is both my hobby + and job to to this, because while I'm studying computer + science I have also worked for many years as a system and + network administrator in my spare time. Every week I need + some sort of software so I created a deep hierarchy of + directories where I stored the packages:</p> + +<div class="example"><pre> +drwxrwxr-x 2 netsw users 512 Aug 3 18:39 Audio/ +drwxrwxr-x 2 netsw users 512 Jul 9 14:37 Benchmark/ +drwxrwxr-x 12 netsw users 512 Jul 9 00:34 Crypto/ +drwxrwxr-x 5 netsw users 512 Jul 9 00:41 Database/ +drwxrwxr-x 4 netsw users 512 Jul 30 19:25 Dicts/ +drwxrwxr-x 10 netsw users 512 Jul 9 01:54 Graphic/ +drwxrwxr-x 5 netsw users 512 Jul 9 01:58 Hackers/ +drwxrwxr-x 8 netsw users 512 Jul 9 03:19 InfoSys/ +drwxrwxr-x 3 netsw users 512 Jul 9 03:21 Math/ +drwxrwxr-x 3 netsw users 512 Jul 9 03:24 Misc/ +drwxrwxr-x 9 netsw users 512 Aug 1 16:33 Network/ +drwxrwxr-x 2 netsw users 512 Jul 9 05:53 Office/ +drwxrwxr-x 7 netsw users 512 Jul 9 09:24 SoftEng/ +drwxrwxr-x 7 netsw users 512 Jul 9 12:17 System/ +drwxrwxr-x 12 netsw users 512 Aug 3 20:15 Typesetting/ +drwxrwxr-x 10 netsw users 512 Jul 9 14:08 X11/ +</pre></div> + + <p>In July 1996 I decided to make this archive public to + the world via a nice Web interface. "Nice" means that I + wanted to offer an interface where you can browse + directly through the archive hierarchy. And "nice" means + that I didn't wanted to change anything inside this + hierarchy - not even by putting some CGI scripts at the + top of it. Why? Because the above structure should be + later accessible via FTP as well, and I didn't want any + Web or CGI stuff to be there.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>The solution has two parts: The first is a set of CGI + scripts which create all the pages at all directory + levels on-the-fly. I put them under + <code>/e/netsw/.www/</code> as follows:</p> + +<div class="example"><pre> +-rw-r--r-- 1 netsw users 1318 Aug 1 18:10 .wwwacl +drwxr-xr-x 18 netsw users 512 Aug 5 15:51 DATA/ +-rw-rw-rw- 1 netsw users 372982 Aug 5 16:35 LOGFILE +-rw-r--r-- 1 netsw users 659 Aug 4 09:27 TODO +-rw-r--r-- 1 netsw users 5697 Aug 1 18:01 netsw-about.html +-rwxr-xr-x 1 netsw users 579 Aug 2 10:33 netsw-access.pl +-rwxr-xr-x 1 netsw users 1532 Aug 1 17:35 netsw-changes.cgi +-rwxr-xr-x 1 netsw users 2866 Aug 5 14:49 netsw-home.cgi +drwxr-xr-x 2 netsw users 512 Jul 8 23:47 netsw-img/ +-rwxr-xr-x 1 netsw users 24050 Aug 5 15:49 netsw-lsdir.cgi +-rwxr-xr-x 1 netsw users 1589 Aug 3 18:43 netsw-search.cgi +-rwxr-xr-x 1 netsw users 1885 Aug 1 17:41 netsw-tree.cgi +-rw-r--r-- 1 netsw users 234 Jul 30 16:35 netsw-unlimit.lst +</pre></div> + + <p>The <code>DATA/</code> subdirectory holds the above + directory structure, i.e. the real + <strong><em>net.sw</em></strong> stuff and gets + automatically updated via <code>rdist</code> from time to + time. The second part of the problem remains: how to link + these two structures together into one smooth-looking URL + tree? We want to hide the <code>DATA/</code> directory + from the user while running the appropriate CGI scripts + for the various URLs. Here is the solution: first I put + the following into the per-directory configuration file + in the <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + of the server to rewrite the announced URL + <code>/net.sw/</code> to the internal path + <code>/e/netsw</code>:</p> + +<div class="example"><pre> +RewriteRule ^net.sw$ net.sw/ [R] +RewriteRule ^net.sw/(.*)$ e/netsw/$1 +</pre></div> + + <p>The first rule is for requests which miss the trailing + slash! The second rule does the real thing. And then + comes the killer configuration which stays in the + per-directory config file + <code>/e/netsw/.www/.wwwacl</code>:</p> + +<div class="example"><pre> +Options ExecCGI FollowSymLinks Includes MultiViews + +RewriteEngine on + +# we are reached via /net.sw/ prefix +RewriteBase /net.sw/ + +# first we rewrite the root dir to +# the handling cgi script +RewriteRule ^$ netsw-home.cgi [L] +RewriteRule ^index\.html$ netsw-home.cgi [L] + +# strip out the subdirs when +# the browser requests us from perdir pages +RewriteRule ^.+/(netsw-[^/]+/.+)$ $1 [L] + +# and now break the rewriting for local files +RewriteRule ^netsw-home\.cgi.* - [L] +RewriteRule ^netsw-changes\.cgi.* - [L] +RewriteRule ^netsw-search\.cgi.* - [L] +RewriteRule ^netsw-tree\.cgi$ - [L] +RewriteRule ^netsw-about\.html$ - [L] +RewriteRule ^netsw-img/.*$ - [L] + +# anything else is a subdir which gets handled +# by another cgi script +RewriteRule !^netsw-lsdir\.cgi.* - [C] +RewriteRule (.*) netsw-lsdir.cgi/$1 +</pre></div> + + <p>Some hints for interpretation:</p> + + <ol> + <li>Notice the <code>L</code> (last) flag and no + substitution field ('<code>-</code>') in the forth part</li> + + <li>Notice the <code>!</code> (not) character and + the <code>C</code> (chain) flag at the first rule + in the last part</li> + + <li>Notice the catch-all pattern in the last rule</li> + </ol> + </dd> + </dl> + + + + <h3>NCSA imagemap to Apache <code>mod_imap</code></h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>When switching from the NCSA webserver to the more + modern Apache webserver a lot of people want a smooth + transition. So they want pages which use their old NCSA + <code>imagemap</code> program to work under Apache with the + modern <code class="module"><a href="../mod/mod_imap.html">mod_imap</a></code>. The problem is that there + are a lot of hyperlinks around which reference the + <code>imagemap</code> program via + <code>/cgi-bin/imagemap/path/to/page.map</code>. Under + Apache this has to read just + <code>/path/to/page.map</code>.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We use a global rule to remove the prefix on-the-fly for + all requests:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^/cgi-bin/imagemap(.*) $1 [PT] +</pre></div> + </dd> + </dl> + + + + <h3>Search pages in more than one directory</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Sometimes it is necessary to let the webserver search + for pages in more than one directory. Here MultiViews or + other techniques cannot help.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We program a explicit ruleset which searches for the + files in the directories.</p> + +<div class="example"><pre> +RewriteEngine on + +# first try to find it in custom/... +# ...and if found stop and be happy: +RewriteCond /your/docroot/<strong>dir1</strong>/%{REQUEST_FILENAME} -f +RewriteRule ^(.+) /your/docroot/<strong>dir1</strong>/$1 [L] + +# second try to find it in pub/... +# ...and if found stop and be happy: +RewriteCond /your/docroot/<strong>dir2</strong>/%{REQUEST_FILENAME} -f +RewriteRule ^(.+) /your/docroot/<strong>dir2</strong>/$1 [L] + +# else go on for other Alias or ScriptAlias directives, +# etc. +RewriteRule ^(.+) - [PT] +</pre></div> + </dd> + </dl> + + + + <h3>Set Environment Variables According To URL Parts</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Perhaps you want to keep status information between + requests and use the URL to encode it. But you don't want + to use a CGI wrapper for all pages just to strip out this + information.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We use a rewrite rule to strip out the status information + and remember it via an environment variable which can be + later dereferenced from within XSSI or CGI. This way a + URL <code>/foo/S=java/bar/</code> gets translated to + <code>/foo/bar/</code> and the environment variable named + <code>STATUS</code> is set to the value "java".</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^(.*)/<strong>S=([^/]+)</strong>/(.*) $1/$3 [E=<strong>STATUS:$2</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Virtual User Hosts</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Assume that you want to provide + <code>www.<strong>username</strong>.host.domain.com</code> + for the homepage of username via just DNS A records to the + same machine and without any virtualhosts on this + machine.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>For HTTP/1.0 requests there is no solution, but for + HTTP/1.1 requests which contain a Host: HTTP header we + can use the following ruleset to rewrite + <code>http://www.username.host.com/anypath</code> + internally to <code>/home/username/anypath</code>:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{<strong>HTTP_HOST</strong>} ^www\.<strong>[^.]+</strong>\.host\.com$ +RewriteRule ^(.+) %{HTTP_HOST}$1 [C] +RewriteRule ^www\.<strong>([^.]+)</strong>\.host\.com(.*) /home/<strong>$1</strong>$2 +</pre></div> + </dd> + </dl> + + + + <h3>Redirect Homedirs For Foreigners</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>We want to redirect homedir URLs to another webserver + <code>www.somewhere.com</code> when the requesting user + does not stay in the local domain + <code>ourdomain.com</code>. This is sometimes used in + virtual host contexts.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>Just a rewrite condition:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{REMOTE_HOST} <strong>!^.+\.ourdomain\.com$</strong> +RewriteRule ^(/~.+) http://www.somewhere.com/$1 [R,L] +</pre></div> + </dd> + </dl> + + + + <h3>Redirect Failing URLs To Other Webserver</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>A typical FAQ about URL rewriting is how to redirect + failing requests on webserver A to webserver B. Usually + this is done via <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> CGI-scripts in Perl, but + there is also a <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> solution. + But notice that this performs more poorly than using an + <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> + CGI-script!</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>The first solution has the best performance but less + flexibility, and is less error safe:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond /your/docroot/%{REQUEST_FILENAME} <strong>!-f</strong> +RewriteRule ^(.+) http://<strong>webserverB</strong>.dom/$1 +</pre></div> + + <p>The problem here is that this will only work for pages + inside the <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>. While you can add more + Conditions (for instance to also handle homedirs, etc.) + there is better variant:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{REQUEST_URI} <strong>!-U</strong> +RewriteRule ^(.+) http://<strong>webserverB</strong>.dom/$1 +</pre></div> + + <p>This uses the URL look-ahead feature of <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. + The result is that this will work for all types of URLs + and is a safe way. But it does a performance impact on + the webserver, because for every request there is one + more internal subrequest. So, if your webserver runs on a + powerful CPU, use this one. If it is a slow machine, use + the first approach or better a <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> CGI-script.</p> + </dd> + </dl> + + + + <h3>Extended Redirection</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Sometimes we need more control (concerning the + character escaping mechanism) of URLs on redirects. + Usually the Apache kernels URL escape function also + escapes anchors, i.e. URLs like "<code>url#anchor</code>". + You cannot use this directly on redirects with + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> because the + <code>uri_escape()</code> function of Apache + would also escape the hash character. + How can we redirect to such a URL?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We have to use a kludge by the use of a NPH-CGI script + which does the redirect itself. Because here no escaping + is done (NPH=non-parseable headers). First we introduce a + new URL scheme <code>xredirect:</code> by the following + per-server config-line (should be one of the last rewrite + rules):</p> + +<div class="example"><pre> +RewriteRule ^xredirect:(.+) /path/to/nph-xredirect.cgi/$1 \ + [T=application/x-httpd-cgi,L] +</pre></div> + + <p>This forces all URLs prefixed with + <code>xredirect:</code> to be piped through the + <code>nph-xredirect.cgi</code> program. And this program + just looks like:</p> + +<div class="example"><pre> +#!/path/to/perl +## +## nph-xredirect.cgi -- NPH/CGI script for extended redirects +## Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved. +## + +$| = 1; +$url = $ENV{'PATH_INFO'}; + +print "HTTP/1.0 302 Moved Temporarily\n"; +print "Server: $ENV{'SERVER_SOFTWARE'}\n"; +print "Location: $url\n"; +print "Content-type: text/html\n"; +print "\n"; +print "<html>\n"; +print "<head>\n"; +print "<title>302 Moved Temporarily (EXTENDED)</title>\n"; +print "</head>\n"; +print "<body>\n"; +print "<h1>Moved Temporarily (EXTENDED)</h1>\n"; +print "The document has moved <a HREF=\"$url\">here</a>.<p>\n"; +print "</body>\n"; +print "</html>\n"; + +##EOF## +</pre></div> + + <p>This provides you with the functionality to do + redirects to all URL schemes, i.e. including the one + which are not directly accepted by <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. + For instance you can now also redirect to + <code>news:newsgroup</code> via</p> + +<div class="example"><pre> +RewriteRule ^anyurl xredirect:news:newsgroup +</pre></div> + + <div class="note">Notice: You have not to put <code>[R]</code> or + <code>[R,L]</code> to the above rule because the + <code>xredirect:</code> need to be expanded later + by our special "pipe through" rule above.</div> + </dd> + </dl> + + + + <h3>Archive Access Multiplexer</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Do you know the great CPAN (Comprehensive Perl Archive + Network) under <a href="http://www.perl.com/CPAN">http://www.perl.com/CPAN</a>? + This does a redirect to one of several FTP servers around + the world which carry a CPAN mirror and is approximately + near the location of the requesting client. Actually this + can be called an FTP access multiplexing service. While + CPAN runs via CGI scripts, how can a similar approach + implemented via <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>First we notice that from version 3.0.0 + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> can + also use the "<code>ftp:</code>" scheme on redirects. + And second, the location approximation can be done by a + <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code> + over the top-level domain of the client. + With a tricky chained ruleset we can use this top-level + domain as a key to our multiplexing map.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap multiplex txt:/path/to/map.cxan +RewriteRule ^/CxAN/(.*) %{REMOTE_HOST}::$1 [C] +RewriteRule ^.+\.<strong>([a-zA-Z]+)</strong>::(.*)$ ${multiplex:<strong>$1</strong>|ftp.default.dom}$2 [R,L] +</pre></div> + +<div class="example"><pre> +## +## map.cxan -- Multiplexing Map for CxAN +## + +de ftp://ftp.cxan.de/CxAN/ +uk ftp://ftp.cxan.uk/CxAN/ +com ftp://ftp.cxan.com/CxAN/ + : +##EOF## +</pre></div> + </dd> + </dl> + + + + <h3>Time-Dependent Rewriting</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>When tricks like time-dependent content should happen a + lot of webmasters still use CGI scripts which do for + instance redirects to specialized pages. How can it be done + via <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>There are a lot of variables named <code>TIME_xxx</code> + for rewrite conditions. In conjunction with the special + lexicographic comparison patterns <code><STRING</code>, + <code>>STRING</code> and <code>=STRING</code> we can + do time-dependent redirects:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{TIME_HOUR}%{TIME_MIN} >0700 +RewriteCond %{TIME_HOUR}%{TIME_MIN} <1900 +RewriteRule ^foo\.html$ foo.day.html +RewriteRule ^foo\.html$ foo.night.html +</pre></div> + + <p>This provides the content of <code>foo.day.html</code> + under the URL <code>foo.html</code> from + <code>07:00-19:00</code> and at the remaining time the + contents of <code>foo.night.html</code>. Just a nice + feature for a homepage...</p> + </dd> + </dl> + + + + <h3>Backward Compatibility for YYYY to XXXX migration</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>How can we make URLs backward compatible (still + existing virtually) after migrating <code>document.YYYY</code> + to <code>document.XXXX</code>, e.g. after translating a + bunch of <code>.html</code> files to <code>.phtml</code>?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We just rewrite the name to its basename and test for + existence of the new extension. If it exists, we take + that name, else we rewrite the URL to its original state.</p> + + +<div class="example"><pre> +# backward compatibility ruleset for +# rewriting document.html to document.phtml +# when and only when document.phtml exists +# but no longer document.html +RewriteEngine on +RewriteBase /~quux/ +# parse out basename, but remember the fact +RewriteRule ^(.*)\.html$ $1 [C,E=WasHTML:yes] +# rewrite to document.phtml if exists +RewriteCond %{REQUEST_FILENAME}.phtml -f +RewriteRule ^(.*)$ $1.phtml [S=1] +# else reverse the previous basename cutout +RewriteCond %{ENV:WasHTML} ^yes$ +RewriteRule ^(.*)$ $1.html +</pre></div> + </dd> + </dl> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="content" id="content">Content Handling</a></h2> + + + + <h3>From Old to New (intern)</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Assume we have recently renamed the page + <code>foo.html</code> to <code>bar.html</code> and now want + to provide the old URL for backward compatibility. Actually + we want that users of the old URL even not recognize that + the pages was renamed.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We rewrite the old URL to the new one internally via the + following rule:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>foo</strong>\.html$ <strong>bar</strong>.html +</pre></div> + </dd> + </dl> + + + + <h3>From Old to New (extern)</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Assume again that we have recently renamed the page + <code>foo.html</code> to <code>bar.html</code> and now want + to provide the old URL for backward compatibility. But this + time we want that the users of the old URL get hinted to + the new one, i.e. their browsers Location field should + change, too.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We force a HTTP redirect to the new URL which leads to a + change of the browsers and thus the users view:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>foo</strong>\.html$ <strong>bar</strong>.html [<strong>R</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Browser Dependent Content</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>At least for important top-level pages it is sometimes + necessary to provide the optimum of browser dependent + content, i.e. one has to provide a maximum version for the + latest Netscape variants, a minimum version for the Lynx + browsers and a average feature version for all others.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We cannot use content negotiation because the browsers do + not provide their type in that form. Instead we have to + act on the HTTP header "User-Agent". The following condig + does the following: If the HTTP header "User-Agent" + begins with "Mozilla/3", the page <code>foo.html</code> + is rewritten to <code>foo.NS.html</code> and and the + rewriting stops. If the browser is "Lynx" or "Mozilla" of + version 1 or 2 the URL becomes <code>foo.20.html</code>. + All other browsers receive page <code>foo.32.html</code>. + This is done by the following ruleset:</p> + +<div class="example"><pre> +RewriteCond %{HTTP_USER_AGENT} ^<strong>Mozilla/3</strong>.* +RewriteRule ^foo\.html$ foo.<strong>NS</strong>.html [<strong>L</strong>] + +RewriteCond %{HTTP_USER_AGENT} ^<strong>Lynx/</strong>.* [OR] +RewriteCond %{HTTP_USER_AGENT} ^<strong>Mozilla/[12]</strong>.* +RewriteRule ^foo\.html$ foo.<strong>20</strong>.html [<strong>L</strong>] + +RewriteRule ^foo\.html$ foo.<strong>32</strong>.html [<strong>L</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Dynamic Mirror</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Assume there are nice webpages on remote hosts we want + to bring into our namespace. For FTP servers we would use + the <code>mirror</code> program which actually maintains an + explicit up-to-date copy of the remote data on the local + machine. For a webserver we could use the program + <code>webcopy</code> which acts similar via HTTP. But both + techniques have one major drawback: The local copy is + always just as up-to-date as often we run the program. It + would be much better if the mirror is not a static one we + have to establish explicitly. Instead we want a dynamic + mirror with data which gets updated automatically when + there is need (updated data on the remote host).</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>To provide this feature we map the remote webpage or even + the complete remote webarea to our namespace by the use + of the <dfn>Proxy Throughput</dfn> feature + (flag <code>[P]</code>):</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>hotsheet/</strong>(.*)$ <strong>http://www.tstimpreso.com/hotsheet/</strong>$1 [<strong>P</strong>] +</pre></div> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>usa-news\.html</strong>$ <strong>http://www.quux-corp.com/news/index.html</strong> [<strong>P</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Reverse Dynamic Mirror</h3> + + + + <dl> + <dt>Description:</dt> + + <dd>...</dd> + + <dt>Solution:</dt> + + <dd> +<div class="example"><pre> +RewriteEngine on +RewriteCond /mirror/of/remotesite/$1 -U +RewriteRule ^http://www\.remotesite\.com/(.*)$ /mirror/of/remotesite/$1 +</pre></div> + </dd> + </dl> + + + + <h3>Retrieve Missing Data from Intranet</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>This is a tricky way of virtually running a corporate + (external) Internet webserver + (<code>www.quux-corp.dom</code>), while actually keeping + and maintaining its data on a (internal) Intranet webserver + (<code>www2.quux-corp.dom</code>) which is protected by a + firewall. The trick is that on the external webserver we + retrieve the requested data on-the-fly from the internal + one.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>First, we have to make sure that our firewall still + protects the internal webserver and that only the + external webserver is allowed to retrieve data from it. + For a packet-filtering firewall we could for instance + configure a firewall ruleset like the following:</p> + +<div class="example"><pre> +<strong>ALLOW</strong> Host www.quux-corp.dom Port >1024 --> Host www2.quux-corp.dom Port <strong>80</strong> +<strong>DENY</strong> Host * Port * --> Host www2.quux-corp.dom Port <strong>80</strong> +</pre></div> + + <p>Just adjust it to your actual configuration syntax. + Now we can establish the <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + rules which request the missing data in the background + through the proxy throughput feature:</p> + +<div class="example"><pre> +RewriteRule ^/~([^/]+)/?(.*) /home/$1/.www/$2 +RewriteCond %{REQUEST_FILENAME} <strong>!-f</strong> +RewriteCond %{REQUEST_FILENAME} <strong>!-d</strong> +RewriteRule ^/home/([^/]+)/.www/?(.*) http://<strong>www2</strong>.quux-corp.dom/~$1/pub/$2 [<strong>P</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Load Balancing</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Suppose we want to load balance the traffic to + <code>www.foo.com</code> over <code>www[0-5].foo.com</code> + (a total of 6 servers). How can this be done?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>There are a lot of possible solutions for this problem. + We will discuss first a commonly known DNS-based variant + and then the special one with <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>:</p> + + <ol> + <li> + <strong>DNS Round-Robin</strong> + + <p>The simplest method for load-balancing is to use + the DNS round-robin feature of <code>BIND</code>. + Here you just configure <code>www[0-9].foo.com</code> + as usual in your DNS with A(address) records, e.g.</p> + +<div class="example"><pre> +www0 IN A 1.2.3.1 +www1 IN A 1.2.3.2 +www2 IN A 1.2.3.3 +www3 IN A 1.2.3.4 +www4 IN A 1.2.3.5 +www5 IN A 1.2.3.6 +</pre></div> + + <p>Then you additionally add the following entry:</p> + +<div class="example"><pre> +www IN CNAME www0.foo.com. + IN CNAME www1.foo.com. + IN CNAME www2.foo.com. + IN CNAME www3.foo.com. + IN CNAME www4.foo.com. + IN CNAME www5.foo.com. + IN CNAME www6.foo.com. +</pre></div> + + <p>Notice that this seems wrong, but is actually an + intended feature of <code>BIND</code> and can be used + in this way. However, now when <code>www.foo.com</code> gets + resolved, <code>BIND</code> gives out <code>www0-www6</code> + - but in a slightly permutated/rotated order every time. + This way the clients are spread over the various + servers. But notice that this not a perfect load + balancing scheme, because DNS resolve information + gets cached by the other nameservers on the net, so + once a client has resolved <code>www.foo.com</code> + to a particular <code>wwwN.foo.com</code>, all + subsequent requests also go to this particular name + <code>wwwN.foo.com</code>. But the final result is + ok, because the total sum of the requests are really + spread over the various webservers.</p> + </li> + + <li> + <strong>DNS Load-Balancing</strong> + + <p>A sophisticated DNS-based method for + load-balancing is to use the program + <code>lbnamed</code> which can be found at <a href="http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html"> + http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html</a>. + It is a Perl 5 program in conjunction with auxilliary + tools which provides a real load-balancing for + DNS.</p> + </li> + + <li> + <strong>Proxy Throughput Round-Robin</strong> + + <p>In this variant we use <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + and its proxy throughput feature. First we dedicate + <code>www0.foo.com</code> to be actually + <code>www.foo.com</code> by using a single</p> + +<div class="example"><pre> +www IN CNAME www0.foo.com. +</pre></div> + + <p>entry in the DNS. Then we convert + <code>www0.foo.com</code> to a proxy-only server, + i.e. we configure this machine so all arriving URLs + are just pushed through the internal proxy to one of + the 5 other servers (<code>www1-www5</code>). To + accomplish this we first establish a ruleset which + contacts a load balancing script <code>lb.pl</code> + for all URLs.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap lb prg:/path/to/lb.pl +RewriteRule ^/(.+)$ ${lb:$1} [P,L] +</pre></div> + + <p>Then we write <code>lb.pl</code>:</p> + +<div class="example"><pre> +#!/path/to/perl +## +## lb.pl -- load balancing script +## + +$| = 1; + +$name = "www"; # the hostname base +$first = 1; # the first server (not 0 here, because 0 is myself) +$last = 5; # the last server in the round-robin +$domain = "foo.dom"; # the domainname + +$cnt = 0; +while (<STDIN>) { + $cnt = (($cnt+1) % ($last+1-$first)); + $server = sprintf("%s%d.%s", $name, $cnt+$first, $domain); + print "http://$server/$_"; +} + +##EOF## +</pre></div> + + <div class="note">A last notice: Why is this useful? Seems like + <code>www0.foo.com</code> still is overloaded? The + answer is yes, it is overloaded, but with plain proxy + throughput requests, only! All SSI, CGI, ePerl, etc. + processing is completely done on the other machines. + This is the essential point.</div> + </li> + + <li> + <strong>Hardware/TCP Round-Robin</strong> + + <p>There is a hardware solution available, too. Cisco + has a beast called LocalDirector which does a load + balancing at the TCP/IP level. Actually this is some + sort of a circuit level gateway in front of a + webcluster. If you have enough money and really need + a solution with high performance, use this one.</p> + </li> + </ol> + </dd> + </dl> + + + + <h3>New MIME-type, New Service</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>On the net there are a lot of nifty CGI programs. But + their usage is usually boring, so a lot of webmaster + don't use them. Even Apache's Action handler feature for + MIME-types is only appropriate when the CGI programs + don't need special URLs (actually <code>PATH_INFO</code> + and <code>QUERY_STRINGS</code>) as their input. First, + let us configure a new file type with extension + <code>.scgi</code> (for secure CGI) which will be processed + by the popular <code>cgiwrap</code> program. The problem + here is that for instance we use a Homogeneous URL Layout + (see above) a file inside the user homedirs has the URL + <code>/u/user/foo/bar.scgi</code>. But + <code>cgiwrap</code> needs the URL in the form + <code>/~user/foo/bar.scgi/</code>. The following rule + solves the problem:</p> + +<div class="example"><pre> +RewriteRule ^/[uge]/<strong>([^/]+)</strong>/\.www/(.+)\.scgi(.*) ... +... /internal/cgi/user/cgiwrap/~<strong>$1</strong>/$2.scgi$3 [NS,<strong>T=application/x-http-cgi</strong>] +</pre></div> + + <p>Or assume we have some more nifty programs: + <code>wwwlog</code> (which displays the + <code>access.log</code> for a URL subtree and + <code>wwwidx</code> (which runs Glimpse on a URL + subtree). We have to provide the URL area to these + programs so they know on which area they have to act on. + But usually this ugly, because they are all the times + still requested from that areas, i.e. typically we would + run the <code>swwidx</code> program from within + <code>/u/user/foo/</code> via hyperlink to</p> + +<div class="example"><pre> +/internal/cgi/user/swwidx?i=/u/user/foo/ +</pre></div> + + <p>which is ugly. Because we have to hard-code + <strong>both</strong> the location of the area + <strong>and</strong> the location of the CGI inside the + hyperlink. When we have to reorganize the area, we spend a + lot of time changing the various hyperlinks.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>The solution here is to provide a special new URL format + which automatically leads to the proper CGI invocation. + We configure the following:</p> + +<div class="example"><pre> +RewriteRule ^/([uge])/([^/]+)(/?.*)/\* /internal/cgi/user/wwwidx?i=/$1/$2$3/ +RewriteRule ^/([uge])/([^/]+)(/?.*):log /internal/cgi/user/wwwlog?f=/$1/$2$3 +</pre></div> + + <p>Now the hyperlink to search at + <code>/u/user/foo/</code> reads only</p> + +<div class="example"><pre> +HREF="*" +</pre></div> + + <p>which internally gets automatically transformed to</p> + +<div class="example"><pre> +/internal/cgi/user/wwwidx?i=/u/user/foo/ +</pre></div> + + <p>The same approach leads to an invocation for the + access log CGI program when the hyperlink + <code>:log</code> gets used.</p> + </dd> + </dl> + + + + <h3>From Static to Dynamic</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>How can we transform a static page + <code>foo.html</code> into a dynamic variant + <code>foo.cgi</code> in a seamless way, i.e. without notice + by the browser/user.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We just rewrite the URL to the CGI-script and force the + correct MIME-type so it gets really run as a CGI-script. + This way a request to <code>/~quux/foo.html</code> + internally leads to the invocation of + <code>/~quux/foo.cgi</code>.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^foo\.<strong>html</strong>$ foo.<strong>cgi</strong> [T=<strong>application/x-httpd-cgi</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>On-the-fly Content-Regeneration</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Here comes a really esoteric feature: Dynamically + generated but statically served pages, i.e. pages should be + delivered as pure static pages (read from the filesystem + and just passed through), but they have to be generated + dynamically by the webserver if missing. This way you can + have CGI-generated pages which are statically served unless + one (or a cronjob) removes the static contents. Then the + contents gets refreshed.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + This is done via the following ruleset: + +<div class="example"><pre> +RewriteCond %{REQUEST_FILENAME} <strong>!-s</strong> +RewriteRule ^page\.<strong>html</strong>$ page.<strong>cgi</strong> [T=application/x-httpd-cgi,L] +</pre></div> + + <p>Here a request to <code>page.html</code> leads to a + internal run of a corresponding <code>page.cgi</code> if + <code>page.html</code> is still missing or has filesize + null. The trick here is that <code>page.cgi</code> is a + usual CGI script which (additionally to its <code>STDOUT</code>) + writes its output to the file <code>page.html</code>. + Once it was run, the server sends out the data of + <code>page.html</code>. When the webmaster wants to force + a refresh the contents, he just removes + <code>page.html</code> (usually done by a cronjob).</p> + </dd> + </dl> + + + + <h3>Document With Autorefresh</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Wouldn't it be nice while creating a complex webpage if + the webbrowser would automatically refresh the page every + time we write a new version from within our editor? + Impossible?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>No! We just combine the MIME multipart feature, the + webserver NPH feature and the URL manipulation power of + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>. First, we establish a new + URL feature: Adding just <code>:refresh</code> to any + URL causes this to be refreshed every time it gets + updated on the filesystem.</p> + +<div class="example"><pre> +RewriteRule ^(/[uge]/[^/]+/?.*):refresh /internal/cgi/apache/nph-refresh?f=$1 +</pre></div> + + <p>Now when we reference the URL</p> + +<div class="example"><pre> +/u/foo/bar/page.html:refresh +</pre></div> + + <p>this leads to the internal invocation of the URL</p> + +<div class="example"><pre> +/internal/cgi/apache/nph-refresh?f=/u/foo/bar/page.html +</pre></div> + + <p>The only missing part is the NPH-CGI script. Although + one would usually say "left as an exercise to the reader" + ;-) I will provide this, too.</p> + +<div class="example"><pre> +#!/sw/bin/perl +## +## nph-refresh -- NPH/CGI script for auto refreshing pages +## Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved. +## +$| = 1; + +# split the QUERY_STRING variable +@pairs = split(/&/, $ENV{'QUERY_STRING'}); +foreach $pair (@pairs) { + ($name, $value) = split(/=/, $pair); + $name =~ tr/A-Z/a-z/; + $name = 'QS_' . $name; + $value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C", hex($1))/eg; + eval "\$$name = \"$value\""; +} +$QS_s = 1 if ($QS_s eq ''); +$QS_n = 3600 if ($QS_n eq ''); +if ($QS_f eq '') { + print "HTTP/1.0 200 OK\n"; + print "Content-type: text/html\n\n"; + print "&lt;b&gt;ERROR&lt;/b&gt;: No file given\n"; + exit(0); +} +if (! -f $QS_f) { + print "HTTP/1.0 200 OK\n"; + print "Content-type: text/html\n\n"; + print "&lt;b&gt;ERROR&lt;/b&gt;: File $QS_f not found\n"; + exit(0); +} + +sub print_http_headers_multipart_begin { + print "HTTP/1.0 200 OK\n"; + $bound = "ThisRandomString12345"; + print "Content-type: multipart/x-mixed-replace;boundary=$bound\n"; + &print_http_headers_multipart_next; +} + +sub print_http_headers_multipart_next { + print "\n--$bound\n"; +} + +sub print_http_headers_multipart_end { + print "\n--$bound--\n"; +} + +sub displayhtml { + local($buffer) = @_; + $len = length($buffer); + print "Content-type: text/html\n"; + print "Content-length: $len\n\n"; + print $buffer; +} + +sub readfile { + local($file) = @_; + local(*FP, $size, $buffer, $bytes); + ($x, $x, $x, $x, $x, $x, $x, $size) = stat($file); + $size = sprintf("%d", $size); + open(FP, "&lt;$file"); + $bytes = sysread(FP, $buffer, $size); + close(FP); + return $buffer; +} + +$buffer = &readfile($QS_f); +&print_http_headers_multipart_begin; +&displayhtml($buffer); + +sub mystat { + local($file) = $_[0]; + local($time); + + ($x, $x, $x, $x, $x, $x, $x, $x, $x, $mtime) = stat($file); + return $mtime; +} + +$mtimeL = &mystat($QS_f); +$mtime = $mtime; +for ($n = 0; $n &lt; $QS_n; $n++) { + while (1) { + $mtime = &mystat($QS_f); + if ($mtime ne $mtimeL) { + $mtimeL = $mtime; + sleep(2); + $buffer = &readfile($QS_f); + &print_http_headers_multipart_next; + &displayhtml($buffer); + sleep(5); + $mtimeL = &mystat($QS_f); + last; + } + sleep($QS_s); + } +} + +&print_http_headers_multipart_end; + +exit(0); + +##EOF## +</pre></div> + </dd> + </dl> + + + + <h3>Mass Virtual Hosting</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>The <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> feature of Apache is nice + and works great when you just have a few dozens + virtual hosts. But when you are an ISP and have hundreds of + virtual hosts to provide this feature is not the best + choice.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>To provide this feature we map the remote webpage or even + the complete remote webarea to our namespace by the use + of the <dfn>Proxy Throughput</dfn> feature (flag <code>[P]</code>):</p> + +<div class="example"><pre> +## +## vhost.map +## +www.vhost1.dom:80 /path/to/docroot/vhost1 +www.vhost2.dom:80 /path/to/docroot/vhost2 + : +www.vhostN.dom:80 /path/to/docroot/vhostN +</pre></div> + +<div class="example"><pre> +## +## httpd.conf +## + : +# use the canonical hostname on redirects, etc. +UseCanonicalName on + + : +# add the virtual host in front of the CLF-format +CustomLog /path/to/access_log "%{VHOST}e %h %l %u %t \"%r\" %>s %b" + : + +# enable the rewriting engine in the main server +RewriteEngine on + +# define two maps: one for fixing the URL and one which defines +# the available virtual hosts with their corresponding +# DocumentRoot. +RewriteMap lowercase int:tolower +RewriteMap vhost txt:/path/to/vhost.map + +# Now do the actual virtual host mapping +# via a huge and complicated single rule: +# +# 1. make sure we don't map for common locations +RewriteCond %{REQUEST_URI} !^/commonurl1/.* +RewriteCond %{REQUEST_URI} !^/commonurl2/.* + : +RewriteCond %{REQUEST_URI} !^/commonurlN/.* +# +# 2. make sure we have a Host header, because +# currently our approach only supports +# virtual hosting through this header +RewriteCond %{HTTP_HOST} !^$ +# +# 3. lowercase the hostname +RewriteCond ${lowercase:%{HTTP_HOST}|NONE} ^(.+)$ +# +# 4. lookup this hostname in vhost.map and +# remember it only when it is a path +# (and not "NONE" from above) +RewriteCond ${vhost:%1} ^(/.*)$ +# +# 5. finally we can map the URL to its docroot location +# and remember the virtual host for logging puposes +RewriteRule ^/(.*)$ %1/$1 [E=VHOST:${lowercase:%{HTTP_HOST}}] + : +</pre></div> + </dd> + </dl> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="access" id="access">Access Restriction</a></h2> + + + + <h3>Blocking of Robots</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>How can we block a really annoying robot from + retrieving pages of a specific webarea? A + <code>/robots.txt</code> file containing entries of the + "Robot Exclusion Protocol" is typically not enough to get + rid of such a robot.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We use a ruleset which forbids the URLs of the webarea + <code>/~quux/foo/arc/</code> (perhaps a very deep + directory indexed area where the robot traversal would + create big server load). We have to make sure that we + forbid access only to the particular robot, i.e. just + forbidding the host where the robot runs is not enough. + This would block users from this host, too. We accomplish + this by also matching the User-Agent HTTP header + information.</p> + +<div class="example"><pre> +RewriteCond %{HTTP_USER_AGENT} ^<strong>NameOfBadRobot</strong>.* +RewriteCond %{REMOTE_ADDR} ^<strong>123\.45\.67\.[8-9]</strong>$ +RewriteRule ^<strong>/~quux/foo/arc/</strong>.+ - [<strong>F</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>Blocked Inline-Images</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Assume we have under <code>http://www.quux-corp.de/~quux/</code> + some pages with inlined GIF graphics. These graphics are + nice, so others directly incorporate them via hyperlinks to + their pages. We don't like this practice because it adds + useless traffic to our server.</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>While we cannot 100% protect the images from inclusion, + we can at least restrict the cases where the browser + sends a HTTP Referer header.</p> + +<div class="example"><pre> +RewriteCond %{HTTP_REFERER} <strong>!^$</strong> +RewriteCond %{HTTP_REFERER} !^http://www.quux-corp.de/~quux/.*$ [NC] +RewriteRule <strong>.*\.gif$</strong> - [F] +</pre></div> + +<div class="example"><pre> +RewriteCond %{HTTP_REFERER} !^$ +RewriteCond %{HTTP_REFERER} !.*/foo-with-gif\.html$ +RewriteRule <strong>^inlined-in-foo\.gif$</strong> - [F] +</pre></div> + </dd> + </dl> + + + + <h3>Host Deny</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>How can we forbid a list of externally configured hosts + from using our server?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>For Apache >= 1.3b6:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap hosts-deny txt:/path/to/hosts.deny +RewriteCond ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR] +RewriteCond ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND +RewriteRule ^/.* - [F] +</pre></div> + + <p>For Apache <= 1.3b6:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap hosts-deny txt:/path/to/hosts.deny +RewriteRule ^/(.*)$ ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND}/$1 +RewriteRule !^NOT-FOUND/.* - [F] +RewriteRule ^NOT-FOUND/(.*)$ ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND}/$1 +RewriteRule !^NOT-FOUND/.* - [F] +RewriteRule ^NOT-FOUND/(.*)$ /$1 +</pre></div> + +<div class="example"><pre> +## +## hosts.deny +## +## ATTENTION! This is a map, not a list, even when we treat it as such. +## mod_rewrite parses it for key/value pairs, so at least a +## dummy value "-" must be present for each entry. +## + +193.102.180.41 - +bsdti1.sdm.de - +192.76.162.40 - +</pre></div> + </dd> + </dl> + + + + <h3>Proxy Deny</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>How can we forbid a certain host or even a user of a + special host from using the Apache proxy?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We first have to make sure <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + is below(!) <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> in the Configuration + file when compiling the Apache webserver. This way it gets + called <em>before</em> <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. Then we + configure the following for a host-dependent deny...</p> + +<div class="example"><pre> +RewriteCond %{REMOTE_HOST} <strong>^badhost\.mydomain\.com$</strong> +RewriteRule !^http://[^/.]\.mydomain.com.* - [F] +</pre></div> + + <p>...and this one for a user@host-dependent deny:</p> + +<div class="example"><pre> +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>^badguy@badhost\.mydomain\.com$</strong> +RewriteRule !^http://[^/.]\.mydomain.com.* - [F] +</pre></div> + </dd> + </dl> + + + + <h3>Special Authentication Variant</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>Sometimes a very special authentication is needed, for + instance a authentication which checks for a set of + explicitly configured users. Only these should receive + access and without explicit prompting (which would occur + when using the Basic Auth via <code class="module"><a href="../mod/mod_auth.html">mod_auth</a></code>).</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>We use a list of rewrite conditions to exclude all except + our friends:</p> + +<div class="example"><pre> +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>!^friend1@client1.quux-corp\.com$</strong> +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>!^friend2</strong>@client2.quux-corp\.com$ +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>!^friend3</strong>@client3.quux-corp\.com$ +RewriteRule ^/~quux/only-for-friends/ - [F] +</pre></div> + </dd> + </dl> + + + + <h3>Referer-based Deflector</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>How can we program a flexible URL Deflector which acts + on the "Referer" HTTP header and can be configured with as + many referring pages as we like?</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>Use the following really tricky ruleset...</p> + +<div class="example"><pre> +RewriteMap deflector txt:/path/to/deflector.map + +RewriteCond %{HTTP_REFERER} !="" +RewriteCond ${deflector:%{HTTP_REFERER}} ^-$ +RewriteRule ^.* %{HTTP_REFERER} [R,L] + +RewriteCond %{HTTP_REFERER} !="" +RewriteCond ${deflector:%{HTTP_REFERER}|NOT-FOUND} !=NOT-FOUND +RewriteRule ^.* ${deflector:%{HTTP_REFERER}} [R,L] +</pre></div> + + <p>... in conjunction with a corresponding rewrite + map:</p> + +<div class="example"><pre> +## +## deflector.map +## + +http://www.badguys.com/bad/index.html - +http://www.badguys.com/bad/index2.html - +http://www.badguys.com/bad/index3.html http://somewhere.com/ +</pre></div> + + <p>This automatically redirects the request back to the + referring page (when "<code>-</code>" is used as the value + in the map) or to a specific URL (when an URL is specified + in the map as the second argument).</p> + </dd> + </dl> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="other" id="other">Other</a></h2> + + + + <h3>External Rewriting Engine</h3> + + + + <dl> + <dt>Description:</dt> + + <dd> + <p>A FAQ: How can we solve the FOO/BAR/QUUX/etc. + problem? There seems no solution by the use of + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>...</p> + </dd> + + <dt>Solution:</dt> + + <dd> + <p>Use an external <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code>, i.e. a program which acts + like a <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code>. It is run once on startup of Apache + receives the requested URLs on <code>STDIN</code> and has + to put the resulting (usually rewritten) URL on + <code>STDOUT</code> (same order!).</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap quux-map <strong>prg:</strong>/path/to/map.quux.pl +RewriteRule ^/~quux/(.*)$ /~quux/<strong>${quux-map:$1}</strong> +</pre></div> + +<div class="example"><pre> +#!/path/to/perl + +# disable buffered I/O which would lead +# to deadloops for the Apache server +$| = 1; + +# read URLs one per line from stdin and +# generate substitution URL on stdout +while (<>) { + s|^foo/|bar/|; + print $_; +} +</pre></div> + + <p>This is a demonstration-only example and just rewrites + all URLs <code>/~quux/foo/...</code> to + <code>/~quux/bar/...</code>. Actually you can program + whatever you like. But notice that while such maps can be + <strong>used</strong> also by an average user, only the + system administrator can <strong>define</strong> it.</p> + </dd> + </dl> + + + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/rewriteguide.html" title="English"> en </a> | +<a href="../ko/misc/rewriteguide.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html.ko.euc-kr new file mode 100644 index 00000000..694b8f01 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/rewriteguide.html.ko.euc-kr @@ -0,0 +1,2013 @@ +<?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><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>URL 재작성 지침서 - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>URL 재작성 지침서</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/misc/rewriteguide.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/rewriteguide.html" title="Korean"> ko </a></p> +</div> +<div class="outofdate">이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.</div> + + <div class="note"> + <p>원저자<br /> + <cite>Ralf S. Engelschall <rse@apache.org></cite><br /> + 1997년 12월</p> + </div> + + <p>이 문서는 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> <a href="../mod/mod_rewrite.html">참조 문서</a>를 보충한다. + 이 문서는 웹관리자가 실제 작업에서 부딪치게되는 전형적인 + URL관련 문제를 해결하기위해서 어떻게 아파치 + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용하는지 설명한다. URL + 재작성 규칙을 설정하여 문제를 해결하는 방법을 자세히 설명한다.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#ToC1"><code>mod_rewrite</code> 소개</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ToC2">실용적인 해결책</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#url">URL 구조</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#content">컨텐츠 다루기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#access">접근 제한</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#other">기타</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="ToC1" id="ToC1"><code>mod_rewrite</code> 소개</a></h2> + + + + <p>아파치 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> 모듈은 굉장하다. + 즉, URL을 조작할 수 있는 강력하고 실로 정교한 모듈이다. + 상상해왔던 거의 모든 종류의 URL 조작이 가능하다. 그러나 + 그 대가로 사용하기 복잡하다. <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>의 + 최대 단점은 초보자가 이해하고 사용하기 쉽지 않다는 점이다. + 심지어 아파치 전문가도 종종 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>의 + 새로운 용도를 발견한다.</p> + + <p>다른 말로: <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></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="ToC2" id="ToC2">실용적인 해결책</a></h2> + + + + <p>이제 내가 직접 만들었거나 다른 사람들이 만든 많은 실용적인 + 해결책이 나온다. 예제에서 URL 재작성의 흑마술을 마음껏 배우길 + 바란다.</p> + + <div class="warning">주의: 서버 설정에 따라 상황에 맞게 + 예제를 조금 수정해야 할 경우가 있다. 예를 들어, 추가로 + <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code>, <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code> + 등을 사용한다면 <code>[PT]</code> 플래그를 추가한다. 혹은 + 주서버설정/가상호스트 사용장소가 아닌 <code>.htaccess</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="url" id="url">URL 구조</a></h2> + + + + <h3>기준이 되는 URL</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>한 리소스에 대해 여러 URL을 가지는 웹서버가 있다. + 보통 (실제 사용하고 알려져야 할) 기준이 되는 URL과, + 단축 혹은 내부 용도의 URL이 있다. 사용자가 요청에 + 어떤 URL을 사용하던지 기준이 되는 URL만을 보여줘야 + 한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>기준이 되지않는 모든 URL을 브라우저가 알도록 고치기위해 + 외부 HTTP 리다이렉션한다. 예를 들어 아래 규칙은 + <code>/~user</code>를 기준이 되는 <code>/u/user</code>로 + 대체하고, <code>/u/user</code> 마지막에 슬래쉬가 없다면 + 추가한다.</p> + +<div class="example"><pre> +RewriteRule ^/<strong>~</strong>([^/]+)/?(.*) /<strong>u</strong>/$1/$2 [<strong>R</strong>] +RewriteRule ^/([uge])/(<strong>[^/]+</strong>)$ /$1/$2<strong>/</strong> [<strong>R</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>기준이 되는 호스트명</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd>이 규칙은 동일한 사이트에 도달할 수 있는 다른 호스트명 + 대신 특정 호스트명을 사용하도록 강제한다. 예를 들어, + <strong>example.com</strong> 대신 + <strong>www.example.com</strong>을 사용하도록 강제하고 + 싶다면 다음과 같은 규칙을 사용할 수 있다.</dd> + + <dt>해결책:</dt> + + <dd> +<div class="example"><pre> +# 80번이 아닌 포트에서 실행하는 사이트용 +RewriteCond %{HTTP_HOST} !^fully\.qualified\.domain\.name [NC] +RewriteCond %{HTTP_HOST} !^$ +RewriteCond %{SERVER_PORT} !^80$ +RewriteRule ^/(.*) http://fully.qualified.domain.name:%{SERVER_PORT}/$1 [L,R] + +# 그리고, 80번 포트에서 실행하는 사이트용 +RewriteCond %{HTTP_HOST} !^fully\.qualified\.domain\.name [NC] +RewriteCond %{HTTP_HOST} !^$ +RewriteRule ^/(.*) http://fully.qualified.domain.name/$1 [L,R] +</pre></div> + </dd> + </dl> + + + + <h3><code>DocumentRoot</code>를 옮긴 경우</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>웹서버의 <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>는 보통 URL + "<code>/</code>"과 직접 관련있다. 그러나 이곳에 모든 + 자료가 있지 않고, 자료가 다른 여러 곳에 흩어져있는 + 경우가 있다. 예를 들어 인트라넷 사이트에 (외부를 위한 + 홈페이지) <code>/e/www/</code>와 (인트라넷을 위한 + 홈페이지) <code>/e/sww/</code>가 있다고 하자. 이제 + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>가 + <code>/e/www/</code>이기때문에, 요청에서 페이지에 + 포함된 그림 등을 이곳에서 가져와야 한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>우리는 URL <code>/</code>를 <code>/e/www/</code>로 + 리다이렉션만 하면 된다. 사소해 보이지만 실제로 + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용해서만 가능하다. + (<code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> 등이 제공하는) URL + <em>Alias</em> 같은 전형적인 방법은 <em>앞부분</em>만 + 찾는다. <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>가 + 모든 URL의 앞부분이기때문에 이 방법을 사용하여 리다이렉션을 + 할 수 없다. <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용하면 + 진짜 간단하다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule <strong>^/$</strong> /e/www/ [<strong>R</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>마지막 슬래쉬 문제</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>디렉토리를 지칭하는 URL의 마지막 슬래쉬 문제가 + 없다면 모든 웹관리자는 환호할 것이다. 슬래쉬가 없다면, + 즉 <code>/~quux/foo/</code> 대신 <code>/~quux/foo</code>를 + 사용하면 서버가 <code>foo</code>라는 <em>파일</em>을 + 찾기때문에 오류가 발생한다. 파일이 디렉토리이기때문에 + 받아들이지 않는다. 대부분의 경우 보통 서버가 자동으로 + URL을 고치지만, 가끔 직접 해줘야 할 경우가 있다. 예를 + 들어, CGI 스크립트 등으로 복잡한 URL 재작성을 한 후에 + 그러하다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>이 미묘한 문제의 해결방법은 서버가 자동으로 마지막 + 슬래쉬를 추가하는 것이다. 브라우저가 나머지 그림 등을 + 올바로 요청할 수 있도록, 외부 리다이렉션을 해야 한다. + 내부 리다이렉션을 한다면 디렉토리 페이지에만 동작하여 + 이 페이지가 상대 URL로 포함하는 그림을 브라우저가 + 요청할때 찾을 수 없다. 예를 들어, 외부 리다이렉션을 + 사용하지 않을때 <code>/~quux/foo/index.html</code>에서 + <code>image.gif</code>를 요청하면 + <code>/~quux/image.gif</code>를 요청하게 된다!</p> + + <p>그래서 이를 해결하기위해 다음과 같이 설정한다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^foo<strong>$</strong> foo<strong>/</strong> [<strong>R</strong>] +</pre></div> + + <p>홈디렉토리의 최상위 <code>.htaccess</code> 파일에 + 다음과 같이 설정할 수도 있다. 그러나 처리하는데 부담이 + 된다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteCond %{REQUEST_FILENAME} <strong>-d</strong> +RewriteRule ^(.+<strong>[^/]</strong>)$ $1<strong>/</strong> [R] +</pre></div> + </dd> + </dl> + + + + <h3>일관된 URL 구조로 만든 웹클러스터</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>인트라넷 웹서버군의 모든 웹서버에 동일하고 일관된 + URL 구조를 만들고 싶다. 즉, 모든 (정의상 서버에 속하여 + 서버에 의존적인!) URL을 서버 <em>독립적으로</em> 만든다! + 웹 이름공간에 서버독립적인 동일한 구조를 부여해야 한다: + URL은 실제 서버를 지칭하면 안된다. 서버군이 자동으로 + 실제 서버로 유도한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>먼저 사용자, 그룹, 독립체의 위치 정보를 저장한 + (분산된) 외부맵에 실제 서버 정보를 얻어온다. 외부맵은 + 다음과 같은 형식이다</p> + +<div class="example"><pre> +user1 server_of_user1 +user2 server_of_user2 +: : +</pre></div> + + <p>우리는 이 정보를 각각 <code>map.xxx-to-host</code> + 파일에 저장했다. 다음으로 모든 서버에서 URL이 서버에 + 없다면 다음과 같은 URL을,</p> + +<div class="example"><pre> +/u/user/anypath +/g/group/anypath +/e/entity/anypath +</pre></div> + + <p>다음과 같이 리다이렉션한다</p> + +<div class="example"><pre> +http://physical-host/u/user/anypath +http://physical-host/g/group/anypath +http://physical-host/e/entity/anypath +</pre></div> + + <p>아래 규칙은 맵파일을 사용하여 이 작업을 한다 (server0은 + 맵에 항목이 없는 경우 사용할 기본서버라고 가정한다):</p> + +<div class="example"><pre> +RewriteEngine on + +RewriteMap user-to-host txt:/path/to/map.user-to-host +RewriteMap group-to-host txt:/path/to/map.group-to-host +RewriteMap entity-to-host txt:/path/to/map.entity-to-host + +RewriteRule ^/u/<strong>([^/]+)</strong>/?(.*) http://<strong>${user-to-host:$1|server0}</strong>/u/$1/$2 +RewriteRule ^/g/<strong>([^/]+)</strong>/?(.*) http://<strong>${group-to-host:$1|server0}</strong>/g/$1/$2 +RewriteRule ^/e/<strong>([^/]+)</strong>/?(.*) http://<strong>${entity-to-host:$1|server0}</strong>/e/$1/$2 + +RewriteRule ^/([uge])/([^/]+)/?$ /$1/$2/.www/ +RewriteRule ^/([uge])/([^/]+)/([^.]+.+) /$1/$2/.www/$3\ +</pre></div> + </dd> + </dl> + + + + <h3>홈디렉토리를 다른 웹서버로 이전</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>많은 웹관리자는 웹서버의 모든 홈디렉토리를 다른 + 웹서버로 이전한 경우 해결책을 물어본다. 이 방법은 + 이전 서버를 대체할 새로운 서버를 구성하는데 시간이 + 걸리는 경우에 필요하다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용하면 간단하다. + 이전 웹서버는 모든 <code>/~user/anypath</code> URL을 + <code>http://newserver/~user/anypath</code>로 + 리다이렉션하면 된다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^/~(.+) http://<strong>newserver</strong>/~$1 [R,L] +</pre></div> + </dd> + </dl> + + + + <h3>홈디렉토리 구조 만들기</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>사용자가 수천명인 사이트는 보통 홈디렉토리 구조를 + 만든다. 즉, 예를 들어 이름이 사용자명의 첫번째 문자인 + 하위디렉토리에 홈디렉토리를 둔다. 그래서, + <code>/~foo/anypath</code>는 + <code>/home/<strong>f</strong>/foo/.www/anypath</code>이고, + <code>/~bar/anypath</code>는 + <code>/home/<strong>b</strong>/bar/.www/anypath</code>이다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>물결표시가 있는 URL을 위와 같은 구조로 변환하기위해 + 다음 규칙을 사용한다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*) /home/<strong>$2</strong>/$1/.www$3 +</pre></div> + </dd> + </dl> + + + + <h3>파일시스템 재구성</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>이 예는 실로 하드코어적이다: 디렉토리별 + <code>RewriteRules</code>를 매우 많이 사용하여 자료 + 자체는 그대로 둔체로 웹에 자료를 자연스럽게 브라우징하도록 + 한다. 배경: 나는 1992년 부터 자유롭게 사용할 수 있는 + 유닉스 소프트웨어들을 <strong><em>net.sw</em></strong>에 + 모아두고 있었다. 이는 내가 컴퓨터과학을 공부하면서 + 여러해동안 여가시간에 시스템 관리자와 네트웍 관리자를 + 해왔기때문에 내 취미이자 일이다. 매주마다 새로 소프트웨어가 + 추가될 때마다 디렉토리를 깊게 만들어왔다:</p> + +<div class="example"><pre> +drwxrwxr-x 2 netsw users 512 Aug 3 18:39 Audio/ +drwxrwxr-x 2 netsw users 512 Jul 9 14:37 Benchmark/ +drwxrwxr-x 12 netsw users 512 Jul 9 00:34 Crypto/ +drwxrwxr-x 5 netsw users 512 Jul 9 00:41 Database/ +drwxrwxr-x 4 netsw users 512 Jul 30 19:25 Dicts/ +drwxrwxr-x 10 netsw users 512 Jul 9 01:54 Graphic/ +drwxrwxr-x 5 netsw users 512 Jul 9 01:58 Hackers/ +drwxrwxr-x 8 netsw users 512 Jul 9 03:19 InfoSys/ +drwxrwxr-x 3 netsw users 512 Jul 9 03:21 Math/ +drwxrwxr-x 3 netsw users 512 Jul 9 03:24 Misc/ +drwxrwxr-x 9 netsw users 512 Aug 1 16:33 Network/ +drwxrwxr-x 2 netsw users 512 Jul 9 05:53 Office/ +drwxrwxr-x 7 netsw users 512 Jul 9 09:24 SoftEng/ +drwxrwxr-x 7 netsw users 512 Jul 9 12:17 System/ +drwxrwxr-x 12 netsw users 512 Aug 3 20:15 Typesetting/ +drwxrwxr-x 10 netsw users 512 Jul 9 14:08 X11/ +</pre></div> + + <p>1996년 7월 이 저장소를 멋있는 웹 인터페이스를 통해 + 세상에 공개하기로 결정햇다. "멋있다"는 말은, 최상위 + 디렉토리에 CGI 스크립트를 두지 않고도, 저장소 계층구조를 + 직접 브라우질하길 바란다는 뜻이다. 왜? 저장소를 나중에 + FTP로도 접근할 수 있도록 만들 예정이였기때문에 웹이나 + CGI와 관련된 내용을 같이 두기 싫었다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>해결책은 두 부분으로 나뉜다: 먼저 디렉토리 수준에서 + 필요한 모든 페이지를 동적으로 만드는 CGI 스크립트가 + 필요하다. 나는 이 스크립트들을 다음과 같이 + <code>/e/netsw/.www/</code>에 두었다:</p> + +<div class="example"><pre> +-rw-r--r-- 1 netsw users 1318 Aug 1 18:10 .wwwacl +drwxr-xr-x 18 netsw users 512 Aug 5 15:51 DATA/ +-rw-rw-rw- 1 netsw users 372982 Aug 5 16:35 LOGFILE +-rw-r--r-- 1 netsw users 659 Aug 4 09:27 TODO +-rw-r--r-- 1 netsw users 5697 Aug 1 18:01 netsw-about.html +-rwxr-xr-x 1 netsw users 579 Aug 2 10:33 netsw-access.pl +-rwxr-xr-x 1 netsw users 1532 Aug 1 17:35 netsw-changes.cgi +-rwxr-xr-x 1 netsw users 2866 Aug 5 14:49 netsw-home.cgi +drwxr-xr-x 2 netsw users 512 Jul 8 23:47 netsw-img/ +-rwxr-xr-x 1 netsw users 24050 Aug 5 15:49 netsw-lsdir.cgi +-rwxr-xr-x 1 netsw users 1589 Aug 3 18:43 netsw-search.cgi +-rwxr-xr-x 1 netsw users 1885 Aug 1 17:41 netsw-tree.cgi +-rw-r--r-- 1 netsw users 234 Jul 30 16:35 netsw-unlimit.lst +</pre></div> + + <p><code>DATA/</code> 하위디렉토리에 위에서 말한 저장소가 + 있다. 실제 <strong><em>net.sw</em></strong>의 내용은 보통 + <code>rdist</code>를 사용하여 자동으로 가져온다. 두번째 + 부분이 남았다: 어떻게 이 두 구조를 하나의 자연스러운 + URL 구조로 연결하는가? 사용자에게 <code>DATA/</code> + 디렉토리를 감추고, URL마다 적절한 CGI 스크립트를 실행하고 + 싶다. 해결책은 다음과 같다: 먼저 서버의 <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>에서 공개된 + URL <code>/net.sw/</code>를 내부 경로 <code>/e/netsw</code>로 + 재작성하기위해 디렉토리별 설정파일에 다음과 같이 설정한다:</p> + +<div class="example"><pre> +RewriteRule ^net.sw$ net.sw/ [R] +RewriteRule ^net.sw/(.*)$ e/netsw/$1 +</pre></div> + + <p>첫번째 규칙은 마지막에 슬래쉬가 없는 요청을 위해서 + 사용했다! 두번째 규칙이 실제 작업을 한다. 그리고 디렉토리별 + 설정파일 <code>/e/netsw/.www/.wwwacl</code>에 결정적인 + 설정이 나온다:</p> + +<div class="example"><pre> +Options ExecCGI FollowSymLinks Includes MultiViews + +RewriteEngine on + +# 앞 부분이 /net.sw/ 로 접근한다 +RewriteBase /net.sw/ + +# 먼저 최상위 디렉토리를 +# cgi 스크립트로 재작성한다 +RewriteRule ^$ netsw-home.cgi [L] +RewriteRule ^index\.html$ netsw-home.cgi [L] + +# 브라우저가 디렉토리별 페이지를 요청한 경우 +# 하위디렉토리를 추출한다 +RewriteRule ^.+/(netsw-[^/]+/.+)$ $1 [L] + +# 이제 재작성을 마친다 +RewriteRule ^netsw-home\.cgi.* - [L] +RewriteRule ^netsw-changes\.cgi.* - [L] +RewriteRule ^netsw-search\.cgi.* - [L] +RewriteRule ^netsw-tree\.cgi$ - [L] +RewriteRule ^netsw-about\.html$ - [L] +RewriteRule ^netsw-img/.*$ - [L] + +# 다른 cgi 스크립트가 처리할 +# 하위디렉토리가 남았다 +RewriteRule !^netsw-lsdir\.cgi.* - [C] +RewriteRule (.*) netsw-lsdir.cgi/$1 +</pre></div> + + <p>해석을 위한 힌트:</p> + + <ol> + <li>네번째 부분에서 대체 필드('<code>-</code>')가 + 없고 <code>L</code> (last) 플래그가 있음을 주목하라</li> + + <li>마지막 부분에서 첫번째 규칙에 <code>!</code> + (not) 문자와 <code>C</code> (chain) 플래그를 주목하라</li> + + <li>마지막 규칙에서 기타 해당하지 않는 모든 경우를 + 잡아내는 패턴을 주목하라</li> + </ol> + </dd> + </dl> + + + + <h3>NCSA imagemap을 아파치 <code>mod_imap</code>으로</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>사람들은 NCSA 웹서버에서 현대적인 아파치 웹서버로 + 자연스럽게 옮겨가길 바란다. 그래서 오래된 NCSA + <code>imagemap</code> 프로그램을 사용한 페이지를 현대적인 + 아파치 <code class="module"><a href="../mod/mod_imap.html">mod_imap</a></code>로 처리하길 바란다. + 문제는 <code>imagemap</code> 프로그램을 + <code>/cgi-bin/imagemap/path/to/page.map</code>과 + 같이 참조하는 하이퍼링크가 많다는 것이다. 아파치는 + <code>/path/to/page.map</code>과 같은 요청을 받아야 + 한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>모든 요청에서 앞부분을 동적으로 제거하는 전역 규칙을 + 사용한다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^/cgi-bin/imagemap(.*) $1 [PT] +</pre></div> + </dd> + </dl> + + + + <h3>여러 디렉토리에서 페이지 검색</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>가끔 웹서버가 여러 디렉토리에서 파일을 찾아야 할 + 때가 있다. 이 경우 MultiViews나 다른 방법은 도움이 + 안된다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>여러 디렉토리에서 파일을 찾는 규칙을 직접 프로그램한다.</p> + +<div class="example"><pre> +RewriteEngine on + +# 먼저 custom/에서 찾길 시도하고... +# ...찾으면 끝! +RewriteCond /your/docroot/<strong>dir1</strong>/%{REQUEST_FILENAME} -f +RewriteRule ^(.+) /your/docroot/<strong>dir1</strong>/$1 [L] + +# 두번째로 pub/에서 찾길 시도한다... +# ...찾으면 끝! +RewriteCond /your/docroot/<strong>dir2</strong>/%{REQUEST_FILENAME} -f +RewriteRule ^(.+) /your/docroot/<strong>dir2</strong>/$1 [L] + +# 못찾으면 다른 Alias나 ScriptAlias 지시어 등으로 진행한다. +RewriteRule ^(.+) - [PT] +</pre></div> + </dd> + </dl> + + + + <h3>URL에 따라 환경변수를 설정한다</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>요청들간에 상태정보를 유지하기위해 URL에 정보를 + 인코딩하는 방법도 있다. 그러나 단지 이 정보를 제거하기위해 + 모든 페이지에 CGI wrapper를 사용하고 싶지 않다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>재작성 규칙을 사용하여 상태정보를 추출하고, 추출한 + 정보를 나중에 XSSI나 CGI에서 사용하기위해 환경변수에 + 저장한다. 그래서 URL <code>/foo/S=java/bar/</code>는 + <code>/foo/bar/</code>로 변환되고 <code>STATUS</code>라는 + 환경변수 값을 "java"로 설정한다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteRule ^(.*)/<strong>S=([^/]+)</strong>/(.*) $1/$3 [E=<strong>STATUS:$2</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>가상 사용자 호스트</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>가상호스트를 사용하지 않고 같은 컴퓨터로 DNS A + 레코드를 설정하여 + <code>www.<strong>username</strong>.host.domain.com</code>을 + 사용자의 홈페이지로 제공하고 싶다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>HTTP/1.0 요청의 경우 방법이 없지만, Host: HTTP + 헤더를 포함한 HTTP/1.1 요청은 다음 규칙을 사용하여 + 내부적으로 <code>http://www.username.host.com/anypath</code>를 + <code>/home/username/anypath</code>로 재작성할 수 + 있다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{<strong>HTTP_HOST</strong>} ^www\.<strong>[^.]+</strong>\.host\.com$ +RewriteRule ^(.+) %{HTTP_HOST}$1 [C] +RewriteRule ^www\.<strong>([^.]+)</strong>\.host\.com(.*) /home/<strong>$1</strong>$2 +</pre></div> + </dd> + </dl> + + + + <h3>홈디렉토리를 외부 서버로 리다이렉션</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>지역 도메인 <code>ourdomain.com</code> 밖에서 요청이 + 들어오면 홈디렉토리 URL을 다른 웹서버 + <code>www.somewhere.com</code>으로 리다리렉션하길 + 바란다. 종종 가상호스트 사용장소에서 사용한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>재작성 조건을 사용하면 된다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{REMOTE_HOST} <strong>!^.+\.ourdomain\.com$</strong> +RewriteRule ^(/~.+) http://www.somewhere.com/$1 [R,L] +</pre></div> + </dd> + </dl> + + + + <h3>실패한 URL을 다른 웹서버로 리다이렉션</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>URL 재작성에 대해서 웹서버 A에 해당 파일이 없는 + 경우 웹서버 B로 요청을 리다이렉션하는 방법을 자주 + 물어본다. 보통 Perl로 작성한 <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> CGI 스크립트를 + 사용하지만, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용하는 + 방법도 있다. 그러나 성능은 <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> CGI 스크립트보다 + 떨어짐을 명심하라!</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>첫번째 방법은 빠르지만 유연성이 떨어지고 완전하지 + 않다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond /your/docroot/%{REQUEST_FILENAME} <strong>!-f</strong> +RewriteRule ^(.+) http://<strong>webserverB</strong>.dom/$1 +</pre></div> + + <p>이 방법의 단점은 <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> 안에 있는 페이지만 + 가능하다는 점이다. (예를 들어 홈디렉토리 등을 위해) + 조건을 추가할 수 있지만, 더 좋은 방법이 있다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{REQUEST_URI} <strong>!-U</strong> +RewriteRule ^(.+) http://<strong>webserverB</strong>.dom/$1 +</pre></div> + + <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>의 URL 전방참조(look-ahead)를 + 사용한다. 그래서 모든 URL에 동작하고 안전하다. 그러나 + 모든 요청마다 내부 하위요청을 한번 더 하기때문에 웹서버 + 성능에 악영향을 준다. 그래서 강력한 CPU에서 웹서버를 + 실행한다면 사용하라. 컴퓨터가 느리다면 첫번째 방법이나 + 더 나은 <code class="directive"><a href="../mod/core.html#errordocument">ErrorDocument</a></code> + CGI 스크립트를 사용하라.</p> + </dd> + </dl> + + + + <h3>확장 리다이렉션</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>가끔 리다이렉션하는 URL을 더 조절할 필요가 있다. + 아파치 내부 URL escape 함수는 "<code>url#anchor</code>" + 같은 URL의 anchor도 escape한다. 아파치의 + <code>uri_escape()</code> 함수는 우물정자(#)도 같이 + escape하므로 사용할 수 없다. 그러면 어떻게 이런 URL로 + 리다이렉션할 수 있나?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>직접 리다이렉션하는 NPH-CGI 스크립트를 사용한 해결책이 + 필요하다. escape를 하지 않기때문이다 (NPH=non-parseable + headers). 먼저 다음 서버설정을 하여 (재작성 규칙의 + 끝부분에 사용해야 한다) 새로운 URL scheme + <code>xredirect:</code>를 도입한다:</p> + +<div class="example"><pre> +RewriteRule ^xredirect:(.+) /path/to/nph-xredirect.cgi/$1 \ + [T=application/x-httpd-cgi,L] +</pre></div> + + <p>그러면 <code>xredirect:</code>로 시작하는 모든 URL은 + <code>nph-xredirect.cgi</code> 프로그램을 통하게 된다. + 프로그램은 다음과 같다:</p> + +<div class="example"><pre> +#!/path/to/perl +## +## nph-xredirect.cgi -- NPH/CGI script for extended redirects +## Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved. +## + +$| = 1; +$url = $ENV{'PATH_INFO'}; + +print "HTTP/1.0 302 Moved Temporarily\n"; +print "Server: $ENV{'SERVER_SOFTWARE'}\n"; +print "Location: $url\n"; +print "Content-type: text/html\n"; +print "\n"; +print "<html>\n"; +print "<head>\n"; +print "<title>302 Moved Temporarily (EXTENDED)</title>\n"; +print "</head>\n"; +print "<body>\n"; +print "<h1>Moved Temporarily (EXTENDED)</h1>\n"; +print "The document has moved <a HREF=\"$url\">here</a>.<p>\n"; +print "</body>\n"; +print "</html>\n"; + +##EOF## +</pre></div> + + <p>그러면 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>가 직접 받지못하는 + 모든 URL scheme으로 리다이렉션할 수 있다. 예를 들어, + 다음과 같이 <code>news:newsgroup</code>으로 리다이렉션할 + 수 있다</p> + +<div class="example"><pre> +RewriteRule ^anyurl xredirect:news:newsgroup +</pre></div> + + <div class="note">주의: 위의 특별한 "통과" 규칙을 사용하여 + <code>xredirect:</code>를 마지막에 확장해야 하기때문에 + 규칙에 <code>[R]</code>이나 <code>[R,L]</code>을 사용하면 + 안된다.</div> + </dd> + </dl> + + + + <h3>저장소 접근 중계(multiplexer)</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p><a href="http://www.perl.com/CPAN">http://www.perl.com/CPAN</a>에 + 있는 대단한 CPAN (Comprehensive Perl Archive Network)을 + 아는가? 이 주소는 세계에 흩어진 여러 CPAN 미러 FTP + 서버중 클라이언트에 가까이 있는 서버로 리다이렉션한다. + 이를 FTP 접근 중계 서비스라고 한다. CPAN은 CGI 스크립트를 + 사용하지만, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용하여 + 비슷하게 만들 수 있을까?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>먼저 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> 3.0.0 버전부터 + 리다이렉션에 "<code>ftp:</code>" scheme을 사용할 수 + 있다. 다음으로 클라이언트의 최상위 도메인을 <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code>과 같이 + 사용하여 위치를 추정할 수 있다. 복잡히 엮인 규칙에서 + 최상위 도메인을 중계맵의 키로 사용한다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap multiplex txt:/path/to/map.cxan +RewriteRule ^/CxAN/(.*) %{REMOTE_HOST}::$1 [C] +RewriteRule ^.+\.<strong>([a-zA-Z]+)</strong>::(.*)$ ${multiplex:<strong>$1</strong>|ftp.default.dom}$2 [R,L] +</pre></div> + +<div class="example"><pre> +## +## map.cxan -- Multiplexing Map for CxAN +## + +de ftp://ftp.cxan.de/CxAN/ +uk ftp://ftp.cxan.uk/CxAN/ +com ftp://ftp.cxan.com/CxAN/ + : +##EOF## +</pre></div> + </dd> + </dl> + + + + <h3>시간에 따른 재작성</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>시간에 따라 다른 내용을 서비스하는 경우 많은 웹관리자는 + 잠시 특별한 페이지로 리다이렉션하기위해 CGI 스크립트를 + 사용한다. <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>로는 어떻게 + 할 수 있는가?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>재작성 조건에서 사용할 수 있는 여러 <code>TIME_xxx</code> + 변수가 있다. 변수와 특별한 사전순서 비교 + <code><STRING</code>, <code>>STRING</code>, + <code>=STRING</code>을 사용하여 시간에 따라 리다이렉션할 + 수 있다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteCond %{TIME_HOUR}%{TIME_MIN} >0700 +RewriteCond %{TIME_HOUR}%{TIME_MIN} <1900 +RewriteRule ^foo\.html$ foo.day.html +RewriteRule ^foo\.html$ foo.night.html +</pre></div> + + <p>URL <code>foo.html</code>을 요청하면 + <code>07:00-19:00</code> 동안 <code>foo.day.html</code> + 내용을 서비스하고, 나머지 시간 동안 + <code>foo.night.html</code> 내용을 서비스한다. 홈페이지에서 + 사용하기 좋은 기능이다...</p> + </dd> + </dl> + + + + <h3>YYYY를 XXXX로 이전한 경우 역호환</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>여러 <code>.html</code> 파일을 <code>.phtml</code>로 + 변환하는 등 <code>document.YYYY</code>를 + <code>document.XXXX</code>로 이전한후 역호환(backward + compatibility) URL을 (가상적으로 존재하게) 만들 수 + 있나?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>이름을 기본이름으로 재작성한후 새로운 확장자를 + 가진 파일이 있는지 검사한다. 있다면 그 파일명을 사용하고, + 없으면 URL을 원래 상태로 재작성한다.</p> + + +<div class="example"><pre> +# 문서.html 이 없고 +# 문서.phtml 만 있는 경우 +# 문서.html 을 문서.phtml 로 +# 재작성하는 역호환 규칙 +RewriteEngine on +RewriteBase /~quux/ +# 기본이름을 찾고, 찾았다는 사실을 기억한다 +RewriteRule ^(.*)\.html$ $1 [C,E=WasHTML:yes] +# 파일이 있다면 문서.phtml 로 재작성한다 +RewriteCond %{REQUEST_FILENAME}.phtml -f +RewriteRule ^(.*)$ $1.phtml [S=1] +# 아니면 앞에서 찾은 기본이름을 되돌린다 +RewriteCond %{ENV:WasHTML} ^yes$ +RewriteRule ^(.*)$ $1.html +</pre></div> + </dd> + </dl> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="content" id="content">컨텐츠 다루기</a></h2> + + + + <h3>새로 이전 (감추기)</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>최근 <code>foo.html</code>을 <code>bar.html</code>로 + 변경하고 역호환성을 위해 이전 URL을 계속 제공하고 + 싶다고 가정하자. 사용자는 이전 URL이 변경되었다는 + 사실을 눈치채지 못한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>다음 규칙으로 이전 URL을 내부적으로 새로운 URL로 + 재작성한다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>foo</strong>\.html$ <strong>bar</strong>.html +</pre></div> + </dd> + </dl> + + + + <h3>새로 이전 (알리기)</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>다시 <code>foo.html</code>을 <code>bar.html</code>로 + 변경하고 역호환성을 위해 이전 URL을 계속 제공하고 + 싶다고 가정하자. 그러나 이제는 이전 URL을 사용하면 + 사용자에게 새로운 URL을 힌트로 알려준다. 즉, 브라우저 + 주소창이 변한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>새로운 URL로 HTTP 리다이렉션하다. 그러면 브라우저가 + 새로운 URL를 보이고 변경사실을 사용자가 알게된다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>foo</strong>\.html$ <strong>bar</strong>.html [<strong>R</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>브라우저에 따른 내용</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>최소한 중요한 최상위 페이지는 브라우저에 최적화된 + 내용으로 서비스해야할 경우가 있다. 즉, 최신 Netscape + 브라우저에게는 최상의 버전을, Lynx 브라우저에게는 + 최저 버전을, 나머지 브라우저에는 평균적인 버전을 + 제공한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>브라우저가 내용협상을 위해 자신의 종류에 대한 정보를 + 제공하지 않기때문에 내용협상을 사용할 수 없다. 대신 + HTTP "User-Agent" 헤더를 사용한다. 다음 규칙은 HTTP + "User-Agent" 헤더가 "Mozilla/3"으로 시작하면 + <code>foo.html</code> 페이지를 <code>foo.NS.html</code>로 + 재작성하고 재작성을 중단한다. 브라우저가 "Lynx"나 + "Mozilla" 버전 1 혹은 2라면 URL은 + <code>foo.20.html</code>이 된다. 나머지 브라우저는 + <code>foo.32.html</code> 페이지를 받는다. 아래 규칙이 + 이 작업을 한다:</p> + +<div class="example"><pre> +RewriteCond %{HTTP_USER_AGENT} ^<strong>Mozilla/3</strong>.* +RewriteRule ^foo\.html$ foo.<strong>NS</strong>.html [<strong>L</strong>] + +RewriteCond %{HTTP_USER_AGENT} ^<strong>Lynx/</strong>.* [OR] +RewriteCond %{HTTP_USER_AGENT} ^<strong>Mozilla/[12]</strong>.* +RewriteRule ^foo\.html$ foo.<strong>20</strong>.html [<strong>L</strong>] + +RewriteRule ^foo\.html$ foo.<strong>32</strong>.html [<strong>L</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>동적 미러</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>외부 호스트에 우리 사이트로 가져오고 싶은 좋은 + 웹페이지가 있다고 가정하자. FTP 서버의 경우 직접 외부 + 자료의 최신복사본을 유지하는 <code>mirror</code> 프로그램을 + 사용할 수 있고, 웹서버라면 HTTP로 비슷한 작업을 하는 + <code>webcopy</code> 프로그램을 사용할 수 있다. 그러나 + 두 방법 모두 단점이 있다: 복사본은 가끔씩 프로그램을 + 실행해줄 때만 최신판으로 유지된다. 직접 구성해야하는 + 정적인 미러가 아니라면 좋겠다. 대신 (외부 호스트에서 + 자료가 갱신되면) 필요할때 자동으로 자료를 갱신하는 + 동적 미러가 필요하다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>이를 위해 <dfn>Proxy Throughput</dfn> 기능을 (플래그 + <code>[P]</code>) 사용하여 외부 웹페이지 혹은 외부 + 웹공간 전체를 우리 이름공간으로 대응한다:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>hotsheet/</strong>(.*)$ <strong>http://www.tstimpreso.com/hotsheet/</strong>$1 [<strong>P</strong>] +</pre></div> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^<strong>usa-news\.html</strong>$ <strong>http://www.quux-corp.com/news/index.html</strong> [<strong>P</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>동적 역미러</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd>...</dd> + + <dt>해결책:</dt> + + <dd> +<div class="example"><pre> +RewriteEngine on +RewriteCond /mirror/of/remotesite/$1 -U +RewriteRule ^http://www\.remotesite\.com/(.*)$ /mirror/of/remotesite/$1 +</pre></div> + </dd> + </dl> + + + + <h3>없는 자료를 인트라넷에서 가져오기</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>실제 자료를 방화벽이 보호하는 (내부) 인트라넷 웹서버에 + (<code>www2.quux-corp.dom</code>) 저장하면서, 기업의 + (외부) 인터넷 웹서버를 (<code>www.quux-corp.dom</code>) + 실행하는 것처럼 보이게 한다. 외부 웹서버는 요청한 + 자료를 내부 웹서버에서 가져온다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>먼저 방화벽이 내부 웹서버를 보호하고 외부 웹서버만이 + 내부 웹서버에서 자료를 얻을 수 있게 한다. 다음과 같이 + 패킷필터링 방화벽을 설정한다:</p> + +<div class="example"><pre> +<strong>ALLOW</strong> Host www.quux-corp.dom Port >1024 --> Host www2.quux-corp.dom Port <strong>80</strong> +<strong>DENY</strong> Host * Port * --> Host www2.quux-corp.dom Port <strong>80</strong> +</pre></div> + + <p>실제 설정문법에 알맞게 고쳐라. 없는 자료를 내부적으로 + proxy throughput 기능을 통해 요청하는 + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> 규칙을 작성한다:</p> + +<div class="example"><pre> +RewriteRule ^/~([^/]+)/?(.*) /home/$1/.www/$2 +RewriteCond %{REQUEST_FILENAME} <strong>!-f</strong> +RewriteCond %{REQUEST_FILENAME} <strong>!-d</strong> +RewriteRule ^/home/([^/]+)/.www/?(.*) http://<strong>www2</strong>.quux-corp.dom/~$1/pub/$2 [<strong>P</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>로드밸런싱 (부하 분산하기)</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p><code>www.foo.com</code>의 통신량을 + <code>www[0-5].foo.com</code> (총 서버 6대)으로 분산하고 + 싶다. 어떻게 하는가?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>매우 다양한 방법으로 이 문제를 해결할 수 있다. + 먼저 DNS를 사용한 잘 알려진 방법을 설명하고, + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>를 사용하는 경우를 살펴보자:</p> + + <ol> + <li> + <strong>DNS Round-Robin</strong> + + <p>가장 간단한 로드밸런싱 방법은 <code>BIND</code>의 + DNS round-robin 방식을 사용하는 것이다. 다음과 + 같이 DNS A(address) 레코드에 + <code>www[0-9].foo.com</code>을 설정한다.</p> + +<div class="example"><pre> +www0 IN A 1.2.3.1 +www1 IN A 1.2.3.2 +www2 IN A 1.2.3.3 +www3 IN A 1.2.3.4 +www4 IN A 1.2.3.5 +www5 IN A 1.2.3.6 +</pre></div> + + <p>그리고 다음 항목을 추가한다:</p> + +<div class="example"><pre> +www IN CNAME www0.foo.com. + IN CNAME www1.foo.com. + IN CNAME www2.foo.com. + IN CNAME www3.foo.com. + IN CNAME www4.foo.com. + IN CNAME www5.foo.com. + IN CNAME www6.foo.com. +</pre></div> + + <p>잘못된 것처럼 보이지만, 실제로 <code>BIND</code>의 + 의도된 기능이다. 이제 <code>www.foo.com</code>을 + 찾으면, <code>BIND</code>는 매번 순서를 조금씩 + 바꿔가며 <code>www0-www6</code>을 반환한다. 그래서 + 클라이언트들을 여러 서버로 분산한다. 그러나 DNS + 검색 결과가 네트웍의 다른 네임서버에 캐쉬되여 + <code>www.foo.com</code>을 찾은 결과가 특정 + <code>wwwN.foo.com</code>이면 클라이언트의 다음 + 요청들도 같은 <code>wwwN.foo.com</code>으로 + 보내지기때문에 완벽한 로드밸런싱 기법이 아님을 + 주의하라. 그러나 크게 보면 요청이 여러 웹서버에 + 분산되므로 효과가 좋다.</p> + </li> + + <li> + <strong>DNS 로드밸런싱</strong> + + <p><a href="http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html">http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html</a>에 + 있는 <code>lbnamed</code> 프로그램을 사용하여 + 정교한 DNS기반 로드밸런싱을 할 수 있다. DNS가 + 실제 로드밸런싱을 하도록 만드는 여러 도구와 Perl + 5 프로그램이다.</p> + </li> + + <li> + <strong>Proxy Throughput Round-Robin</strong> + + <p>이 방법은 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>와 proxy + throughput 기능을 사용한다. 먼저 DNS에 다음 항목을 + 사용하여 <code>www0.foo.com</code>이 실제 + <code>www.foo.com</code>을 전담하게 한다</p> + +<div class="example"><pre> +www IN CNAME www0.foo.com. +</pre></div> + + <p>그리고 <code>www0.foo.com</code>을 프록시전용 + 서버로 변경한다. 즉, URL을 받으면 서버는 내부 + 프록시를 통해 다른 5대 서버중 (<code>www1-www5</code>) + 한대로 보내기만 한다. 이를 위해 먼저 모든 URL을 + 로드밸런싱 스크립트 <code>lb.pl</code>로 보내는 + 규칙을 만든다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap lb prg:/path/to/lb.pl +RewriteRule ^/(.+)$ ${lb:$1} [P,L] +</pre></div> + + <p><code>lb.pl</code>을 작성한다:</p> + +<div class="example"><pre> +#!/path/to/perl +## +## lb.pl -- 로드밸런싱 스크립트 +## + +$| = 1; + +$name = "www"; # 기본 호스트명 +$first = 1; # 첫번째 서버 (자신이 0이기 때문에, 0을 사용하지 않는다) +$last = 5; # round-robin에서 마지막 서버 +$domain = "foo.dom"; # 도메인명 + +$cnt = 0; +while (<STDIN>) { + $cnt = (($cnt+1) % ($last+1-$first)); + $server = sprintf("%s%d.%s", $name, $cnt+$first, $domain); + print "http://$server/$_"; +} + +##EOF## +</pre></div> + + <div class="note">마지막 주의: 왜 이 방법이 유용한가? + <code>www0.foo.com</code>에 부담이 가지않는가? + 물론, 부담이 된다. 그러나 단순한 proxy throughput + 요청만 하기때문에 괜찮다! 모든 SSI, CGI, ePerl + 등은 전적으로 다른 서버가 처리한다. 이것이 핵심이다.</div> + </li> + + <li> + <strong>하드웨어/TCP Round-Robin</strong> + + <p>하드웨어를 사용한 해결책도 있다. Cisco는 TCP/IP + 수준에서 로드밸런싱을 하는 LocalDirector라는 괴물을 + 판다. 실제로는 웹서버군 앞단에 위치하는 일종의 + 회로수준 게이트웨이다. 자금이 충분하고 고성능 + 해결책이 필요하다면 이것을 사용하라.</p> + </li> + </ol> + </dd> + </dl> + + + + <h3>새로운 MIME-type, 새로운 서비스</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>네트웍에는 멋진 CGI 프로그램들이 많다. 그러나 사용하기 + 번거러워서 많은 웹관리자가 사용하지 않는다. 아파치의 + MIME-type에 따른 Action 핸들러 기능도 CGI 프로그램이 + 특별한 URL을 (정확히 <code>PATH_INFO</code>와 + <code>QUERY_STRINGS</code>) 프로그램의 입력으로 사용하지 + 않을 때만 적절하다. 먼저, 확장자가 (secure CGI를 줄여) + <code>.scgi</code>인 파일을 유명한 <code>cgiwrap</code> + 프로그램으로 처리하기위해 새로운 type을 설정한다. + 문제는 (위에서 본) 일관된 URL 구조를 사용하는 경우 + 사용자 홈디렉토리가 <code>/u/user/foo/bar.scgi</code>같은 + URL인 점이다. <code>cgiwrap</code>는 + <code>/~user/foo/bar.scgi/</code> 형식의 URL을 + 원하기때문이다. 다음 규칙이 문제를 해결한다:</p> + +<div class="example"><pre> +RewriteRule ^/[uge]/<strong>([^/]+)</strong>/\.www/(.+)\.scgi(.*) ... +... /internal/cgi/user/cgiwrap/~<strong>$1</strong>/$2.scgi$3 [NS,<strong>T=application/x-http-cgi</strong>] +</pre></div> + + <p>이제 다른 멋진 프로그램, (URL 하위트리에 대한 + <code>access.log</code>를 출력하는) <code>wwwlog</code>와 + (URL 하위트리에 Glimpse를 실행하는) <code>wwwidx</code>가 + 있다고 가정하자. 우리는 프로그램에게 작업할 대상인 + URL 영역을 알려줘야 한다. 그러나 요청할때마다 항상 + 적어줘야 하기때문에 깔끔하지 않다. 즉, 보통 + <code>/u/user/foo/</code>에 대해 <code>swwidx</code> + 프로그램을 실행한다면 다음과 같은 링크를 사용한다</p> + +<div class="example"><pre> +/internal/cgi/user/swwidx?i=/u/user/foo/ +</pre></div> + + <p>깔끔하지 않다. 링크에 영역의 위치<strong>와</strong> + CGI 위치를 <strong>모두</strong> 적어야 하기때문이다. + 영역을 재구성한다면 여러 하이퍼링크를 수정하는데 많은 + 시간이 걸릴 것이다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>해결책은 자동으로 적절한 CGI를 실행하는 새로운 + 특별한 URL 형식을 만드는 것이다. 다음과 같이 설정한다:</p> + +<div class="example"><pre> +RewriteRule ^/([uge])/([^/]+)(/?.*)/\* /internal/cgi/user/wwwidx?i=/$1/$2$3/ +RewriteRule ^/([uge])/([^/]+)(/?.*):log /internal/cgi/user/wwwlog?f=/$1/$2$3 +</pre></div> + + <p>이제 <code>/u/user/foo/</code>을 검색하는 링크는 + 다음과 같다</p> + +<div class="example"><pre> +HREF="*" +/u/user/foo/* (???) +</pre></div> + + <p>내부적으로 다음과 같이 자동변환된다</p> + +<div class="example"><pre> +/internal/cgi/user/wwwidx?i=/u/user/foo/ +</pre></div> + + <p>같은 방법으로 링크 뒤에 <code>:log</code>를 사용하여 + 접근 로그 CGI 프로그램을 실행할 수 있다.</p> + </dd> + </dl> + + + + <h3>정적에서 동적으로</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>어떻게 브라우저와 사용자가 모르게 자연스럽게 정적 + 페이지 <code>foo.html</code>을 동적인 <code>foo.cgi</code>로 + 변경할 수 있나.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>URL을 CGI 스크립트로 재작성하고, MIME-type을 수정하여 + CGI 스크립트로 실행하게 한다. 그래서 + <code>/~quux/foo.html</code>를 요청하면 내부적으로 + <code>/~quux/foo.cgi</code>를 실행하게 된다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteBase /~quux/ +RewriteRule ^foo\.<strong>html</strong>$ foo.<strong>cgi</strong> [T=<strong>application/x-httpd-cgi</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>즉석 컨텐츠 재생성</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>이 방법은 실로 비기이다: 동적으로 페이지를 생성하지만, + 정적으로 페이지를 서비스한다. 즉, 페이지는 순수하게 + (파일시스템에서 읽은 내용을 그대로) 정적 페이지로 + 전달되지만, 없을 경우 웹서버가 동적으로 생성한다. + 그러면 누가 (혹은 cron 작업이) 정적 컨텐츠를 지우지않는 + 한 CGI가 생성한 페이지를 정적으로 서비스한다. 컨텐츠를 + 지우면 내용을 갱신한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + 다음 규칙을 사용한다: + +<div class="example"><pre> +RewriteCond %{REQUEST_FILENAME} <strong>!-s</strong> +RewriteRule ^page\.<strong>html</strong>$ page.<strong>cgi</strong> [T=application/x-httpd-cgi,L] +</pre></div> + + <p>여기서 <code>page.html</code>를 요청할때 + <code>page.html</code>이 없거나 파일크기가 0인 경우 + 내부적으로 <code>page.cgi</code>를 실행한다. 여기서 + 비결은 <code>page.cgi</code>가 일반적인 CGI 스크립트와 + 같이 <code>STDOUT</code>에 출력하고, 추가로 출력을 + <code>page.html</code> 파일에 적는다. 한번 실행한후 + 서버는 <code>page.html</code>의 정보를 보낸다. 웹관리자가 + 강재로 내용을 갱신하고 싶다면, (보통 cron 작업이) + <code>page.html</code>을 지우기만 하면 된다.</p> + </dd> + </dl> + + + + <h3>자동으로 새로 고침하는 문서</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>복잡한 웹페이지를 만들때 편집자가 내용을 수정할 + 때마다 자동으로 페이지를 새로 고침하는 웹브라우저가 + 있으면 얼마나 좋을까? 불가능한가?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>가능하다! MIME multipart 기능과 웹서버 NPH 기능, + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>의 URL 조작 능력을 결합하면 + 된다. 먼저, 새로운 URL 기능을 만든다: URL에 + <code>:refresh</code>를 추가하기만 하면 파일시스템에서 + 수정될 때마다 새로 고침한다.</p> + +<div class="example"><pre> +RewriteRule ^(/[uge]/[^/]+/?.*):refresh /internal/cgi/apache/nph-refresh?f=$1 +</pre></div> + + <p>이제 다음 URL에 접근하면</p> + +<div class="example"><pre> +/u/foo/bar/page.html:refresh +</pre></div> + + <p>다음 URL을 내부적으로 부른다</p> + +<div class="example"><pre> +/internal/cgi/apache/nph-refresh?f=/u/foo/bar/page.html +</pre></div> + + <p>이제 NPH-CGI 스크립트만 남았다. 보통 "독자에게 + 연습으로 남겨둠"이라고 말하지만 ;-) 나는 이것도 제공한다.</p> + +<div class="example"><pre> +#!/sw/bin/perl +## +## nph-refresh -- NPH/CGI script for auto refreshing pages +## Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved. +## +$| = 1; + +# split the QUERY_STRING variable +@pairs = split(/&/, $ENV{'QUERY_STRING'}); +foreach $pair (@pairs) { + ($name, $value) = split(/=/, $pair); + $name =~ tr/A-Z/a-z/; + $name = 'QS_' . $name; + $value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C", hex($1))/eg; + eval "\$$name = \"$value\""; +} +$QS_s = 1 if ($QS_s eq ''); +$QS_n = 3600 if ($QS_n eq ''); +if ($QS_f eq '') { + print "HTTP/1.0 200 OK\n"; + print "Content-type: text/html\n\n"; + print "&lt;b&gt;ERROR&lt;/b&gt;: No file given\n"; + exit(0); +} +if (! -f $QS_f) { + print "HTTP/1.0 200 OK\n"; + print "Content-type: text/html\n\n"; + print "&lt;b&gt;ERROR&lt;/b&gt;: File $QS_f not found\n"; + exit(0); +} + +sub print_http_headers_multipart_begin { + print "HTTP/1.0 200 OK\n"; + $bound = "ThisRandomString12345"; + print "Content-type: multipart/x-mixed-replace;boundary=$bound\n"; + &print_http_headers_multipart_next; +} + +sub print_http_headers_multipart_next { + print "\n--$bound\n"; +} + +sub print_http_headers_multipart_end { + print "\n--$bound--\n"; +} + +sub displayhtml { + local($buffer) = @_; + $len = length($buffer); + print "Content-type: text/html\n"; + print "Content-length: $len\n\n"; + print $buffer; +} + +sub readfile { + local($file) = @_; + local(*FP, $size, $buffer, $bytes); + ($x, $x, $x, $x, $x, $x, $x, $size) = stat($file); + $size = sprintf("%d", $size); + open(FP, "&lt;$file"); + $bytes = sysread(FP, $buffer, $size); + close(FP); + return $buffer; +} + +$buffer = &readfile($QS_f); +&print_http_headers_multipart_begin; +&displayhtml($buffer); + +sub mystat { + local($file) = $_[0]; + local($time); + + ($x, $x, $x, $x, $x, $x, $x, $x, $x, $mtime) = stat($file); + return $mtime; +} + +$mtimeL = &mystat($QS_f); +$mtime = $mtime; +for ($n = 0; $n &lt; $QS_n; $n++) { + while (1) { + $mtime = &mystat($QS_f); + if ($mtime ne $mtimeL) { + $mtimeL = $mtime; + sleep(2); + $buffer = &readfile($QS_f); + &print_http_headers_multipart_next; + &displayhtml($buffer); + sleep(5); + $mtimeL = &mystat($QS_f); + last; + } + sleep($QS_s); + } +} + +&print_http_headers_multipart_end; + +exit(0); + +##EOF## +</pre></div> + </dd> + </dl> + + + + <h3>대량의 가상호스트</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>가상호스트가 몇개만 있다면 아파치의 <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + 기능이 잘 동작한다. 그러나 가상호스트가 수백개 있는 + ISP라면 이 기능이 최선은 아니다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>이 기능을 제공하려면 <dfn>Proxy Throughput</dfn> + 기능을 (플래그 <code>[P]</code>) 사용하여 외부 웹페이지 + 혹은 전체 외부 웹영역을 우리의 이름공간에 대응한다:</p> + +<div class="example"><pre> +## +## vhost.map +## +www.vhost1.dom:80 /path/to/docroot/vhost1 +www.vhost2.dom:80 /path/to/docroot/vhost2 + : +www.vhostN.dom:80 /path/to/docroot/vhostN +</pre></div> + +<div class="example"><pre> +## +## httpd.conf +## + : +# 리다이렉트할때 정규 호스트명을 사용한다. +UseCanonicalName on + + : +# 가상호스트를 CLF 형식 앞에 추가한다 +CustomLog /path/to/access_log "%{VHOST}e %h %l %u %t \"%r\" %>s %b" + : + +# 주서버에서 재작성 엔진을 사용한다 +RewriteEngine on + +# 두 맵을 정의한다: 하나는 URL을 고치고, +# 다른 하나는 가상호스트별 DocumentRoot를 +# 정의한다. +RewriteMap lowercase int:tolower +RewriteMap vhost txt:/path/to/vhost.map + +# 이제 크고 복잡한 규칙 한개를 사용하여 +# 가상호스트로 대응한다. +# +# 1. 가상호스트들이 같이 사용하는 위치는 대응하지 않는다 +RewriteCond %{REQUEST_URI} !^/commonurl1/.* +RewriteCond %{REQUEST_URI} !^/commonurl2/.* + : +RewriteCond %{REQUEST_URI} !^/commonurlN/.* +# +# 2. 우리가 현재 사용하는 방법이 Host 헤더를 +# 가상호스트를 지원하므로 +# Host 헤더가 있는지 확인한다 +RewriteCond %{HTTP_HOST} !^$ +# +# 3. 호스트명을 소문자로 만든다 +RewriteCond ${lowercase:%{HTTP_HOST}|NONE} ^(.+)$ +# +# 4. vhost.map에서 호스트명을 찾고 +# 경로일때만 기억한다 +# (위에서 "NONE"은 아니다) +RewriteCond ${vhost:%1} ^(/.*)$ +# +# 5. 마지막으로 URL을 문서 위치로 대응하고 +# 로그에 남기기위해 가상호스트를 기억해 둔다 +RewriteRule ^/(.*)$ %1/$1 [E=VHOST:${lowercase:%{HTTP_HOST}}] + : +</pre></div> + </dd> + </dl> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="access" id="access">접근 제한</a></h2> + + + + <h3>로봇 막기</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>어떻게 하면 특정 웹공간의 페이지를 긁어모으는 귀찮은 + 로봇을 막을 수 있나? "Robot Exclusion Protocol" 항목을 + 저장한 <code>/robots.txt</code> 파일은 보통 이런 로봇을 + 막는데 충분하지 않다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>(아마도 디렉토리가 깊어서 로봇이 돌아다니면 서버에 + 부담이 큰 경우) 웹공간 <code>/~quux/foo/arc/</code>에 + 있는 URL들을 거부하는 규칙을 사용한다. 우리는 특정 + 로봇의 접근을 막아야 한다. 즉, 로봇을 실행하는 호스트를 + 막는 것으로는 불충분하며, 그 호스트의 사용자도 막아버리게 + 된다. User-Agent HTTP 헤더 정보도 비교한다.</p> + +<div class="example"><pre> +RewriteCond %{HTTP_USER_AGENT} ^<strong>NameOfBadRobot</strong>.* +RewriteCond %{REMOTE_ADDR} ^<strong>123\.45\.67\.[8-9]</strong>$ +RewriteRule ^<strong>/~quux/foo/arc/</strong>.+ - [<strong>F</strong>] +</pre></div> + </dd> + </dl> + + + + <h3>그림 퍼가기 방지</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p><code>http://www.quux-corp.de/~quux/</code>에 있는 + 페이지들이 GIF 그림을 포함한다고 가정하자. 이 그림이 + 멋있어서, 다른 사람들이 자신의 페이지에 직접 링크를 + 건다. 서버에 불필요한 부담이 되므로 막고 싶다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>그림을 100% 보호할 수는 없지만, 최소한 브라우저가 + HTTP Referer 헤더를 보내는 경우 제한할 수 있다.</p> + +<div class="example"><pre> +RewriteCond %{HTTP_REFERER} <strong>!^$</strong> +RewriteCond %{HTTP_REFERER} !^http://www.quux-corp.de/~quux/.*$ [NC] +RewriteRule <strong>.*\.gif$</strong> - [F] +</pre></div> + +<div class="example"><pre> +RewriteCond %{HTTP_REFERER} !^$ +RewriteCond %{HTTP_REFERER} !.*/foo-with-gif\.html$ +RewriteRule <strong>^inlined-in-foo\.gif$</strong> - [F] +</pre></div> + </dd> + </dl> + + + + <h3>호스트 거부</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>어떻게 외부에서 서버에 접근할 수 없는 호스트 목록을 + 설정할 수 있나?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>아파치 >= 1.3b6에서:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap hosts-deny txt:/path/to/hosts.deny +RewriteCond ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR] +RewriteCond ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND +RewriteRule ^/.* - [F] +</pre></div> + + <p>아파치 <= 1.3b6에서:</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap hosts-deny txt:/path/to/hosts.deny +RewriteRule ^/(.*)$ ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND}/$1 +RewriteRule !^NOT-FOUND/.* - [F] +RewriteRule ^NOT-FOUND/(.*)$ ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND}/$1 +RewriteRule !^NOT-FOUND/.* - [F] +RewriteRule ^NOT-FOUND/(.*)$ /$1 +</pre></div> + +<div class="example"><pre> +## +## hosts.deny +## +## 주의! 이것은 목록처럼 보이지만 목록이 아니라 맵이다. +## mod_rewrite는 이 정보를 키/값 쌍으로 해석하기때문에, +## 각 항목의 값 자리에 최소한 "-"가 필요하다. +## + +193.102.180.41 - +bsdti1.sdm.de - +192.76.162.40 - +</pre></div> + </dd> + </dl> + + + + <h3>프록시 거부</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>어떻게 특정 호스트 혹은 특정 호스트의 사용자가 + 아파치 프록시를 사용할 수 없도록 하나?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>먼저 아파치 웹서버를 컴파일할때 구성파일에서 + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>가 <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> + 아래에(!) 있어야 한다. 그러면 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>는 + <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> <em>이전에</em> 불린다. + 이제 다음과 같이 특정 호스트를 거부하도록 설정한다...</p> + +<div class="example"><pre> +RewriteCond %{REMOTE_HOST} <strong>^badhost\.mydomain\.com$</strong> +RewriteRule !^http://[^/.]\.mydomain.com.* - [F] +</pre></div> + + <p>...그리고 다음은 user@host에 따라 거부한다:</p> + +<div class="example"><pre> +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>^badguy@badhost\.mydomain\.com$</strong> +RewriteRule !^http://[^/.]\.mydomain.com.* - [F] +</pre></div> + </dd> + </dl> + + + + <h3>특별한 인증 방식</h3> + + + + <dl> + <dt>상활설명:</dt> + + <dd> + <p>가끔 매우 특별한 인증이 필요할 때가 있다. 예를 + 들어, 미리 설정해둔 사용자인지 검사한다. 이들에게만 + (<code class="module"><a href="../mod/mod_auth.html">mod_auth</a></code>의 Basic Auth를 사용한 + 경우와 달리) 별다른 물음없이 접근을 허용한다.</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>친구만 접근이 가능하도록 재작성 규칙들을 사용한다:</p> + +<div class="example"><pre> +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>!^friend1@client1.quux-corp\.com$</strong> +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>!^friend2</strong>@client2.quux-corp\.com$ +RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} <strong>!^friend3</strong>@client3.quux-corp\.com$ +RewriteRule ^/~quux/only-for-friends/ - [F] +</pre></div> + </dd> + </dl> + + + + <h3>Referer기반 변환기(deflector)</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>"Referer" HTTP 헤더에 따라 원하는대로 참조페이지를 + 설정할 수 있는 유연한 URL 변환기를 만들 수 있는가?</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>다음과 같이 복잡한 규칙을...</p> + +<div class="example"><pre> +RewriteMap deflector txt:/path/to/deflector.map + +RewriteCond %{HTTP_REFERER} !="" +RewriteCond ${deflector:%{HTTP_REFERER}} ^-$ +RewriteRule ^.* %{HTTP_REFERER} [R,L] + +RewriteCond %{HTTP_REFERER} !="" +RewriteCond ${deflector:%{HTTP_REFERER}|NOT-FOUND} !=NOT-FOUND +RewriteRule ^.* ${deflector:%{HTTP_REFERER}} [R,L] +</pre></div> + + <p>... 재작성 맵과 같이 사용한다:</p> + +<div class="example"><pre> +## +## deflector.map +## + +http://www.badguys.com/bad/index.html - +http://www.badguys.com/bad/index2.html - +http://www.badguys.com/bad/index3.html http://somewhere.com/ +</pre></div> + + <p>그러면 요청을 자동으로 (맵에서 값으로 "<code>-</code>"를 + 사용한 경우) 참조페이지나 (URL이 맵에 있는 경우 두번째 + 아규먼트로) 특정 URL로 리다이렉션한다.</p> + </dd> + </dl> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="other" id="other">기타</a></h2> + + + + <h3>외부 재작성 엔진</h3> + + + + <dl> + <dt>상황설명:</dt> + + <dd> + <p>FAQ: 어떻게 이런저런 잡다한 문제를 풀 수 있는가? + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>로는 해결책이 안보인다...</p> + </dd> + + <dt>해결책:</dt> + + <dd> + <p>외부 <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code>을 사용하라. + 즉, 프로그램이 <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code> 역할을 + 한다. 프로그램은 아파치가 시작할때 시작하여 + <code>STDIN</code>에서 요청한 URL을 받고, (같은 순서로!) + 결과 (보통 재작성된) URL을 <code>STDOUT</code>에 출력한다.</p> + +<div class="example"><pre> +RewriteEngine on +RewriteMap quux-map <strong>prg:</strong>/path/to/map.quux.pl +RewriteRule ^/~quux/(.*)$ /~quux/<strong>${quux-map:$1}</strong> +</pre></div> + +<div class="example"><pre> +#!/path/to/perl + +# 아파치 서버가 멈추지 않도록 +# 입출력 버퍼를 사용하지 않는다 +$| = 1; + +# stdin에서 한줄씩 URL을 읽고 +# stdout에 변환한 URL을 출력한다 +while (<>) { + s|^foo/|bar/|; + print $_; +} +</pre></div> + + <p>설명하기위해 모든 <code>/~quux/foo/...</code> URL을 + <code>/~quux/bar/...</code>로 재작성하는 스크립트를 + 예로 들었다. 실제로 마음대로 프로그래밍할 수 있다. + 그러나 일반 사용자가 이런 맵을 <strong>사용할</strong> + 수 있다고 하더라고, 오직 시스템 관리자만이 맵을 + <strong>정의해야</strong> 함을 주의하라.</p> + </dd> + </dl> + + + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/misc/rewriteguide.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/rewriteguide.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html new file mode 100644 index 00000000..893872b5 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: security_tips.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: security_tips.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: security_tips.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.en new file mode 100644 index 00000000..560c8259 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.en @@ -0,0 +1,354 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Security Tips - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Security Tips</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/security_tips.html" title="English"> en </a> | +<a href="../ko/misc/security_tips.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/security_tips.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> +</div> + + <p>Some hints and tips on security issues in setting up a web server. + Some of the suggestions will be general, others specific to Apache.</p> + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#uptodate">Keep up to Date</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#serverroot">Permissions on ServerRoot Directories</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 in General</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#nsaliasedcgi">Non Script Aliased CGI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#saliasedcgi">Script Aliased CGI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#dynamic">Other sources of dynamic content</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#systemsettings">Protecting System Settings</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#protectserverfiles">Protect Server Files by Default</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#watchyourlogs">Watching Your Logs</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="uptodate" id="uptodate">Keep up to Date</a></h2> + + <p>The Apache HTTP Server has a good record for security and a + developer community highly concerned about security issues. But + it is inevitable that some problems -- small or large -- will be + discovered in software after it is released. For this reason, it + is crucial to keep aware of updates to the software. If you have + obtained your version of the HTTP Server directly from Apache, we + highly recommend you subscribe to the <a href="http://httpd.apache.org/lists.html#http-announce">Apache + HTTP Server Announcements List</a> where you can keep informed of + new releases and security updates. Similar services are available + from most third-party distributors of Apache software.</p> + + <p>Of course, most times that a web server is compromised, it is + not because of problems in the HTTP Server code. Rather, it comes + from problems in add-on code, CGI scripts, or the underlying + Operating System. You must therefore stay aware of problems and + updates with all the software on your system.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="serverroot" id="serverroot">Permissions on ServerRoot Directories</a></h2> + + + + <p>In typical operation, Apache is started by the root user, and it + switches to the user defined by the <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> directive to serve hits. As is the + case with any command that root executes, you must take care that it is + protected from modification by non-root users. Not only must the files + themselves be writeable only by root, but so must the directories, and + parents of all directories. For example, if you choose to place + ServerRoot in <code>/usr/local/apache</code> then it is suggested that + you create that directory as root, with commands like these:</p> + + <div class="example"><p><code> + mkdir /usr/local/apache <br /> + cd /usr/local/apache <br /> + mkdir bin conf logs <br /> + chown 0 . bin conf logs <br /> + chgrp 0 . bin conf logs <br /> + chmod 755 . bin conf logs + </code></p></div> + + <p>It is assumed that <code>/</code>, <code>/usr</code>, and + <code>/usr/local</code> are only modifiable by root. When you install the + <code class="program"><a href="../programs/httpd.html">httpd</a></code> executable, you should ensure that it is + similarly protected:</p> + + <div class="example"><p><code> + cp httpd /usr/local/apache/bin <br /> + chown 0 /usr/local/apache/bin/httpd <br /> + chgrp 0 /usr/local/apache/bin/httpd <br /> + chmod 511 /usr/local/apache/bin/httpd + </code></p></div> + + <p>You can create an htdocs subdirectory which is modifiable by other + users -- since root never executes any files out of there, and shouldn't + be creating files in there.</p> + + <p>If you allow non-root users to modify any files that root either + executes or writes on then you open your system to root compromises. + For example, someone could replace the <code class="program"><a href="../programs/httpd.html">httpd</a></code> binary so + that the next time you start it, it will execute some arbitrary code. If + the logs directory is writeable (by a non-root user), someone could replace + a log file with a symlink to some other system file, and then root + might overwrite that file with arbitrary data. If the log files + themselves are writeable (by a non-root user), then someone may be + able to overwrite the log itself with bogus data.</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>Server Side Includes (SSI) present a server administrator with + several potential security risks.</p> + + <p>The first risk is the increased load on the server. All + SSI-enabled files have to be parsed by Apache, whether or not + there are any SSI directives included within the files. While this + load increase is minor, in a shared server environment it can become + significant.</p> + + <p>SSI files also pose the same risks that are associated with CGI + scripts in general. Using the <code>exec cmd</code> element, SSI-enabled + files can execute any CGI script or program under the permissions of the + user and group Apache runs as, as configured in + <code>httpd.conf</code>.</p> + + <p>There are ways to enhance the security of SSI files while still + taking advantage of the benefits they provide.</p> + + <p>To isolate the damage a wayward SSI file can cause, a server + administrator can enable <a href="../suexec.html">suexec</a> as + described in the <a href="#cgi">CGI in General</a> section.</p> + + <p>Enabling SSI for files with <code>.html</code> or <code>.htm</code> + extensions can be dangerous. This is especially true in a shared, or high + traffic, server environment. SSI-enabled files should have a separate + extension, such as the conventional <code>.shtml</code>. This helps keep + server load at a minimum and allows for easier management of risk.</p> + + <p>Another solution is to disable the ability to run scripts and + programs from SSI pages. To do this replace <code>Includes</code> + with <code>IncludesNOEXEC</code> in the <code class="directive"><a href="../mod/core.html#options">Options</a></code> directive. Note that users may + still use <code><--#include virtual="..." --></code> to execute CGI + scripts if these scripts are in directories designated by a <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> directive.</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 in General</a></h2> + + + + <p>First of all, you always have to remember that you must trust the + writers of the CGI scripts/programs or your ability to spot potential + security holes in CGI, whether they were deliberate or accidental. CGI + scripts can run essentially arbitrary commands on your system with the + permissions of the web server user and can therefore be extremely + dangerous if they are not carefully checked.</p> + + <p>All the CGI scripts will run as the same user, so they have potential + to conflict (accidentally or deliberately) with other scripts e.g. User + A hates User B, so he writes a script to trash User B's CGI database. One + program which can be used to allow scripts to run as different users is + <a href="../suexec.html">suEXEC</a> which is included with Apache as of + 1.2 and is called from special hooks in the Apache server code. Another + popular way of doing this is with + <a href="http://cgiwrap.unixtools.org/">CGIWrap</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="nsaliasedcgi" id="nsaliasedcgi">Non Script Aliased CGI</a></h2> + + + + <p>Allowing users to execute CGI scripts in any directory should only be + considered if:</p> + + <ul> + <li>You trust your users not to write scripts which will deliberately + or accidentally expose your system to an attack.</li> + <li>You consider security at your site to be so feeble in other areas, + as to make one more potential hole irrelevant.</li> + <li>You have no users, and nobody ever visits your server.</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="saliasedcgi" id="saliasedcgi">Script Aliased CGI</a></h2> + + + + <p>Limiting CGI to special directories gives the admin control over what + goes into those directories. This is inevitably more secure than non + script aliased CGI, but only if users with write access to the + directories are trusted or the admin is willing to test each + new CGI script/program for potential security holes.</p> + + <p>Most sites choose this option over the non script aliased CGI + approach.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="dynamic" id="dynamic">Other sources of dynamic content</a></h2> + + + + <p>Embedded scripting options which run as part of the server itself, + such as <code>mod_php</code>, <code>mod_perl</code>, <code>mod_tcl</code>, + and <code>mod_python</code>, run under the identity of the server itself + (see the <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> directive), and + therefore scripts executed by these engines potentially can access + anything the server user can. Some scripting engines may provide + restrictions, but it is better to be safe and assume not.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="systemsettings" id="systemsettings">Protecting System Settings</a></h2> + + + + <p>To run a really tight ship, you'll want to stop users from setting + up <code>.htaccess</code> files which can override security features + you've configured. Here's one way to do it.</p> + + <p>In the server configuration file, put</p> + + <div class="example"><p><code> + <Directory /> <br /> + AllowOverride None <br /> + </Directory> + </code></p></div> + + <p>This prevents the use of <code>.htaccess</code> files in all + directories apart from those specifically enabled.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="protectserverfiles" id="protectserverfiles">Protect Server Files by Default</a></h2> + + + + <p>One aspect of Apache which is occasionally misunderstood is the + feature of default access. That is, unless you take steps to change it, + if the server can find its way to a file through normal URL mapping + rules, it can serve it to clients.</p> + + <p>For instance, consider the following example:</p> + + <div class="example"><p><code> + # cd /; ln -s / public_html <br /> + Accessing <code>http://localhost/~root/</code> + </code></p></div> + + <p>This would allow clients to walk through the entire filesystem. To + work around this, add the following block to your server's + configuration:</p> + + <div class="example"><p><code> + <Directory /> <br /> + Order Deny,Allow <br /> + Deny from all <br /> + </Directory> + </code></p></div> + + <p>This will forbid default access to filesystem locations. Add + appropriate <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> blocks to + allow access only in those areas you wish. For example,</p> + + <div class="example"><p><code> + <Directory /usr/users/*/public_html> <br /> + Order Deny,Allow <br /> + Allow from all <br /> + </Directory> <br /> + <Directory /usr/local/httpd> <br /> + Order Deny,Allow <br /> + Allow from all <br /> + </Directory> + </code></p></div> + + <p>Pay particular attention to the interactions of <code class="directive"><a href="../mod/core.html#location">Location</a></code> and <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> directives; for instance, even + if <code><Directory /></code> denies access, a <code> + <Location /></code> directive might overturn it.</p> + + <p>Also be wary of playing games with the <code class="directive"><a href="../mod/mod_userdir.html#userdir">UserDir</a></code> directive; setting it to + something like <code>./</code> would have the same effect, for root, as + the first example above. If you are using Apache 1.3 or above, we strongly + recommend that you include the following line in your server + configuration files:</p> + + <div class="example"><p><code> + UserDir disabled root + </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="watchyourlogs" id="watchyourlogs">Watching Your Logs</a></h2> + + + + <p>To keep up-to-date with what is actually going on against your server + you have to check the <a href="../logs.html">Log Files</a>. Even though + the log files only reports what has already happened, they will give you + some understanding of what attacks is thrown against the server and + allow you to check if the necessary level of security is present.</p> + + <p>A couple of examples:</p> + + <div class="example"><p><code> + grep -c "/jsp/source.jsp?/jsp/ /jsp/source.jsp??" access_log <br /> + grep "client denied" error_log | tail -n 10 + </code></p></div> + + <p>The first example will list the number of attacks trying to exploit the + <a href="http://online.securityfocus.com/bid/4876/info/">Apache Tomcat + Source.JSP Malformed Request Information Disclosure Vulnerability</a>, + the second example will list the ten last denied clients, for example:</p> + + <div class="example"><p><code> + [Thu Jul 11 17:18:39 2002] [error] [client foo.bar.com] client denied + by server configuration: /usr/local/apache/htdocs/.htpasswd + </code></p></div> + + <p>As you can see, the log files only report what already has happened, so + if the client had been able to access the <code>.htpasswd</code> file you + would have seen something similar to:</p> + + <div class="example"><p><code> + foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" + </code></p></div> + + <p>in your <a href="../logs.html#accesslog">Access Log</a>. This means + you probably commented out the following in your server configuration + file:</p> + + <div class="example"><p><code> + <Files ~ "^\.ht"> <br /> + Order allow,deny <br /> + Deny from all <br /> + </Files> + </code></p></div> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/security_tips.html" title="English"> en </a> | +<a href="../ko/misc/security_tips.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/security_tips.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.ko.euc-kr new file mode 100644 index 00000000..58c56f14 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.ko.euc-kr @@ -0,0 +1,345 @@ +<?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><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>보안 팁 - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>보안 팁</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/misc/security_tips.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/security_tips.html" title="Korean"> ko </a> | +<a href="../tr/misc/security_tips.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate">이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.</div> + + <p>웹서버를 운영할때 도움이 될 보안 관련 힌트와 팁이다. + 어떤 것은 일반적이고, 어떤 것은 아파치에만 해당하는 것이다.</p> + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#uptodate">최신판으로 유지하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#serverroot">ServerRoot 디렉토리 권한</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="#nsaliasedcgi">ScriptAlias하지 않은 CGI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#saliasedcgi">ScriptAlias한 CGI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#dynamic">동적 내용을 생성하는 다른 방법</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#systemsettings">시스템 설정 보호하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#protectserverfiles">기본적으로 서버에 있는 파일 보호하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#watchyourlogs">로그 살펴보기</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="uptodate" id="uptodate">최신판으로 유지하기</a></h2> + + <p>아파치 웹서버는 안전과 보안 문제에 관심이 많은 개발자 + 공동체로 유명하다. 그러나 크건 작건 발표후 발견되는 문제들을 + 피할 수 없다. 그래서 소프트웨어를 최신버전으로 유지하는 + 것이 중요하다. 아파치에서 직접 웹서버를 다운로드했다면, + 새로운 버전과 보안 업데이트를 알려주는 <a href="http://httpd.apache.org/lists.html#http-announce">아파치 + 웹서버 발표 메일링리스트</a>를 구독하길 강력히 권한다. + 아파치 소프트웨어를 배포하는 많은 제삼자들도 비슷한 서비스를 + 제공한다.</p> + + <p>물론 웹서버 코드때문에 웹서버가 공격을 당하는 경우는 + 많지 않다. 그보다 추가 코드, 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="serverroot" id="serverroot">ServerRoot 디렉토리 권한</a></h2> + + + + <p>보통 root 사용자가 아파치를 시작한 후, 요청을 서비스하기위해 + <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> 지시어로 + 지정한 사용자로 변환한다. root가 실행하는 명령어가 있다면, + root 이외의 사용자가 수정하지 못하도록 주의해야 한다. 이 + 파일들을 root만 쓸 수 있어야 하고, 디렉토리와 모든 상위디렉토리도 + 마찬가지다. 예를 들어, ServerRoot로 /usr/local/apache를 + 사용한다면 root 사용자가 다음과 같이 디렉토리를 만들길 + 제안한다:</p> + + <div class="example"><p><code> + mkdir /usr/local/apache <br /> + cd /usr/local/apache <br /> + mkdir bin conf logs <br /> + chown 0 . bin conf logs <br /> + chgrp 0 . bin conf logs <br /> + chmod 755 . bin conf logs + </code></p></div> + + <p>그러면 /, /usr, /usr/local 은 root만이 수정할 수 있다. + httpd 실행파일을 설치할때 다음과 같이 보호해야 한다:</p> + + <div class="example"><p><code> + cp httpd /usr/local/apache/bin <br /> + chown 0 /usr/local/apache/bin/httpd <br /> + chgrp 0 /usr/local/apache/bin/httpd <br /> + chmod 511 /usr/local/apache/bin/httpd + </code></p></div> + + <p>htdocs 하위디렉토리는 다른 사용자들이 수정할 수 있도록 + 만들 수 있다 -- root는 그곳에 있는 파일을 실행하지도, 만들지도 + 않아야 한다.</p> + + <p>root가 아닌 사용자가 root가 실행하거나 쓰기가능한 파일을 + 수정할 수 있다면 시스템의 root 권한을 훔칠 수 있다. 예를 + 들어, 누군가 httpd 실행파일을 변경하였다면 다음번 시작할때 + 임의의 코드를 실행하게 된다. logs 디렉토리가 (root가 아닌 + 사용자에게) 쓰기가능하다면 누군가 로그파일을 다른 시스템파일로 + 심볼링크를 걸어서 root가 파일에 임의의 자료를 덮어쓸 수 + 있다. 로그파일이 (root가 아닌 사용자에게) 쓰기가능하다면 + 누군가 로그에 이상한 자료를 기록할 수 있다.</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>Server Side Includes (SSI)는 서버 관리자에게 보안상 몇가지 + 잠재적인 위험이다.</p> + + <p>첫번째 위험은 서버의 부하를 늘리는 점이다. 아파치는 파일에 + SSI 지시어가 있는지 여부와 관계없이 모든 SSI 파일을 분석해야 + 한다. 조금 부하가 늘지만, 서버를 여러 사람이 같이 사용하는 + 환경에서는 심각할 수 있다.</p> + + <p>또, SSI 파일은 일반적인 CGI 스크립트와 동일한 위험을 + 가진다. SSI 파일에서 "exec cmd"를 사용하면 httpd.conf에서 + 아파치를 실행하도록 설정한 사용자와 그룹 권한으로 CGI + 스크립트나 프로그램을 실행할 수 있다.</p> + + <p>장점을 활용하면서 SSI 파일의 보안을 향상시키는 방법이 + 있다.</p> + + <p>SSI 파일이 가져올 수 있는 피해를 격리하기위해 서버관리자는 + <a href="#cgi">일반적인 CGI</a> 절에서 설명하는 방법으로 + <a href="../suexec.html">suexec</a>를 사용할 수 있다</p> + + <p>.html이나 .htm 확장자를 SSI 파일로 사용하는 것은 위험하다. + 특히 여러 사람이 공유하거나 통신량이 많은 서버 환경에서 + 위험하다. SSI 파일은 일반적으로 많이 사용하는 .shtml 같은 + 별도의 확장자를 가져야 한다. 그러면 서버 부하를 최소화하고 + 위험요소를 쉽게 관리할 수 있다.</p> + + <p>다른 방법은 SSI 페이지가 스크립트나 프로그램을 실행하지 + 못하도록 만드는 것이다. <code class="directive"><a href="../mod/core.html#options">Options</a></code> 지시어에서 <code>Includes</code> + 대신 <code>IncludesNOEXEC</code>를 사용한다. 그래도 스크립트가 + <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> 지시어로 + 지정한 디렉토리에 있다면 <--#include virtual="..." -->를 + 사용하여 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="cgi" id="cgi">일반적인 CGI</a></h2> + + + + <p>결국 당신은 항상 CGI 스크립트/프로그램의 저자를 신뢰해야 + 하고, 고의건 실수이건 CGI의 잠재적인 보안상 허점을 발견할 + 수 있어야 한다. 기본적으로 CGI 스크립트는 웹서버 사용자 + 권한으로 시스템에서 어떤 명령어라도 실행할 수 있기때문에 + 주의있게 확인하지 않으면 매우 위험하다.</p> + + <p>모든 CGI 스크립트가 같은 사용자로 실행되기때문에 다른 + 스크립트와 (고의건 실수이건) 충돌할 가능성이 있다. 예를 + 들어, 사용자 A는 사용자 B를 매우 싫어하여, 사용자 B의 CGI + 데이터베이스를 지워버리는 스크립트를 작성할 수 있다. 아파치 + 1.2 버전부터 포함되었고 아파치 서버에서 특별한 훅(hook)으로 + 동작하는 <a href="../suexec.html">suEXEC</a>는 스크립트를 + 다른 사용자로 실행하는 방법중 하나다. 다른 대중적인 방법에는 + <a href="http://cgiwrap.unixtools.org/">CGIWrap</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="nsaliasedcgi" id="nsaliasedcgi">ScriptAlias하지 않은 CGI</a></h2> + + + + <p>다음 조건을 만족할때만 사용자가 어떤 디렉토리에서라도 + CGI 스크립트를 실행하도록 허용할 수 있다:</p> + + <ul> + <li>당신은 고의건 실수이건 사용자가 시스템을 공격에 노출시키는 + 스크립트를 작성하지 않는다고 믿는다.</li> + <li>시스템의 다른 부분의 보안이 약해서, 잠재적인 허점을 + 하나 더 만들어도 나빠질 것이 없다고 생각하는 경우.</li> + <li>사용자가 없고, 아마 아무도 서버를 방문하지않는 경우.</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="saliasedcgi" id="saliasedcgi">ScriptAlias한 CGI</a></h2> + + + + <p>특정 디렉토리에서만 CGI를 실행할 수 있도록 제한하면 관리자는 + 이들 디렉토리를 통제할 수 있다. 이 경우는 scriptalias하지 + 않은 CGI보다 확실히 안전하다. 단, 신뢰하는 사용자만 디렉토리에 + 접근할 수 있고, 관리자가 새로운 CGI 스크립트/프로그램의 + 잠재적인 보안상 허점을 검사할 용이가 있다면.</p> + + <p>대부분의 사이트는 scriptalias하지 않은 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="dynamic" id="dynamic">동적 내용을 생성하는 다른 방법</a></h2> + + + + <p> + mod_php, mod_perl, mod_tcl, mod_python 같이 서버의 일부로 + 동작하는 임베디드 스크립트는 서버와 같은 사용자로 (<code class="directive"><a href="../mod/mpm_common.html#user">User</a></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="systemsettings" id="systemsettings">시스템 설정 보호하기</a></h2> + + + + <p>정말로 안전한 서버를 운영하려면 사용자가 + <code>.htaccess</code> 파일을 사용하여 당신이 설정한 보안기능을 + 변경하길 바라지 않을 것이다. 그러기위해 다음과 같은 방법이 + 있다.</p> + + <p>서버 설정파일에 다음을 추가한다</p> + + <div class="example"><p><code> + <Directory /> <br /> + AllowOverride None <br /> + </Directory> + </code></p></div> + + <p>그러면 사용가능하도록 명시적으로 허용한 디렉토리를 제외하고는 + <code>.htaccess</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="protectserverfiles" id="protectserverfiles">기본적으로 서버에 있는 파일 보호하기</a></h2> + + + + <p>사람들은 종종 아파치의 기본 접근에 대해 잘못 알고있다. + 즉, 서버가 일반적인 URL 대응 규칙을 사용하여 파일을 찾을 + 수 있다면, 특별히 조치를 하지 않는한 클라이언트에게 파일이 + 서비스될 수 있다.</p> + + <p>예를 들어, 아래와 같은 경우:</p> + + <div class="example"><p><code> + # cd /; ln -s / public_html <br /> + <code>http://localhost/~root/</code> 에 접근한다 + </code></p></div> + + <p>그러면 클라이언트는 전체 파일시스템을 돌아다닐 수 있다. + 이를 막기위해 서버설정에서 다음과 같은 조치를 한다:</p> + + <div class="example"><p><code> + <Directory /> <br /> + Order Deny,Allow <br /> + Deny from all <br /> + </Directory> + </code></p></div> + + <p>그러면 파일시스템 위치에 대해 기본 접근이 거부된다. + 원하는 영역에 접근할 수 있도록 다음과 같은 <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> 블록을 추가한다.</p> + + <div class="example"><p><code> + <Directory /usr/users/*/public_html> <br /> + Order Deny,Allow <br /> + Allow from all <br /> + </Directory> <br /> + <Directory /usr/local/httpd> <br /> + Order Deny,Allow <br /> + Allow from all <br /> + </Directory> + </code></p></div> + + <p><code class="directive"><a href="../mod/core.html#location">Location</a></code>과 <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> 지시어를 같이 사용하는 + 경우 특별히 주의를 기울여라. 예를 들어, <code><Directory + /></code>가 접근을 거부하더라도 <code><Location + /></code> 지시어가 이를 무시할 수 있다</p> + + <p><code class="directive"><a href="../mod/mod_userdir.html#userdir">UserDir</a></code> 지시어를 + 사용하는 경우에도 주의하라. 지시어를 "./" 같이 설정하면 + root 사용자에 대해 바로 위의 경우와 같은 문제가 발생한다. + 아파치 1.3 이상을 사용한다면 서버 설정파일에 아래 줄을 추가하길 + 강력히 권한다:</p> + + <div class="example"><p><code> + UserDir disabled root + </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="watchyourlogs" id="watchyourlogs">로그 살펴보기</a></h2> + + + + <p>실제로 서버에서 무슨 일이 있어나고 있는지 알려면 <a href="../logs.html">로그파일</a>을 살펴봐야 한다. 로그파일은 + 이미 일어난 일만을 보고하지만, 서버에 어떤 공격이 있었는지 + 알려주고 현재 필요한 만큼 안전한지 확인하게 해준다.</p> + + <p>여러가지 예:</p> + + <div class="example"><p><code> + grep -c "/jsp/source.jsp?/jsp/ /jsp/source.jsp??" access_log <br /> + grep "client denied" error_log | tail -n 10 + </code></p></div> + + <p>첫번째 예는 <a href="http://online.securityfocus.com/bid/4876/info/">잘못된 + Source.JSP 요청으로 서버정보를 알아낼 수 있는 Tomcat의 + 취약점</a>를 이용하려는 공격 횟수를 알려주고, 두번째 예는 + 접근이 거부된 최근 클라이언트 10개를 다음과 같이 보여준다:</p> + + <div class="example"><p><code> + [Thu Jul 11 17:18:39 2002] [error] [client foo.bar.com] client denied + by server configuration: /usr/local/apache/htdocs/.htpasswd + </code></p></div> + + <p>잘 알 듯이 로그파일은 이미 발생한 사건만을 보고한다. + 그래서 클라이언트가 <code>.htpasswd</code> 파일에 접근할 + 수 있었다면 <a href="../logs.html#accesslog">접근 로그</a>에 + 다음과 같은 기록이 남을 것이다:</p> + + <div class="example"><p><code> + foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" + </code></p></div> + + <p>즉, 당신은 서버 설정파일에서 다음 부분을 주석처리했을 + 것이다:</p> + + <div class="example"><p><code> + <Files ~ "^\.ht"> <br /> + Order allow,deny <br /> + Deny from all <br /> + <Files> + </code></p></div> + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/misc/security_tips.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/security_tips.html" title="Korean"> ko </a> | +<a href="../tr/misc/security_tips.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.tr.utf8 b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.tr.utf8 new file mode 100644 index 00000000..7257521f --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/security_tips.html.tr.utf8 @@ -0,0 +1,344 @@ +<?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="tr" xml:lang="tr"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>G체venlik 캅pu챌lar캇 - Apache HTTP Sunucusu</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 href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Mod체ller</a> | <a href="../mod/directives.html">Y철nergeler</a> | <a href="../faq/">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas캇</a></p> +<p class="apache">Apache HTTP Sunucusu S체r체m 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Sunucusu</a> > <a href="http://httpd.apache.org/docs/">Belgeleme</a> > <a href="../">S체r체m 2.0</a> > <a href="./">횉e힊itli Belgeler</a></div><div id="page-content"><div id="preamble"><h1>G체venlik 캅pu챌lar캇</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/misc/security_tips.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/security_tips.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/security_tips.html" title="T체rk챌e"> tr </a></p> +</div> + + <p>Bir HTTP Sunucusunu ayarlarken dikkat edilmesi gerekenler ve baz캇 + ipu챌lar캇. 횜neriler k캇smen Apache��셺e 철zel k캇smen de genel olacakt캇r.</p> + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#uptodate">G체ncel Tutma</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#serverroot"><code>ServerRoot</code> Dizinlerinin 캅zinleri</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Sunucu Tarafl캇 캅챌erik Yerle힊tirme</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI Genelinde</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#nsaliasedcgi"><code>ScriptAlias</code>��셲캇z CGI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#saliasedcgi"><code>ScriptAlias</code>��셪캇 CGI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#dynamic">Devingen i챌erikli kaynaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#systemsettings">Sistem Ayarlar캇n캇n Korunmas캇</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#protectserverfiles">Sunucu dosyalar캇n캇n 철ntan캇ml캇 olarak korunmas캇</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#watchyourlogs">G체nl체klerin 캅zlenmesi</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="uptodate" id="uptodate">G체ncel Tutma</a></h2> + + <p>Apache HTTP Sunucusu iyi bir g체venlik sicilinin yan캇nda g체venlik + konular캇yla olduk챌a ilgili bir geli힊tirici toplulu휓una sahiptir. Fakat, + bir yaz캇l캇m캇n da휓캇t캇lmas캇n캇n ard캇ndan k체챌체k ya da b체y체k baz캇 sorunlar캇n + ke힊fedilmesi ka챌캇n캇lmazd캇r. Bu sebeple, yaz캇l캇m g체ncellemelerinden + haberdar olmak olduk챌a 철nem kazan캇r. HTTP sunucunuzu do휓rudan + Apache��셝en temin ediyorsan캇z yeni s체r체mler ve g체venlik g체ncellemeleri + ile ilgili bilgileri tam zaman캇nda alabilmek i챌in <a href="http://httpd.apache.org/lists.html#http-announce">Apache + HTTP Sunucusu Duyuru Listesi</a>ne mutlaka 체ye olman캇z캇 철neririz. + Apache yaz캇l캇m캇n캇n 체챌체nc체 parti da휓캇t캇mlar캇n캇 yapanlar캇n da buna benzer + hizmetleri vard캇r.</p> + + <p>힇체phesiz, bir HTTP sunucusu, sunucu kodunda bir sorun olmasa da + tehlike alt캇ndad캇r. Eklenti kodlar캇, CGI betikleri hatta i힊letim + sisteminden kaynaklanan sorunlar nedeniyle bu ortaya 챌캇kabilir. Bu + bak캇mdan, sisteminizdeki t체m yaz캇l캇mlar캇n sorunlar캇 ve g체ncellemeleri + hakk캇nda bilgi sahibi olmal캇s캇n캇z.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="serverroot" id="serverroot"><code>ServerRoot</code> Dizinlerinin 캅zinleri</a></h2> + + + <p>Normalde, Apache root kullan캇c캇 taraf캇ndan ba힊lat캇l캇r ve hizmetleri + sunarken <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> y철nergesi + taraf캇ndan tan캇mlanan kullan캇c캇n캇n aidiyetinde 챌al캇힊캇r. Root taraf캇ndan + 챌al캇힊t캇r캇lan komutlarda oldu휓u gibi, root olmayan kullan캇c캇lar캇n + yapacaklar캇 de휓i힊ikliklerden korunmak konusunda da dikkatli + olmal캇s캇n캇z. Dosyalar캇n sadece root taraf캇ndan yaz캇labilir olmas캇n캇 + sa휓lamak yeterli de휓ildir, bu dizinler ve 체st dizinler i챌in de + yap캇lmal캇d캇r. 횜rne휓in, sunucu k철k dizininin + <code>/usr/local/apache</code> olmas캇na karar verdiyseniz, bu dizini + root olarak 힊철yle olu힊turman캇z 철nerilir:</p> + + <div class="example"><p><code> + mkdir /usr/local/apache <br /> + cd /usr/local/apache <br /> + mkdir bin conf logs <br /> + chown 0 . bin conf logs <br /> + chgrp 0 . bin conf logs <br /> + chmod 755 . bin conf logs + </code></p></div> + + <p><code>/</code>, <code>/usr</code>, <code>/usr/local</code> + dizinlerinde sadece root taraf캇ndan de휓i힊iklik yap캇labilece휓i kabul + edilir. <code class="program"><a href="../programs/httpd.html">httpd</a></code> 챌al캇힊t캇r캇labilirini kurarken de benzer + bir 철nlemin al캇nd캇휓캇ndan emin olmal캇s캇n캇z:</p> + + <div class="example"><p><code> + cp httpd /usr/local/apache/bin <br /> + chown 0 /usr/local/apache/bin/httpd <br /> + chgrp 0 /usr/local/apache/bin/httpd <br /> + chmod 511 /usr/local/apache/bin/httpd + </code></p></div> + + <p>Di휓er kullan캇c캇lar캇n de휓i힊iklik yapabilece휓i bir dizin olarak bir + <code>htdocs</code> dizini olu힊turabilirsiniz. Bu dizine root + taraf캇ndan 챌al캇힊t캇r캇labilecek dosyalar konulmamal캇 ve burada root + taraf캇ndan hi챌bir dosya olu힊turulmamal캇d캇r.</p> + + <p>Di휓er kullan캇c캇lara root taraf캇ndan yaz캇labilen ve 챌al캇힊t캇r캇labilen + dosyalarda de휓i힊iklik yapma hakk캇n캇 tan캇rsan캇z, onlara root + kullan캇c캇s캇n캇 ele ge챌irilebilme hakk캇n캇 da tan캇m캇힊 olursunuz. 횜rne휓in, + biri <code class="program"><a href="../programs/httpd.html">httpd</a></code> 챌al캇힊t캇r캇labilirini zararl캇 bir programla + de휓i힊tirebilir ve o program캇 tekrar 챌al캇힊t캇rd캇휓캇n캇z s캇rada program + yapaca휓캇n캇 yapm캇힊 olur. G체nl체kleri kaydetti휓iniz dizin herkes + taraf캇ndan yaz캇labilen bir dizin oldu휓u takdirde, birileri bir g체nl체k + dosyas캇n캇 bir sistem dosyas캇na sembolik ba휓 haline getirerek root + kullan캇c캇s캇n캇n bu dosyaya ilgisiz 힊eyler yazmas캇na sebep olabilir. + G체nl체klerin dosyalar캇 herkes taraf캇ndan yaz캇labilir oldu휓u takdirde ise + birileri dosyaya yan캇lt캇c캇 veriler girebilir.</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">Sunucu Tarafl캇 캅챌erik Yerle힊tirme</a></h2> + + + <p>SSI sayfalar캇 bir sunucu y철neticisi a챌캇s캇ndan 챌e힊itli olas캇 risklere + kaynakl캇k edebilir.</p> + + <p>캅lk risk, sunucu y체k체ndeki art캇힊 olas캇l캇휓캇d캇r. T체m SSI sayfalar캇, SSI + kodu i챌ersin i챌ermesin Apache taraf캇ndan 챌철z체mlenir. Bu k체챌체k bir art캇힊 + gibi g철r체n체rse de bir payla힊캇ml캇 sunucu ortam캇nda 철nemli bir y체k haline + gelebilir.</p> + + <p>SSI sayfalar캇, CGI betikleriyle ilgili riskleri de ta힊캇r. <code>exec + cmd</code> eleman캇 kullan캇larak bir SSI sayfas캇ndan herhangi bir CGI + beti휓ini veya bir sistem program캇n캇 Apache��셬in aidiyetinde oldu휓u + kullan캇c캇n캇n yetkisiyle 챌al캇힊t캇rmak m체mk체nd체r.</p> + + <p>SSI sayfalar캇n캇n yararl캇 철zelliklerinden yararlan캇rken g체venli휓ini de + artt캇rman캇n baz캇 yollar캇 vard캇r.</p> + + <p>Sunucu y철neticisi, bir ba힊캇bozuk SSI sayfas캇n캇n sebep olabilece휓i + zararlar캇 bertaraf etmek i챌in <a href="#cgi">CGI Genelinde</a> + b철l체m체nde a챌캇kland캇휓캇 gibi <a href="../suexec.html">suexec</a>��셢 etkin + k캇labilir.</p> + + <p>SSI sayfalar캇n캇 <code>.html</code> veya <code>.htm</code> + uzant캇lar캇yla etkinle힊tirmek tehlikeli olabilir. Bu 철zellikle + payla힊캇ml캇 ve y체ksek trafikli bir sunucu ortam캇nda 철nemlidir. SSI + sayfalar캇n캇 normal sayfalardan farkl캇 olarak <code>.shtml</code> gibi + bildik bir uzant캇yla etkinle힊tirmek gerekir. Bu, sunucu y체k체n체 asgari + d체zeyde tutmaya ve risk y철netimini kolayla힊t캇rmaya yarar.</p> + + <p>Di휓er bir 챌철z체m de SSI sayfalar캇ndan betik ve program 챌al캇힊t캇rmay캇 + iptal etmektir. Bu, <code class="directive"><a href="../mod/core.html#options">Options</a></code> + y철nergesine de휓er olarak <code>Includes</code> yerine + <code>IncludesNOEXEC</code> vererek sa휓lan캇r. Ancak, e휓er betiklerin + bulundu휓u dizinde <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> + y철nergesiyle CGI betiklerinin 챌al캇힊mas캇 m체mk체n k캇l캇nm캇힊sa, + kullan캇c캇lar캇n <code><--#include virtual="..." --></code> ile bu + betikleri 챌al캇힊t캇rabileceklerine dikkat ediniz.</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 Genelinde</a></h2> + + + <p>Her힊eyden 철nce ya CGI beti휓ini/program캇n캇 yazanlara ya da kendinizin + CGI'deki g체venlik a챌캇klar캇n캇 (ister kas캇tl캇 olsun ister tesad체fi) + yakalama becerinize g체venmek zorundas캇n캇z. CGI betikleri esasen + sisteminizdeki komutlar캇 site kullan캇c캇lar캇n캇n izinleriyle + 챌al캇힊t캇r캇rlar. Bu bak캇mdan dikkatle denenmedikleri takdirde olduk챌a + tehlikeli olabilirler.</p> + + <p>CGI betiklerinin hepsi ayn캇 kullan캇c캇n캇n aidiyetinde 챌al캇힊캇rsa di휓er + betiklerle aralar캇nda 챌eli힊kilerin ortaya 챌캇kmas캇 ister istemez + ka챌캇n캇lmazd캇r. 횜rne휓in A kullan캇c캇s캇n캇n B kullan캇c캇s캇na garezi varsa + bir betik yaz캇p B��셬in CGI veritaban캇n캇 silebilir. Bu gibi durumlar캇n + ortaya 챌캇kmamas캇 i챌in betiklerin farkl캇 kullan캇c캇lar캇n aidiyetlerinde + 챌al캇힊mas캇n캇 sa휓layan ve 1.2 s체r체m체nden beri Apache ile da휓캇t캇lan <a href="../suexec.html">suEXEC</a> diye bir program vard캇r. Ba힊ka bir yol + da <a href="http://cgiwrap.unixtools.org/">CGIWrap</a> kullanmakt캇r.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="nsaliasedcgi" id="nsaliasedcgi"><code>ScriptAlias</code>��셲캇z CGI</a></h2> + + + <p>Kullan캇c캇lar캇n sitenin her yerinde CGI betiklerini 챌al캇힊t캇rmalar캇na + izin vermek ancak 힊u ko힊ullarda m체mk체n olabilir:</p> + + <ul> + <li>Kullan캇c캇lar캇n캇z캇n kas캇tl캇 ya da kas캇ts캇z sistemi sald캇r캇ya a챌캇k + hale getirecek betikler yazmayacaklar캇na tam g체veniniz vard캇r.</li> + <li>Sitenizin g체venli휓i zaten o kadar k철t체d체r ki, bir delik daha + a챌캇lmas캇n캇n mahzuru yoktur.</li> + <li>Sitenizin sizden ba힊ka kullan캇c캇s캇 yoktur ve sunucunuzu sizden + ba힊ka hi챌 kimsenin ziyaret etmesi m체mk체n de휓ildir.</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="saliasedcgi" id="saliasedcgi"><code>ScriptAlias</code>��셪캇 CGI</a></h2> + + + <p>CGI��셺i belli dizinlerle s캇n캇rlamak y철neticiye bu dizinlerde daha iyi + denetim imkan캇 sa휓lar. Bu ka챌캇n캇lmaz olarak <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>��셲캇z CGI��셝en 챌ok daha + g체venlidir, ancak bu dizinlere yazma hakk캇 olan kullan캇c캇lar캇n캇z + g체venilir ki힊iler olmas캇 ve site y철neticisinin de olas캇 g체venlik + a챌캇klar캇na kar힊캇 CGI betiklerini ve programlar캇n캇 denemeye istekli + olmas캇 힊art캇yla.</p> + + <p>횉o휓u site y철neticisi <code>ScriptAlias</code>��셲캇z CGI yerine bu + yakla힊캇m캇 se챌er.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="dynamic" id="dynamic">Devingen i챌erikli kaynaklar</a></h2> + + + <p>Sunucunun bir par챌as캇 gibi 챌al캇힊an, <code>mod_php</code>, + <code>mod_perl</code>, <code>mod_tcl</code> ve <code>mod_python</code> + gibi g철m체l체 betik 챌al캇힊t캇rma se챌enekleri sunucuyu 챌al캇힊t캇ran + kullan캇c캇n캇n aidiyetinde 챌al캇힊캇rlar (<code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> y철nergesine bak캇n캇z). Bu bak캇mdan bu betik + yorumlay캇c캇lar taraf캇ndan 챌al캇힊t캇r캇lan betikler, sunucu kullan캇c캇s캇n캇n + eri힊ti휓i her힊eye eri힊ebilirler. Baz캇 betik yorumlay캇c캇lar캇n getirdi휓i + baz캇 s캇n캇rlamalar varsa da bunlara pek g체venmemek, gerekli s캇namalar캇 + yine de yapmak gerekir.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="systemsettings" id="systemsettings">Sistem Ayarlar캇n캇n Korunmas캇</a></h2> + + + <p>G체venli휓i ger챌ekten s캇k캇 tutmak istiyorsan캇z, kullan캇c캇lar캇n캇z캇n + yap캇land캇rman캇zdaki g체venlik ayarlar캇n캇 ge챌ersiz k캇lmak i챌in + <code>.htaccess</code> dosyalar캇n캇 kullanabilmelerinin de 철n체ne + ge챌melisiniz. Bunu yapman캇n tek bir yolu vard캇r.</p> + + <p>Sunucu yap캇land캇rma dosyan캇za 힊unu yerle힊tirin:</p> + + <div class="example"><p><code> + <Directory /> + <span class="indent"> + AllowOverride None + </span> + </Directory> + </code></p></div> + + <p>B철ylece, belli dizinlerde 철zellikle etkinle힊tirilmedik챌e b체t체n + dizinlerde <code>.htaccess</code> dosyalar캇n캇n kullan캇m캇n캇 engellemi힊 + olursunuz.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="protectserverfiles" id="protectserverfiles">Sunucu dosyalar캇n캇n 철ntan캇ml캇 olarak korunmas캇</a></h2> + + + <p>Apache��셬in ister istemez yanl캇힊 anla힊캇lan y철nlerinden biri 철ntan캇ml캇 eri힊im 철zelli휓idir. Yani siz aksine bir 힊eyler yapmad캇k챌a, sunucu normal URL e힊leme kurallar캇n캇 kullanarak bir dosyay캇 bulabildi휓i s체rece onu istemciye sunacakt캇r.</p> + + <p>횜rne휓in, a힊a휓캇daki durumu ele alal캇m:</p> + + <div class="example"><p><code> + # cd /; ln -s / public_html + </code></p></div> + + <p>Ve, taray캇c캇n캇za <code>http://localhost/~root/</code> yaz캇n.</p> + + <p>B철ylece, istemcilerin t체m dosya sisteminizi gezmelerine izin vermi힊 olursunuz. Bu i힊lemin sonu챌lar캇n캇n 철n체n체 almak i챌in sunucu yap캇land캇rma dosyan캇za 힊unlar캇 yaz캇n:</p> + + <div class="example"><p><code> + <Directory /> + <span class="indent"> + Order Deny,Allow <br /> + Deny from all + </span> + </Directory> + </code></p></div> + + <p>Bu suretle, dosya sisteminize 철ntan캇ml캇 eri힊imi yasaklam캇힊 olursunuz. Eri힊ime izin vermek istedi휓iniz dizinler i챌in uygun <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> b철l체mleri eklemeniz yeterli olacakt캇r. 횜rnek:</p> + + <div class="example"><p><code> + <Directory /usr/users/*/public_html> + <span class="indent"> + Order Deny,Allow <br /> + Allow from all + </span> + </Directory> <br /> + <Directory /usr/local/httpd> + <span class="indent"> + Order Deny,Allow <br /> + Allow from all + </span> + </Directory> + </code></p></div> + + <p><code class="directive"><a href="../mod/core.html#location">Location</a></code> ve <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> y철nergelerinin etkile힊imine de 철zellikle 철nem vermelisiniz; 철rne휓in <code><Directory /></code> eri힊imi yasaklarken bir <code><Location /></code> y철nergesi bunu ortadan kald캇rabilir.</p> + + <p><code class="directive"><a href="../mod/mod_userdir.html#userdir">UserDir</a></code> y철nergesi de size buna benzer bir oyun oynayabilir; y철nergeye <code>./</code> atamas캇n캇 yaparsan캇z, root kullan캇c캇s캇 s철z konusu oldu휓unda yukar캇da ilk 철rnekteki durumla kar힊캇la힊캇r캇z. Apache 1.3 veya 체st체n체 kullan캇yorsan캇z, sunucu yap캇land캇rma dosyan캇zda a힊a휓캇daki sat캇r캇n mutlaka bulunmas캇n캇 철neririz:</p> + + <div class="example"><p><code> + UserDir disabled root + </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="watchyourlogs" id="watchyourlogs">G체nl체klerin 캅zlenmesi</a></h2> + + + <p>Sunucunuzda olup biteni g체n체 g체n체ne bilmek istiyorsan캇z <a href="../logs.html">g체nl체k dosyalar캇na</a> bakmal캇s캇n캇z. G체nl체k dosyalar캇 sadece olup biteni raporlamakla kalmaz, sunucunuza ne t체r sald캇r캇lar yap캇ld캇휓캇n캇 ve g체venlik seviyenizin yeterli olup olmad캇휓캇n캇 anlaman캇z캇 da sa휓larlar.</p> + + <p>Baz캇 철rnekler:</p> + + <div class="example"><p><code> + grep -c "/jsp/source.jsp?/jsp/ /jsp/source.jsp??" access_log <br /> + grep "client denied" error_log | tail -n 10 + </code></p></div> + + <p>캅lk 철rnek, <a href="http://online.securityfocus.com/bid/4876/info/">Apache Tomcat + Source.JSP Bozuk 캅stek Bilgilerini 캅f힊a A챌캇휓캇</a>n캇 istismar etmeyi deneyen sald캇r캇lar캇n say캇s캇n캇 verirken ikinci 철rnek, reddedilen son on istemciyi listeler; 철rnek:</p> + + <div class="example"><p><code> + [Thu Jul 11 17:18:39 2002] [error] [client falan.filan.dom] client denied + by server configuration: /usr/local/apache/htdocs/.htpasswd + </code></p></div> + + <p>G철rd체휓체n체z gibi g체nl체k dosyalar캇 sadece ne olup bitti휓ini raporlar, bu bak캇mdan e휓er istemci <code>.htpasswd</code> dosyas캇na eri힊ebiliyorsa <a href="../logs.html#accesslog">eri힊im g체nl체휓체n체zde</a> 힊una benzer bir kay캇t g철r체rs체n체z:</p> + + <div class="example"><p><code> + falan.filan.dom - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" + </code></p></div> + + <p>Bu, sunucu yap캇land캇rma dosyan캇zda a힊a휓캇daki yap캇land캇rmay캇 iptal etti휓iniz anlam캇na gelir:</p> + + <div class="example"><p><code> + <Files ~ "^\.ht"> + <span class="indent"> + Order allow,deny <br /> + Deny from all + </span> + </Files> + </code></p></div> + + </div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/misc/security_tips.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/misc/security_tips.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/misc/security_tips.html" title="T체rk챌e"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br /><a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> alt캇nda lisansl캇d캇r.</p> +<p class="menu"><a href="../mod/">Mod체ller</a> | <a href="../mod/directives.html">Y철nergeler</a> | <a href="../faq/">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas캇</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/tutorials.html b/rubbos/app/httpd-2.0.64/docs/manual/misc/tutorials.html new file mode 100644 index 00000000..e17505c2 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/tutorials.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: tutorials.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/rubbos/app/httpd-2.0.64/docs/manual/misc/tutorials.html.en b/rubbos/app/httpd-2.0.64/docs/manual/misc/tutorials.html.en new file mode 100644 index 00000000..0b9f2d12 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/misc/tutorials.html.en @@ -0,0 +1,211 @@ +<?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="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache Tutorials - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Apache Tutorials</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/misc/tutorials.html" title="English"> en </a></p> +</div> + + + <div class="warning"><h3>Warning:</h3> + <p>This document has not been fully updated + to take into account changes made in the 2.0 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.</p> + </div> + + <p>The following documents give you step-by-step instructions + on how to accomplish common tasks with the Apache HTTP server. + Many of these documents are located at external sites and are + not the work of the Apache Software Foundation. Copyright to + documents on external sites is owned by the authors or their + assignees. Please consult the <a href="../">official Apache + Server documentation</a> to verify what you read on external + sites.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#starting">Installation & Getting Started</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#basics">Basic Configuration</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#security">Security</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#logging">Logging</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#cgi_ssi">CGI and SSI</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#other">Other Features</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="starting" id="starting">Installation & Getting Started</a></h2> + + + + <ul> + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-1-001-01-NW-DP-LF"> + Getting Started with Apache 1.3</a> (ApacheToday)</li> + + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-07-10-001-01-NW-LF-SW"> + Configuring Your Apache Server Installation</a> + (ApacheToday)</li> + + <li><a href="http://www.onlamp.com/pub/a/apache/2000/02/24/installing_apache.html"> + Getting, Installing, and Running Apache (on Unix)</a> + (O'Reilly Network Apache DevCenter)</li> + + <li><a href="http://www.builder.com/Servers/Apache/ss01.html">Maximum + Apache: Getting Started</a> (CNET Builder.com)</li> + + <li><a href="http://www.devshed.com/Server_Side/Administration/APACHE/"> + How to Build the Apache of Your Dreams</a> (Developer + Shed)</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="basics" id="basics">Basic Configuration</a></h2> + + + + <ul> + <li><a href="http://www.onlamp.com/pub/a/apache/2000/03/02/configuring_apache.html"> + An Amble Through Apache Configuration</a> (O'Reilly Network + Apache DevCenter)</li> + + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-07-19-002-01-NW-LF-SW"> + Using .htaccess Files with Apache</a> (ApacheToday)</li> + + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-07-17-001-01-PS"> + Setting Up Virtual Hosts</a> (ApacheToday)</li> + + <li><a href="http://www.builder.com/Servers/Apache/ss02.html">Maximum + Apache: Configure Apache</a> (CNET Builder.com)</li> + + <li><a href="http://www.devshed.com/Server_Side/Administration/MoreApache/"> + Getting More Out of Apache</a> (Developer Shed)</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="security" id="security">Security</a></h2> + + + + <ul> + <li><a href="http://www.linuxplanet.com/linuxplanet/tutorials/1527/1/"> + Security and Apache: An Essential Primer</a> + (LinuxPlanet)</li> + + <li><a href="http://www.apacheweek.com/features/userauth">Using User + Authentication</a> (Apacheweek)</li> + + <li><a href="http://www.apacheweek.com/features/dbmauth">DBM + User Authentication</a> (Apacheweek)</li> + + <li><a href="http://linux.com/security/newsitem.phtml?sid=12&aid=3549"> + An Introduction to Securing Apache</a> (Linux.com)</li> + + <li><a href="http://linux.com/security/newsitem.phtml?sid=12&aid=3667"> + Securing Apache - Access Control</a> (Linux.com)</li> + + <li>Apache Authentication <a href="http://apachetoday.com/news_story.php3?ltsn=2000-07-24-002-01-NW-LF-SW"> + Part 1</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-07-31-001-01-NW-DP-LF"> + Part 2</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-08-07-001-01-NW-LF-SW"> + Part 3</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-08-14-001-01-NW-LF-SW"> + Part 4</a> (ApacheToday)</li> + + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-11-13-003-01-SC-LF-SW"> + mod_access: Restricting Access by Host</a> (ApacheToday)</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="logging" id="logging">Logging</a></h2> + + + + <ul> + <li><a href="http://www.onlamp.com/pub/a/apache/2000/03/10/log_rhythms.html"> + Log Rhythms</a> (O'Reilly Network Apache DevCenter)</li> + + <li><a href="http://www.apacheweek.com/features/logfiles">Gathering + Visitor Information: Customising Your Logfiles</a> + (Apacheweek)</li> + + <li>Apache Guide: Logging <a href="http://apachetoday.com/news_story.php3?ltsn=2000-08-21-003-01-NW-LF-SW"> + Part 1</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-08-28-001-01-NW-LF-SW"> + Part 2</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-09-05-001-01-NW-LF-SW"> + Part 3</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-09-18-003-01-NW-LF-SW"> + Part 4</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-09-25-001-01-NW-LF-SW"> + Part 5</a> (ApacheToday)</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="cgi_ssi" id="cgi_ssi">CGI and SSI</a></h2> + + + + <ul> + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-05-001-10-NW-LF-SW"> + Dynamic Content with CGI</a> (ApacheToday)</li> + + <li><a href="http://www.cpan.org/doc/FAQs/cgi/idiots-guide.html"> + The Idiot's Guide to Solving Perl CGI Problems</a> + (CPAN)</li> + + <li><a href="http://www.linuxplanet.com/linuxplanet/tutorials/1445/1/"> + Executing CGI Scripts as Other Users</a> (LinuxPlanet)</li> + + <li><a href="http://www.htmlhelp.org/faq/cgifaq.html">CGI + Programming FAQ</a> (Web Design Group)</li> + + <li>Introduction to Server Side Includes <a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-12-001-01-PS"> + Part 1</a> - <a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-19-002-01-NW-LF-SW"> + Part 2</a> (ApacheToday)</li> + + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-26-001-01-NW-LF-SW"> + Advanced SSI Techniques</a> (ApacheToday)</li> + + <li><a href="http://www.builder.com/Servers/ApacheFiles/082400/">Setting + up CGI and SSI with Apache</a> (CNET Builder.com)</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="other" id="other">Other Features</a></h2> + + + + <ul> + <li><a href="http://www.apacheweek.com/features/negotiation">Content + Negotiation Explained</a> (Apacheweek)</li> + + <li><a href="http://www.apacheweek.com/features/imagemaps">Using + Apache Imagemaps</a> (Apacheweek)</li> + + <li><a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-14-002-01-PS"> + Keeping Your Images from Adorning Other Sites</a> + (ApacheToday)</li> + + <li><a href="http://ppewww.ph.gla.ac.uk/~flavell/www/lang-neg.html">Language + Negotiation Notes</a> (Alan J. Flavell)</li> + </ul> + + <p>If you have a pointer to an accurate and well-written + tutorial not included here, please let us know by submitting it + to the <a href="http://bugs.apache.org/">Apache Bug + Database</a>.</p> + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/misc/tutorials.html" title="English"> en </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file |