diff options
author | hongbotian <hongbo.tianhongbo@huawei.com> | 2015-11-30 01:35:09 -0500 |
---|---|---|
committer | hongbotian <hongbo.tianhongbo@huawei.com> | 2015-11-30 01:36:35 -0500 |
commit | cc40af334e619bb549038238507407866f774f8f (patch) | |
tree | 43ddc1974f72997a57173151eafb23e6025a13c9 /rubbos/app/apache2/manual/vhosts | |
parent | 68e74fd78b2485e5914ce34a5b30f4485029e021 (diff) |
upload apache
JIRA: BOTTLENECK-10
Change-Id: I67eae31de6dc824097dfa56ab454ba36fdd23a2c
Signed-off-by: hongbotian <hongbo.tianhongbo@huawei.com>
Diffstat (limited to 'rubbos/app/apache2/manual/vhosts')
36 files changed, 7860 insertions, 0 deletions
diff --git a/rubbos/app/apache2/manual/vhosts/details.html b/rubbos/app/apache2/manual/vhosts/details.html new file mode 100644 index 00000000..1ccf806c --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/details.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: details.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: details.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: details.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/details.html.en b/rubbos/app/apache2/manual/vhosts/details.html.en new file mode 100644 index 00000000..14ad0dac --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/details.html.en @@ -0,0 +1,440 @@ +<?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>An In-Depth Discussion of Virtual Host Matching - 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="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>An In-Depth Discussion of Virtual Host Matching</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/vhosts/details.html" title="English"> en </a> | +<a href="../ko/vhosts/details.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/details.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + + <p>The virtual host code was completely rewritten in + <strong>Apache 1.3</strong>. This document attempts to explain + exactly what Apache does when deciding what virtual host to + serve a hit from. With the help of the new + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + directive virtual host configuration should be a lot easier and + safer than with versions prior to 1.3.</p> + + <p>If you just want to <cite>make it work</cite> without + understanding how, here are <a href="examples.html">some + examples</a>.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#configparsing">Config File Parsing</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#hostmatching">Virtual Host Matching</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#tips">Tips</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="configparsing" id="configparsing">Config File Parsing</a></h2> + + <p>There is a <em>main_server</em> which consists of all the + definitions appearing outside of + <code><VirtualHost></code> sections. There are virtual + servers, called <em>vhosts</em>, which are defined by + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + sections.</p> + + <p>The directives + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, + <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code>, + and <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> + can appear anywhere within the definition of a server. However, + each appearance overrides the previous appearance (within that + server).</p> + + <p>The default value of the <code>Listen</code> field for + main_server is 80. The main_server has no default + <code>ServerPath</code>, or <code>ServerAlias</code>. The + default <code>ServerName</code> is deduced from the server's IP + address.</p> + + <p>The main_server Listen directive has two functions. One + function is to determine the default network port Apache will + bind to. The second function is to specify the port number + which is used in absolute URIs during redirects.</p> + + <p>Unlike the main_server, vhost ports <em>do not</em> affect + what ports Apache listens for connections on.</p> + + <p>Each address appearing in the <code>VirtualHost</code> + directive can have an optional port. If the port is unspecified + it defaults to the value of the main_server's most recent + <code>Listen</code> statement. The special port <code>*</code> + indicates a wildcard that matches any port. Collectively the + entire set of addresses (including multiple <code>A</code> + record results from DNS lookups) are called the vhost's + <em>address set</em>.</p> + + <p>Unless a <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + directive is used for a specific IP address the first vhost + with that address is treated as an IP-based vhost. The IP + address can also be the wildcard <code>*</code>.</p> + + <p>If name-based vhosts should be used a + <code>NameVirtualHost</code> directive <em>must</em> appear + with the IP address set to be used for the name-based vhosts. + In other words, you must specify the IP address that holds the + hostname aliases (CNAMEs) for your name-based vhosts via a + <code>NameVirtualHost</code> directive in your configuration + file.</p> + + <p>Multiple <code>NameVirtualHost</code> directives can be used + each with a set of <code>VirtualHost</code> directives but only + one <code>NameVirtualHost</code> directive should be used for + each specific IP:port pair.</p> + + <p>The ordering of <code>NameVirtualHost</code> and + <code>VirtualHost</code> directives is not important which + makes the following two examples identical (only the order of + the <code>VirtualHost</code> directives for <em>one</em> + address set is important, see below):</p> + +<table><tr> +<td><div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <VirtualHost 111.22.33.44><br /> + # server A<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.44><br /> + # server B<br /> + ...<br /> + </VirtualHost><br /> + <br /> + NameVirtualHost 111.22.33.55<br /> + <VirtualHost 111.22.33.55><br /> + # server C<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # server D<br /> + ...<br /> + </VirtualHost> +</code></p></div></td> +<td><div class="example"><p><code> + <VirtualHost 111.22.33.44><br /> + # server A<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # server C<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.44><br /> + # server B<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # server D<br /> + ...<br /> + </VirtualHost><br /> + <br /> + NameVirtualHost 111.22.33.44<br /> + NameVirtualHost 111.22.33.55<br /> + <br /> +</code></p></div></td> +</tr></table> + + + <p>(To aid the readability of your configuration you should + prefer the left variant.)</p> + + <p>After parsing the <code>VirtualHost</code> directive, the + vhost server is given a default <code>Listen</code> equal to the + port assigned to the first name in its <code>VirtualHost</code> + directive.</p> + + <p>The complete list of names in the <code>VirtualHost</code> + directive are treated just like a <code>ServerAlias</code> (but + are not overridden by any <code>ServerAlias</code> statement) + if all names resolve to the same address set. Note that + subsequent <code>Listen</code> statements for this vhost will not + affect the ports assigned in the address set.</p> + + <p>During initialization a list for each IP address is + generated and inserted into an hash table. If the IP address is + used in a <code>NameVirtualHost</code> directive the list + contains all name-based vhosts for the given IP address. If + there are no vhosts defined for that address the + <code>NameVirtualHost</code> directive is ignored and an error + is logged. For an IP-based vhost the list in the hash table is + empty.</p> + + <p>Due to a fast hashing function the overhead of hashing an IP + address during a request is minimal and almost not existent. + Additionally the table is optimized for IP addresses which vary + in the last octet.</p> + + <p>For every vhost various default values are set. In + particular:</p> + + <ol> + <li>If a vhost has no <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code>, + <code class="directive"><a href="../mod/core.html#timeout">Timeout</a></code>, + <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code>, + <code class="directive"><a href="../mod/core.html#keepalive">KeepAlive</a></code>, + <code class="directive"><a href="../mod/core.html#maxkeepaliverequests">MaxKeepAliveRequests</a></code>, + <code class="directive"><a href="../mod/core.html#receivebuffersize">ReceiveBufferSize</a></code>, + or <code class="directive"><a href="../mod/core.html#sendbuffersize">SendBufferSize</a></code> + directive then the respective value is inherited from the + main_server. (That is, inherited from whatever the final + setting of that value is in the main_server.)</li> + + <li>The "lookup defaults" that define the default directory + permissions for a vhost are merged with those of the + main_server. This includes any per-directory configuration + information for any module.</li> + + <li>The per-server configs for each module from the + main_server are merged into the vhost server.</li> + </ol> + + <p>Essentially, the main_server is treated as "defaults" or a + "base" on which to build each vhost. But the positioning of + these main_server definitions in the config file is largely + irrelevant -- the entire config of the main_server has been + parsed when this final merging occurs. So even if a main_server + definition appears after a vhost definition it might affect the + vhost definition.</p> + + <p>If the main_server has no <code>ServerName</code> at this + point, then the hostname of the machine that <code class="program"><a href="../programs/httpd.html">httpd</a></code> + is running on is used instead. We will call the <em>main_server address + set</em> those IP addresses returned by a DNS lookup on the + <code>ServerName</code> of the main_server.</p> + + <p>For any undefined <code>ServerName</code> fields, a + name-based vhost defaults to the address given first in the + <code>VirtualHost</code> statement defining the vhost.</p> + + <p>Any vhost that includes the magic <code>_default_</code> + wildcard is given the same <code>ServerName</code> as the + main_server.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hostmatching" id="hostmatching">Virtual Host Matching</a></h2> + + <p>The server determines which vhost to use for a request as + follows:</p> + + <h3><a name="hashtable" id="hashtable">Hash table lookup</a></h3> + + <p>When the connection is first made by a client, the IP + address to which the client connected is looked up in the + internal IP hash table.</p> + + <p>If the lookup fails (the IP address wasn't found) the + request is served from the <code>_default_</code> vhost if + there is such a vhost for the port to which the client sent the + request. If there is no matching <code>_default_</code> vhost + the request is served from the main_server.</p> + + <p>If the IP address is not found in the hash table then the + match against the port number may also result in an entry + corresponding to a <code>NameVirtualHost *</code>, which is + subsequently handled like other name-based vhosts.</p> + + <p>If the lookup succeeded (a corresponding list for the IP + address was found) the next step is to decide if we have to + deal with an IP-based or a name-base vhost.</p> + + + + <h3><a name="ipbased" id="ipbased">IP-based vhost</a></h3> + + <p>If the entry we found has an empty name list then we have + found an IP-based vhost, no further actions are performed and + the request is served from that vhost.</p> + + + + <h3><a name="namebased" id="namebased">Name-based vhost</a></h3> + + <p>If the entry corresponds to a name-based vhost the name list + contains one or more vhost structures. This list contains the + vhosts in the same order as the <code>VirtualHost</code> + directives appear in the config file.</p> + + <p>The first vhost on this list (the first vhost in the config + file with the specified IP address) has the highest priority + and catches any request to an unknown server name or a request + without a <code>Host:</code> header field.</p> + + <p>If the client provided a <code>Host:</code> header field the + list is searched for a matching vhost and the first hit on a + <code>ServerName</code> or <code>ServerAlias</code> is taken + and the request is served from that vhost. A <code>Host:</code> + header field can contain a port number, but Apache always + matches against the real port to which the client sent the + request.</p> + + <p>If the client submitted a HTTP/1.0 request without + <code>Host:</code> header field we don't know to what server + the client tried to connect and any existing + <code>ServerPath</code> is matched against the URI from the + request. The first matching path on the list is used and the + request is served from that vhost.</p> + + <p>If no matching vhost could be found the request is served + from the first vhost with a matching port number that is on the + list for the IP to which the client connected (as already + mentioned before).</p> + + + + <h3><a name="persistent" id="persistent">Persistent connections</a></h3> + + <p>The IP lookup described above is only done <em>once</em> for a + particular TCP/IP session while the name lookup is done on + <em>every</em> request during a KeepAlive/persistent + connection. In other words a client may request pages from + different name-based vhosts during a single persistent + connection.</p> + + + + <h3><a name="absoluteURI" id="absoluteURI">Absolute URI</a></h3> + + <p>If the URI from the request is an absolute URI, and its + hostname and port match the main server or one of the + configured virtual hosts <em>and</em> match the address and + port to which the client sent the request, then the + scheme/hostname/port prefix is stripped off and the remaining + relative URI is served by the corresponding main server or + virtual host. If it does not match, then the URI remains + untouched and the request is taken to be a proxy request.</p> + + +<h3><a name="observations" id="observations">Observations</a></h3> + + <ul> + <li>A name-based vhost can never interfere with an IP-base + vhost and vice versa. IP-based vhosts can only be reached + through an IP address of its own address set and never + through any other address. The same applies to name-based + vhosts, they can only be reached through an IP address of the + corresponding address set which must be defined with a + <code>NameVirtualHost</code> directive.</li> + + <li><code>ServerAlias</code> and <code>ServerPath</code> + checks are never performed for an IP-based vhost.</li> + + <li>The order of name-/IP-based, the <code>_default_</code> + vhost and the <code>NameVirtualHost</code> directive within + the config file is not important. Only the ordering of + name-based vhosts for a specific address set is significant. + The one name-based vhosts that comes first in the + configuration file has the highest priority for its + corresponding address set.</li> + + <li>For security reasons the port number given in a + <code>Host:</code> header field is never used during the + matching process. Apache always uses the real port to which + the client sent the request.</li> + + <li>If a <code>ServerPath</code> directive exists which is a + prefix of another <code>ServerPath</code> directive that + appears later in the configuration file, then the former will + always be matched and the latter will never be matched. (That + is assuming that no <code>Host:</code> header field was + available to disambiguate the two.)</li> + + <li>If two IP-based vhosts have an address in common, the + vhost appearing first in the config file is always matched. + Such a thing might happen inadvertently. The server will give + a warning in the error logfile when it detects this.</li> + + <li>A <code>_default_</code> vhost catches a request only if + there is no other vhost with a matching IP address + <em>and</em> a matching port number for the request. The + request is only caught if the port number to which the client + sent the request matches the port number of your + <code>_default_</code> vhost which is your standard + <code>Listen</code> by default. A wildcard port can be + specified (<em>i.e.</em>, <code>_default_:*</code>) to catch + requests to any available port. This also applies to + <code>NameVirtualHost *</code> vhosts.</li> + + <li>The main_server is only used to serve a request if the IP + address and port number to which the client connected is + unspecified and does not match any other vhost (including a + <code>_default_</code> vhost). In other words the main_server + only catches a request for an unspecified address/port + combination (unless there is a <code>_default_</code> vhost + which matches that port).</li> + + <li>A <code>_default_</code> vhost or the main_server is + <em>never</em> matched for a request with an unknown or + missing <code>Host:</code> header field if the client + connected to an address (and port) which is used for + name-based vhosts, <em>e.g.</em>, in a + <code>NameVirtualHost</code> directive.</li> + + <li>You should never specify DNS names in + <code>VirtualHost</code> directives because it will force + your server to rely on DNS to boot. Furthermore it poses a + security threat if you do not control the DNS for all the + domains listed. There's <a href="../dns-caveats.html">more + information</a> available on this and the next two + topics.</li> + + <li><code>ServerName</code> should always be set for each + vhost. Otherwise A DNS lookup is required for each + vhost.</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="tips" id="tips">Tips</a></h2> + + <p>In addition to the tips on the <a href="../dns-caveats.html#tips">DNS Issues</a> page, here are + some further tips:</p> + + <ul> + <li>Place all main_server definitions before any + <code>VirtualHost</code> definitions. (This is to aid the + readability of the configuration -- the post-config merging + process makes it non-obvious that definitions mixed in around + virtual hosts might affect all virtual hosts.)</li> + + <li>Group corresponding <code>NameVirtualHost</code> and + <code>VirtualHost</code> definitions in your configuration to + ensure better readability.</li> + + <li>Avoid <code>ServerPaths</code> which are prefixes of + other <code>ServerPaths</code>. If you cannot avoid this then + you have to ensure that the longer (more specific) prefix + vhost appears earlier in the configuration file than the + shorter (less specific) prefix (<em>i.e.</em>, "ServerPath + /abc" should appear after "ServerPath /abc/def").</li> + </ul> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/details.html" title="English"> en </a> | +<a href="../ko/vhosts/details.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/details.html" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/details.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/details.html.ko.euc-kr new file mode 100644 index 00000000..1ba167ee --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/details.html.ko.euc-kr @@ -0,0 +1,384 @@ +<?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="./">ȣƮ</a></div><div id="page-content"><div id="preamble"><h1>ȣƮ ã ڼ </h1> +<div class="toplang"> +<p><span> : </span><a href="../en/vhosts/details.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/details.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/details.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate"> ֽ ƴմϴ. + ֱٿ ϼ.</div> + + + <p>ȣƮ ڵ <strong>ġ 1.3</strong> ٽ + ۼǾ. ġ û ȣƮ + ϴ Ѵ. ο <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> þ Ͽ + ȣƮ 1.3 .</p> + + <p> ϴ ʰ <cite>ϰԸ</cite> + ϰ ʹٸ, <a href="examples.html"></a> ϶.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#configparsing"> б</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#hostmatching">ȣƮ ã</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#tips"></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="configparsing" id="configparsing"> б</a></h2> + + <p><code><VirtualHost></code> + <em>ּ</em> . <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + κ ȣƮ θ.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, + <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code>, + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> þ + ִ. þ + ( ) þ ȿϴ.</p> + + <p>ּ <code>Listen</code> ⺻ 80̴. ּ + <code>ServerPath</code> <code>ServerAlias</code> + ⺻ . <code>ServerName</code> ⺻ + IP ̴ּ.</p> + + <p>ּ Listen þ ΰ Ѵ. ù° + ġ ⺻ Ʈ Ʈ ϴ ̴. ° + ̷ URI Ʈ ȣ ϴ ̴.</p> + + <p>ּ ȣƮ Ʈ ġ ٸ + Ʈ <em>ʴ´</em>.</p> + + <p><code>VirtualHost</code> þ Ʈ ִ. + Ʈ ּ ֱ <code>Listen</code> + Ѵ. Ư Ʈ <code>*</code> Ʈ + Īϴ ϵī̴. (DNS ˻ <code>A</code> + ڵ带 Ͽ) ȣƮ ּҸ ĪϿ ȣƮ + <em>ּ(address set)</em>̶ θ.</p> + + <p>Ư IP ּҿ <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> þ ٸ + ּҸ ϴ ù° ȣƮ IP ȣƮ Ѵ. + IP ּҿ ϵī <code>*</code> ִ.</p> + + <p≯ ȣƮ Ѵٸ ̸ ȣƮ + IP ּҸ <code>NameVirtualHost</code> þ + ؾ <em>Ѵ</em>. , <code>NameVirtualHost</code> + þ ̸ ȣƮ ȣƮ(CNAME) شϴ + IP ּҸ ؾ Ѵ.</p> + + <p>Ư IP:Ʈ ֿ <code>NameVirtualHost</code> + þ Ѵٸ, <code>NameVirtualHost</code> þ + <code>VirtualHost</code> þ ִ.</p> + + <p><code>NameVirtualHost</code> <code>VirtualHost</code> + þ ߿ ʱ ( + <em></em> ּտ <code>VirtualHost</code> + ߿ϴ. Ʒ ):</p> + +<table><tr> +<td><div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <VirtualHost 111.22.33.44><br /> + # A<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.44><br /> + # B<br /> + ...<br /> + </VirtualHost><br /> + <br /> + NameVirtualHost 111.22.33.55<br /> + <VirtualHost 111.22.33.55><br /> + # C<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # D<br /> + ...<br /> + </VirtualHost> +</code></p></div></td> +<td><div class="example"><p><code> + <VirtualHost 111.22.33.44><br /> + # A<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # C<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.44><br /> + # B<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # D<br /> + ...<br /> + </VirtualHost><br /> + <br /> + NameVirtualHost 111.22.33.44<br /> + NameVirtualHost 111.22.33.55<br /> + <br /> +</code></p></div></td> +</tr></table> + + + <p>( б ϴ.)</p> + + <p><code>VirtualHost</code> þ , ȣƮ + <code>VirtualHost</code> þ Ʈ ⺻ + <code>Listen</code> Ѵ.</p> + + <p><code>VirtualHost</code> þ ̸ + ּտ Ѵٸ <code>ServerAlias</code> Ѵ + ( ٸ <code>ServerAlias</code> ʴ´). + ȣƮ ߰ <code>Listen</code> ּ + Ʈ ϶.</p> + + <p>Ҷ IP ּ ؽ̺ ߰Ѵ. + <code>NameVirtualHost</code> þ IP ּҸ ϸ + IP ּҿ ̸ ȣƮ Ѵ. + ּҿ ȣƮ ٸ <code>NameVirtualHost</code> + þ ϰ α Ѵ. IP ȣƮ + ؽ̺ ߰ ʴ´.</p> + + <p> ؽԼ ϱ û IP ּҸ ؽϴ + δ . ؽ̺ IP ּ κ + ̿ ȭִ.</p> + + <p>ȣƮ ⺻ ȴ. Ư:</p> + + <ol> + <li>ȣƮ <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code>, + <code class="directive"><a href="../mod/core.html#resourceconfig">ResourceConfig</a></code>, + <code class="directive"><a href="../mod/core.html#accessconfig">AccessConfig</a></code>, + <code class="directive"><a href="../mod/core.html#timeout">Timeout</a></code>, + <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code>, + <code class="directive"><a href="../mod/core.html#keepalive">KeepAlive</a></code>, + <code class="directive"><a href="../mod/core.html#maxkeepaliverequests">MaxKeepAliveRequests</a></code>, + <code class="directive"><a href="../mod/core.html#sendbuffersize">SendBufferSize</a></code> + þ ٸ ּ ش ´. (, + ּ Ѵ.)</li> + + <li>ȣƮ 丮 ⺻ ϴ " + ⺻(lookup defaults)" ּ . + 丮 (per-directory configuration) + شȴ.</li> + + <li> (per-server config) ּ + ȣƮ ģ.</li> + </ol> + + <p>⺻ ּ ȣƮ "⺻" Ȥ "" + ȴ. Ͽ ּ ϴ ġ . + ġ ּ оδ. + ּ ǰ ȣƮ ڿ ͵ ȣƮ + ǿ ش.</p> + + <p>ּ <code>ServerName</code> ٸ ϴ + ǻ ȣƮ Ѵ. ּ + <code>ServerName</code> DNS ̻Ͽ IP ּҵ + <em>ּ ּ</em>̶ θ.</p> + + <p≯ ȣƮ <code>ServerName</code> + ȣƮ ϴ <code>VirtualHost</code> + ó ּҸ ⺻ Ѵ.</p> + + <p>Ư <code>_default_</code> Ʈī带 ϴ + ȣƮ ּ <code>ServerName</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="hostmatching" id="hostmatching">ȣƮ ã</a></h2> + + <p> Ʒ ȣƮ û + ó Ѵ:</p> + + <h3><a name="hashtable" id="hashtable">ؽ̺ ã</a></h3> + + <p>Ŭ̾Ʈ ó ϸ IP ּҸ IP + ؽ̺ ã´.</p> + + <p>IP ּҸ ã Ŭ̾Ʈ û Ʈ + شϴ ȣƮ ִٸ, <code>_default_</code> ȣƮ + û Ѵ. <code>_default_</code> ȣƮ + ٸ ּ û Ѵ.</p> + + <p>ؽ̺ IP ּҰ Ʈ ȣ + <code>NameVirtualHost *</code> ش ִ. + ̸ ȣƮó óѴ.</p> + + <p>ãҴٸ (Ͽ IP ּҿ شϴ ã), + IP ȣƮ ̸ ȣƮ Ѵ.</p> + + + + <h3><a name="ipbased" id="ipbased">IP ȣƮ</a></h3> + + <p>ã ̸ ٸ IP ȣƮ̴. + ̻ ۾ ʿ, ȣƮ û óѴ.</p> + + + + <h3><a name="namebased" id="namebased"≯ ȣƮ</a></h3> + + <p≯ Ͽ Ѱ ̻ ȣƮ ԵǸ + ̸ ȣƮ̴. Ͽ ȣƮ + <code>VirtualHost</code> ġѴ.</p> + + <p>Ͽ ù° ȣƮ(Ͽ ش IP ּҸ + ϴ ù° ȣƮ) 켱 , + ų <code>Host:</code> û + óѴ.</p> + + <p>Ŭ̾Ʈ <code>Host:</code> ָ, Ͽ + ù° <code>ServerName</code>̳ + <code>ServerAlias</code> ϴ ȣƮ û + Ѵ. <code>Host:</code> Ʈ ȣ + , ġ Ŭ̾Ʈ û Ʈ + ã´.</p> + + <p>Ŭ̾Ʈ <code>Host:</code> HTTP/1.0 û + ϸ Ŭ̾Ʈ Ϸ + û URI شϴ <code>ServerPath</code> ִ ã´. + Ͽ ã θ ϰ, ȣƮ + û Ѵ.</p> + + <p>ϴ ȣƮ ã ٸ, (̹ տ ߵ) + Ŭ̾Ʈ IP Ͽ ġϴ Ʈ ȣ + ϴ ù° ȣƮ û Ѵ.</p> + + + + <h3><a name="persistent" id="persistent"> </a></h3> + + <p>IP ѵ Ư TCP/IP Ǵ <em>ѹ</em> + ã, ̸ KeepAlive/ ᵿ <em></em> û + ã´. , Ŭ̾Ʈ ᵿ ̸ + ȣƮ û ִ.</p> + + + + <h3><a name="absoluteURI" id="absoluteURI"> URI</a></h3> + + <p>û URI URḬ Ŭ̾Ʈ û + ȣƮ Ʈ ּ Ư ȣƮ شϸ, + ּ Ȥ ȣƮ URI Ŵ/ȣƮ/Ʈ + κ URI Ѵ. شϴ + ּ ȣƮ ٸ URI ״ ΰ û + Ͻ û óѴ.</p> + + +<h3><a name="observations" id="observations"></a></h3> + + <ul> + <li≯ ȣƮ IP ȣƮ ο + ʴ´. IP ȣƮ ڽ ̸ + IP ּҿܿ ּҷε . ̸ + ȣƮ . ̸ ȣƮ + <code>NameVirtualHost</code> þ ּ + IP ּҸ ؼ ִ.</li> + + <li>IP ȣƮ <code>ServerAlias</code> + <code>ServerPath</code> ˻ ʴ´.</li> + + <li>Ͽ ̸ ȣƮ, IP ȣƮ, + <code>_default_</code> ȣƮ, <code>NameVirtualHost</code> + þ ߿ ʴ. Ư ּտ + ̸ ȣƮ ߿ϴ. Ͽ + տ ̸ ȣƮ ڽ ּտ + 켱 .</li> + + <li> <code>Host:</code> Ե Ʈ + ȣ ʴ´. ġ Ŭ̾Ʈ + û Ʈ Ѵ.</li> + + <li>( ̸ <code>Host:</code> ٰ + ϸ,) <code>ServerPath</code> þ Ͽ + ڿ ٸ <code>ServerPath</code> þ պκ + Īϴ տ þ Ѵ.</li> + + <li> IP ȣƮ ּҸ , + Ͽ տ ȣƮ Ѵ. ̷ + ƹ Ͼ ִ. ̷ Ȳ ߰ϸ + αϿ Ѵ.</li> + + <li><code>_default_</code> ȣƮ û IP ּ<em></em> + Ʈ ȣ شϴ ȣƮ û óѴ. + Ŭ̾Ʈ û Ʈ ȣ <code>_default_</code> + ȣƮ Ʈ ȣ(⺻ <code>Listen</code>) + û óѴ. Ʈ û̶ + (<em> </em>, <code>_default_:*</code>) ϵī + Ʈ ִ. <code>NameVirtualHost *</code> + ȣƮ .</li> + + <li>ּ Ŭ̾Ʈ IP ּҿ Ʈ ȣ + شϴ (<code>_default_</code> ȣƮ Ͽ) + ȣƮ û Ѵ. , ּ + ( Ʈ شϴ <code>_default_</code> ȣƮ + ٸ) ּ/Ʈ ֿ û óѴ.</li> + + <li>Ŭ̾Ʈ (<em> </em>, <code>NameVirtualHost</code> + þ) ̸ ȣƮ ּ( Ʈ) + <code>Host:</code> ų + û û <em></em> <code>_default_</code> + ȣƮ ּ ó ʴ´.</li> + + <li>Ҷ DNS + <code>VirtualHost</code> þ DNS ̸ . + Դٰ DNS ʴ´ٸ + Ȼ 赵 ִ. ̿ <a href="../dns-caveats.html"></a> ִ.</li> + + <li> ȣƮ <code>ServerName</code> + ؾ Ѵ. ȱ ȣƮ DNS ã ȴ.</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="tips" id="tips"></a></h2> + + <p><a href="../dns-caveats.html#tips">DNS </a> + ߰ Ʒ ִ:</p> + + <ul> + <li> ּ Ǹ <code>VirtualHost</code> տ + ξ. ( б ϴ. ȱ ߿ + ȣƮ ̿ ǰ ȣƮ + ֱ ȥ.)</li> + + <li>б ϵ شϴ <code>NameVirtualHost</code> + <code>VirtualHost</code> ǵ .</li> + + <li><code>ServerPath</code> ٸ <code>ServerPath</code> + պκ Īϴ 츦 ϶. ٸ Ͽ + պκ ( ڼ) ȣƮ ª ( ڼ) + ȣƮ տ ξ. (<em> </em>, + "ServerPath /abc" "ServerPath /abc/def" ξ + Ѵ.</li> + </ul> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../en/vhosts/details.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/details.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/details.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/apache2/manual/vhosts/details.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/details.html.tr.utf8 new file mode 100644 index 00000000..0049164b --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/details.html.tr.utf8 @@ -0,0 +1,401 @@ +<?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>Sanal Konak Eşlemenin Derinliğine İncelenmesi - 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="./">Sanal Konaklar</a></div><div id="page-content"><div id="preamble"><h1>Sanal Konak Eşlemenin Derinliğine İncelenmesi</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/details.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/details.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/details.html" title="Türkçe"> tr </a></p> +</div> + + + <p>Sanal konak kodu <strong>Apache 1.3</strong> sürümünde baştan yeniden + yazıldı. Bu belgede, bir istek aldığında Apache’nin hangi sanal konak + ile hizmet sunacağına nasıl karar verdiği açıklanmaya çalışılmıştır. + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> yönergesi sayesinde + sanal konak yapılandırması 1.3 sürümünün öncesine göre daha kolay ve + daha güvenilir hale gelmiştir.</p> + + <p>Sanal konakların nasıl çalıştığını öğrenmeden sadece çalıştırmak + isterseniz doğrudan <a href="examples.html">örneklerin bulunduğu + sayfaya</a> bakabilirsiniz.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#configparsing">Yapılandırma Dosyasının Çözümlenmesi</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#hostmatching">Sanal Konağın Belirlenmesi</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#tips">İpuçları</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="configparsing" id="configparsing">Yapılandırma Dosyasının Çözümlenmesi</a></h2> + + <p>Bu belgede <code><VirtualHost></code> bölümleri dışında kalan + tanımlardan bahsederken <em>ana_sunucu</em>, <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümlerindeki tanımlamalardan + bahsederken <em>sankonlar</em> diyeceğiz.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, + <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> ve + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> yönergeleri bir sunucu + yapılandırmasının her yerinde karşımıza çıkabilir. Bununla birlikte, + sunucu dahilinde son göründükleri yerlerde önceki eşdeğerlerini geçersiz + kılarlar.</p> + + <p><code>Listen</code> yönergesinin ana_sunucu için öntanımlı değeri + 80’dir. <code>ServerPath</code> ve <code>ServerAlias</code> + yönergelerinin ana_sunucu için öntanımlı değerleri yoktur. Öntanımlı + <code>ServerName</code> değeri ise sunucunun IP adresinden elde + edilir.</p> + + <p>Ana_sunucu <code>Listen</code> yönergesinin iki işlevi vardır. Biri + Apache’nin dinleyeceği öntanımlı ağ portunu belirlemek, diğeri ise + yönlendirmeler sırasında mutlak URI’lerde kullanılan port numarasını + belirlemektir.</p> + + <p>Ana_sunucunun aksine sankonların portları Apache‘nin dinleyeceği + portlar üzerinde etkili değildir.</p> + + <p><code>VirtualHost</code> yönergesinde görünen her adresin seçimlik bir + portu olabilir. Eğer bir port belirtilmemişse öntanımlı olarak + ana_sunucunun son <code>Listen</code> yönergesinin değeri kullanılır. + Port olarak <code>*</code> belirtildiği takdirde bütün portlar dinlenir. + Adreslerin tamamını (DNS sorgularındaki çoklu A kayıtları dahil) içeren + kümeye sankonların <em>adres kümesi</em> denir.</p> + + <p><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> yönergesi ilk + sankonun IP adresi için kullanılmadığı takdirde bu IP adresine sahip ilk + sankon IP’ye dayalı sankon olarak ele alınır. IP adresi olarak + <code>*</code> belirtmek de mümkündür.</p> + + <p>Eğer isme dayalı sankonlar kullanılacaksa <code>NameVirtualHost</code> + yönergesinin bu isme dayalı sankonların IP adresi kümesini içermesi + <em>gerekir</em>. Başka bir deyişle, yapılandırma dosyanızın + <code>NameVirtualHost</code> yönergesine sankonların sunucu isimlerinin + karşı düştüğü IP adresini yazmalısınız.</p> + + <p>Çok sayıda <code>NameVirtualHost</code> yönergesi belirtebilirse de her + IP:port çifti için birden fazla <code>NameVirtualHost</code> yönergesi + belirtilmemelidir.</p> + + <p>Aşağıdaki iki örneğin eşdeğer olması için <code>NameVirtualHost</code> + ve <code>VirtualHost</code> yönergelerinin sıralamasının bir önemi + yoktur. (Sadece <em>tek</em> adreslik küme içindeki + <code>VirtualHost</code> yönergelerinin sırası önemlidir; aşağıya + bakınız:)</p> + +<table><tr> +<td><div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <VirtualHost 111.22.33.44><br /> + # sunucu A<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.44><br /> + # sunucu B<br /> + ...<br /> + </VirtualHost><br /> + <br /> + NameVirtualHost 111.22.33.55<br /> + <VirtualHost 111.22.33.55><br /> + # sunucu C<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # sunucu D<br /> + ...<br /> + </VirtualHost> +</code></p></div></td> +<td><div class="example"><p><code> + <VirtualHost 111.22.33.44><br /> + # sunucu A<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # sunucu C<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.44><br /> + # sunucu B<br /> + ...<br /> + </VirtualHost><br /> + <VirtualHost 111.22.33.55><br /> + # sunucu D<br /> + ...<br /> + </VirtualHost><br /> + <br /> + NameVirtualHost 111.22.33.44<br /> + NameVirtualHost 111.22.33.55<br /> + <br /> +</code></p></div></td> +</tr></table> + + + <p>(Okuma kolaylığı bakımından soldaki sürümü tercih etmenizi öneririz.) + </p> + + <p><code>VirtualHost</code> yönergesi çözümlendikten sonra sankon + sunucusuna yönergedeki ilk isme atanmış portun öntanımlı olduğu bir + <code>Listen</code> verilir.</p> + + <p>Eğer tüm <code>VirtualHost</code> isimlerinin listesi aynı adres + kümesine çözümleniyorsa bu isimler birer <code>ServerAlias</code> gibi + ele alınırlar (bir <code>ServerAlias</code> yönergesi ile geçersiz + kılınmadıkça). Bir sankon tanımından sonra gelen <code>Listen</code> + satırlarının o sankonun adres kümesine atanmış portlara bir etkisinin + olmayacağına dikkat ediniz.</p> + + <p>İsim listeleri IP adreslerine göre gruplanır ve bir çiftler tablosuna + kaydedilir. Eğer IP adresi bir <code>NameVirtualHost</code> yönergesinde + kullanılmışsa, liste bu IP adresi için tanımlanmış tüm sankonları + içerir. Eğer bu IP adresinin tanımlandığı bir sankon yoksa o + <code>NameVirtualHost</code> yönergesi yoksayılır ve günlüğe bir hata + kaydı düşülür. IP’ye dayalı sankonlar için çiftler listesinde isim + alanları boştur.</p> + + <p>Çiftler listesini işleyen işlevin hızı nedeniyle bir istek sırasında IP + adresine göre gruplama yaparken kaynak harcaması en düşük düzeyde olur + hatta neredeyse hiç olmaz. Ek olarak, tablo, IP adresinin son + sekizlisindeki değişikliklere göre de en iyilenir.</p> + + <p>Her sankon için bazı değerler öntanımlı olarak atanır. Bunların + başlıcaları:</p> + + <ol> + <li>Sankon bir <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code> + yönergesi içermiyorsa, + <code class="directive"><a href="../mod/core.html#timeout">Timeout</a></code>, + <code class="directive"><a href="../mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code>, + <code class="directive"><a href="../mod/core.html#keepalive">KeepAlive</a></code>, + <code class="directive"><a href="../mod/core.html#maxkeepaliverequests">MaxKeepAliveRequests</a></code>, + <code class="directive"><a href="../mod/core.html#receivebuffersize">ReceiveBufferSize</a></code> ve + <code class="directive"><a href="../mod/core.html#sendbuffersize">SendBufferSize</a></code> yönergeleri için + öntanımlı değerler ana_sunucudaki eşdeğerlerinden miras alınır. (Yani, + bu yönergeler için ana_sunucudaki son değerler miras alınır.)</li> + + <li>Sankon için öntanımlı dizin erişim izinlerinin tanımlandığı "arama + öntanımlıları" ana_sunucununkilere katılır. Buna her modülün dizinlere + özgü yapılandırma bilgileri dahildir.</li> + + <li>Her modülün ana_sunucudaki sunuculara özgü yapılandırmaları sankon + sunucusununkilerle katıştırılır.</li> + </ol> + + <p>Esasen, ana_sunucu, sankon sunucularını oluştururken bir öntanımlılar + listesi veya öntanımlı değerlere dayanak noktası olarak ele alınır. + Fakat bu ana_sunucu tanımlarının yapılandırma dosyasındaki yerlerinin + saptanmasının konumuzla ilgisi yoktur; ana_sunucu yapılandırmasının + tamamı son katıştırma yapılacağı zaman çözümlenir. Bu bakımdan, + ana_sunucu tanımlarından bir kısmı sankon tanımlarından sonra yer alsa + bile sankon tanımlarında etkili olabilir.</p> + + <p>Eğer, bu noktada ana_sunucu hiçbir <code>ServerName</code> satırı + içermiyorsa <code class="program"><a href="../programs/httpd.html">httpd</a></code> programının çalıştığı makinenin + konak ismi öntanımlıdır. Ana_sunucunun <code>ServerName</code> için + yaptığı DNS sorgusundan dönen IP adreslerine <em>ana_sunucu adres + kümesi</em> diyoruz.</p> + + <p>Tanımsız <code>ServerName</code> alanları için bir isme dayalı sankon, sankonu tanımlayan <code>VirtualHost</code> yönergesinde belirtilen ilk adresi öntanımlı değer kabul eder.</p> + + <p>Sihirli <code>_default_</code> sankonları için ana_sunucunun <code>ServerName</code> değeri kullanılı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="hostmatching" id="hostmatching">Sanal Konağın Belirlenmesi</a></h2> + + <p>Sunucu bir istek durumunda hangi sankonun kullanılacağını şöyle + belirler:</p> + + <h3><a name="hashtable" id="hashtable">Değer çiftleri tablosu aranır</a></h3> + + <p>Bir istemci tarafından bağlantı ilk yapıldığında önce IP-isim çiftleri + tablosunda istemcinin bağlandığı IP adresi için bir arama yapılır.</p> + + <p>Arama başarısız olursa (IP adresi yoksa) hizmet, istekte belirtilen + port için bir <code>_default_</code> sankon varsa, o sankondan, yoksa + ana_sunucudan sunulur.</p> + + <p>Eğer çiftler tablosunda IP adresi yoksa port numarası ile eşleştirme + çabası ayrıca, diğer isme dayalı sanal konaklardaki gibi ard arda ele + alınmayı gerektiren <code>NameVirtualHost *</code> durumundaki bir + girdiyle sonuçlanabilir.</p> + + <p>Arama sonucunda tabloda IP adresi bulunursa sonraki adım hizmetin bir + IP’ye dayalı sankondan mı yoksa isme dayalı bir sankondan mı + sunulacağına karar vermektir.</p> + + + + <h3><a name="ipbased" id="ipbased">IP’ye dayalı sankon</a></h3> + + <p>Eğer tabloda bulduğumuz girdinin isim alanları boşsa bir IP’ye dayalı + sanal konak bulmuşuz demektir. Artık karar vermek için başka bir şey + yapmaya gerek yoktur ve istek bu sankondan sunulur.</p> + + + + <h3><a name="namebased" id="namebased">İsme dayalı sankon</a></h3> + + <p>Tabloda bulduğumuz girdi için bir isim listesi varsa bir isme dayalı + sankon sözkonusudur. Bu isim listesi, sankonları, ilgili + <code>VirtualHost</code> bölümlerinin yapılandırma dosyasında yer alış + sırasına göre içerir.</p> + + <p>Bu listedeki ilk sankon (yapılandırma dosyasında belirtilen IP adresine + sahip ilk sankon) en yüksek önceliğe sahiptir ve sunucu ismi + belirtilmeyen veya <code>Host:</code> başlık alanı olmayan istekleri bu + sankon karşılar.</p> + + <p>Eğer istemci bir <code>Host:</code> başlık alanı ile istek yapmışsa + liste bu sankon için aranır ve hizmet <code>ServerName</code> veya + <code>ServerAlias</code> ile ilk eşleşmenin sağlandığı sankondan + sunulur. <code>Host:</code> alanında bir port belirtilebilirse de Apache + daima istemcinin isteği gönderdiği portu gerçek port kabul eder.</p> + + <p>Eğer istemci <code>Host:</code> başlık alanı bulunmayan bir HTTP/1.0 + isteği yapmışsa istemcinin hangi sankona bağlanmayı denediğini bilemeyiz + ve istekteki URI ile mevcut <code>ServerPath</code> değerini + eşleştirmeye çalışırız. Listedekilerden ilk eşleşen yola sahip sankondan + hizmeti sunarız.</p> + + <p>İstekle eşleşen bir sankon bulunamazsa IP listesinde istemcinin + bağlandığı portla eşleşen ilk sankondan hizmeti sunarız.</p> + + + + <h3><a name="persistent" id="persistent">Kalıcı bağlantılar</a></h3> + + <p>Yukarıda açıklanan IP araması belli bir TCP/IP oturumunda bir defaya + mahsus yapıldığı halde bir kalıcı/KeepAlive bağlantı sırasında her istek + için ayrı bir arama yapılır. Başka bir deyişle, bir istemci tek bir + kalıcı bağlantı üzerinde farklı isme dayalı sankonlardan sayfa talebinde + bulunabilir.</p> + + + + <h3><a name="absoluteURI" id="absoluteURI">Mutlak URI</a></h3> + + <p>Eğer istekte belirtilen URI bir mutlak URI ise ve istek yapılan konak + ismi ve port ana sunucuyla veya sankonlardan biriyle eşleşiyorsa, + şema/konakadı/port öneki ayrılır ve elde edilen göreli URI ilgili + sankondan veya ana sunucudan sunulur. Eğer bir eşleşme sağlanamazsa + URI’ye dokunulmaz ve istek bir vekil isteği olarak ele alınır.</p> + + +<h3><a name="observations" id="observations">İzlenimler</a></h3> + + <ul> + <li>Bir isme dayalı sankon asla bir IP’ye dayalı sankon ile (veya tersi) + etkileşime girmez. IP’ye dayalı sankonlara sadece kendi adres + kümesindeki bir IP adresi üzerinden erişilebilir, asla başka bir + adresten erişilemez. Aynısı isme dayalı sankonlara da uygulanır; + onlara sadece bir <code>NameVirtualHost</code> yönergesi ile + tanımlanmış adres kümesindeki bir IP adresi üzerinden + erişilebilir.</li> + + <li>Bir IP’ye dayalı sankon için asla <code>ServerAlias</code> ve + <code>ServerPath</code> değerine bakılmaz.</li> + + <li>Yapılandırma dosyası içinde isme/IP’ye dayalı ve + <code>_default_</code> sankonlar ile <code>NameVirtualHost</code> + yönergelerinin yer alış sırasının birbirlerine göre bir önemi yoktur. + Sıralama sadece aynı IP adresine sahip isme dayalı sankonlar arasında + önemlidir. Aynı adres kümesine mensup isme dayalı sankonlardan + yapılandırma dosyasında ilk sırada yer alanı en yüksek önceliğe + sahiptir.</li> + + <li>Güvenlik saikiyle, eşleştirme işlemi sırasında <code>Host:</code> + başlık alanında belirtilen port asla kullanılmaz. Apache daima + istemcinin bağlantı kurduğu gerçek portu kullanır.</li> + + <li>Değeri başka bir <code>ServerPath</code> yönergesinin değeri için + önek olan bir <code>ServerPath</code> yönergesi yapılandırma + dosyasında daha önce yer alıyorsa sonrakiyle eşleşme asla + gerçekleşmez. (Bu belirsizliği giderecek bir <code>Host:</code> başlık + alanının mümkün olmadığı varsayılır.)</li> + + <li>Eğer tek bir IP adresine sahip IP’ye dayalı iki sankon varsa eşleşme + daima yapılandırma dosyasında ilk yer alanla gerçekleşir. Böyle bir + şey kasten yapılmaz. Sunucu böyle bir durumu saptadığında hata + günlüğünde bir uyarı verecektir.</li> + + <li>Bir <code>_default_</code> sankon sadece istekle eşleşen bir IP + adresi bulunamadığında port numarası eşleştiği takdirde isteğe hizmet + sunabilir. Port düzeyinde eşleşmenin olabilmesi için isteğin geldiği + port ile sankon için belirtilen port eşleşmelidir. Olası tüm portlarla + eşleşmeyi sağlamak üzere yıldız imi (<code>_default_:*</code> + şeklinde) kullanılabilir. Aynı şey <code>NameVirtualHost *</code> + sankonlarına da uygulanır.</li> + + <li>Ana_sunucunun bir isteğe hizmet sunabilmesi için istemcinin + bağlandığı IP adresi ve port hiçbir yerde belirtilmemiş ve + <code>_default_</code> dahil hiçbir sankon ile eşleşme sağlanamamış + olmalıdır. Başka bir deyişle, istemcinin bağlandığı port ile eşleşen + bir <code>_default_</code> sankon olmadıkça adres ve port belirtmeyen + bir isteğe ana_sunucu yanıt verecektir.</li> + + <li><code>Host:</code> başlık alanı içermeyen veya hedefi bilinmeyen bir + istek geldiği takdirde, eğer bu istemcinin bağlandığı adres ve port + için (örneğin, <code>NameVirtualHost</code> ile) tanımlanmış bir isme + dayalı sankon varsa bu isteğe ne ana_sunucu ne de bir + <code>_default_</code> sankon hizmet sunabilir.</li> + + <li><code>VirtualHost</code> yönergelerinde asla DNS isimleri + belirtmemelisiniz. Aksi takdirde sunucuyu başlatma sırasında DNS + sorgusu yapmaya zorlamış olursunuz. Listelenen tüm alanlar için DNS + üzerinde tam denetime sahip değilseniz bu ayrıca bir güvenlik + tehdidine yol açar. Bu konuda daha ayrıntılı bilgi edinmek için <a href="../dns-caveats.html">DNS ile ilgili konular ve Apache</a> + belgesine bakınız.</li> + + <li><code>ServerName</code> her sankon için ayrı ayrı belirlenmiş + olmalıdır. Aksi takdirde her sankon için bir DNS sorgusu gerekir.</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="tips" id="tips">İpuçları</a></h2> + + <p><a href="../dns-caveats.html#tips">DNS konuları</a> sayfasındaki + ipuçlarına ilaveten burada da bazı ipuçları bulacaksınız:</p> + + <ul> + <li>Ana_sunucu tanımlarının hepsini <code>VirtualHost</code> + tanımlarının öncesinde bitirin. Bu ayrıca yapılandırmanızın + okunabilirliğini de arttırır; <code>VirtualHost</code> tanımlarının + sonrasına sarkan yapılandırmaların katıştırılması işlemi tüm sanal + konakları etkileyebilen tanımlar bakımından bir + karışıklığa/belirsizliğe sebep olabilir.)</li> + + <li>Birbirleriyle ilgili <code>NameVirtualHost</code> ve + <code>VirtualHost</code> tanımlarını okunabilirliği arttırmak için + gruplayın.</li> + + <li>Değeri başka bir <code>ServerPath</code> için önek olan tanımlamalar + yapmaktan kaçının. Bundan kaçınamıyorsanız, yolu uzun olanı yolu kısa + olanın öncesine yerleştirin. Örneğin, "ServerPath /abc/def" önce + "ServerPath /abc" sonra yer alsın.</li> + </ul> + +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/details.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/details.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/details.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/apache2/manual/vhosts/examples.html b/rubbos/app/apache2/manual/vhosts/examples.html new file mode 100644 index 00000000..ae55ad07 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/examples.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: examples.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: examples.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: examples.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/examples.html.en b/rubbos/app/apache2/manual/vhosts/examples.html.en new file mode 100644 index 00000000..317294dc --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/examples.html.en @@ -0,0 +1,654 @@ +<?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>VirtualHost Examples - 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="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>VirtualHost Examples</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/vhosts/examples.html" title="English"> en </a> | +<a href="../ko/vhosts/examples.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/examples.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + + <p>This document attempts to answer the commonly-asked questions about + setting up virtual hosts. These scenarios are those involving multiple + web sites running on a single server, via <a href="name-based.html">name-based</a> or <a href="ip-based.html">IP-based</a> virtual hosts. + </p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#purename">Running several name-based web + sites on a single IP address.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#twoips">Name-based hosts on more than one + IP address.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#intraextra">Serving the same content on + different IP addresses (such as an internal and external + address).</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#port">Running different sites on different + ports.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ip">IP-based virtual hosting</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ipport">Mixed port-based and ip-based virtual + hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#mixed">Mixed name-based and IP-based + vhosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#proxy">Using <code>Virtual_host</code> and + mod_proxy together</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#default">Using <code>_default_</code> + vhosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#migrate">Migrating a name-based vhost to an + IP-based vhost</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#serverpath">Using the <code>ServerPath</code> + directive</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="purename" id="purename">Running several name-based web + sites on a single IP address.</a></h2> + + <p>Your server has a single IP address, and multiple aliases (CNAMES) + point to this machine in DNS. You want to run a web server for + <code>www.example1.com</code> and <code>www.example2.org</code> on this + machine.</p> + + <div class="note"><h3>Note</h3><p>Creating virtual + host configurations on your Apache server does not magically + cause DNS entries to be created for those host names. You + <em>must</em> have the names in DNS, resolving to your IP + address, or nobody else will be able to see your web site. You + can put entries in your <code>hosts</code> file for local + testing, but that will work only from the machine with those + hosts entries.</p> + </div> + + <div class="example"><h3>Server configuration</h3><p><code> + + + # Ensure that Apache listens on port 80<br /> + Listen 80<br /> + <br /> + # Listen for virtual host requests on all IP addresses<br /> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + <br /> + # Other directives here<br /> + <br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + <br /> + # Other directives here<br /> + <br /> + </span> + </VirtualHost> + </code></p></div> + + <p>The asterisks match all addresses, so the main server serves no + requests. Due to the fact that <code>www.example1.com</code> is first + in the configuration file, it has the highest priority and can be seen + as the <cite>default</cite> or <cite>primary</cite> server. That means + that if a request is received that does not match one of the specified + <code>ServerName</code> directives, it will be served by this first + <code>VirtualHost</code>.</p> + + <div class="note"> + <h3>Note</h3> + + <p>You can, if you wish, replace <code>*</code> with the actual + IP address of the system. In that case, the argument to + <code>VirtualHost</code> <em>must</em> match the argument to + <code>NameVirtualHost</code>:</p> + + <div class="example"><p><code> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + # etc ... + </code></p></div> + + <p>However, it is additionally useful to use <code>*</code> + on systems where the IP address is not predictable - for + example if you have a dynamic IP address with your ISP, and + you are using some variety of dynamic DNS solution. Since + <code>*</code> matches any IP address, this configuration + would work without changes whenever your IP address + changes.</p> + </div> + + <p>The above configuration is what you will want to use in almost + all name-based virtual hosting situations. The only thing that this + configuration will not work for, in fact, is when you are serving + different content based on differing IP addresses or ports.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="twoips" id="twoips">Name-based hosts on more than one + IP address.</a></h2> + + <div class="note"> + <h3>Note</h3><p>Any of the + techniques discussed here can be extended to any number of IP + addresses.</p> + </div> + + <p>The server has two IP addresses. On one (<code>172.20.30.40</code>), we + will serve the "main" server, <code>server.domain.com</code> and on the + other (<code>172.20.30.50</code>), we will serve two or more virtual hosts.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + Listen 80<br /> + <br /> + # This is the "main" server running on 172.20.30.40<br /> + ServerName server.domain.com<br /> + DocumentRoot /www/mainserver<br /> + <br /> + # This is the other address<br /> + NameVirtualHost 172.20.30.50<br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + <br /> + # Other directives here ...<br /> + <br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + <br /> + # Other directives here ...<br /> + <br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Any request to an address other than <code>172.20.30.50</code> will be + served from the main server. A request to <code>172.20.30.50</code> with an + unknown hostname, or no <code>Host:</code> header, will be served from + <code>www.example1.com</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="intraextra" id="intraextra">Serving the same content on + different IP addresses (such as an internal and external + address).</a></h2> + + <p>The server machine has two IP addresses (<code>192.168.1.1</code> + and <code>172.20.30.40</code>). The machine is sitting between an + internal (intranet) network and an external (internet) network. Outside + of the network, the name <code>server.example.com</code> resolves to + the external address (<code>172.20.30.40</code>), but inside the + network, that same name resolves to the internal address + (<code>192.168.1.1</code>).</p> + + <p>The server can be made to respond to internal and external requests + with the same content, with just one <code>VirtualHost</code> + section.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + NameVirtualHost 192.168.1.1<br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 192.168.1.1 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/server1<br /> + ServerName server.example.com<br /> + ServerAlias server<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Now requests from both networks will be served from the same + <code>VirtualHost</code>.</p> + + <div class="note"> + <h3>Note:</h3><p>On the internal + network, one can just use the name <code>server</code> rather + than the fully qualified host name + <code>server.example.com</code>.</p> + + <p>Note also that, in the above example, you can replace the list + of IP addresses with <code>*</code>, which will cause the server to + respond the same on all addresses.</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="port" id="port">Running different sites on different + ports.</a></h2> + + <p>You have multiple domains going to the same IP and also want to + serve multiple ports. By defining the ports in the "NameVirtualHost" + tag, you can allow this to work. If you try using <VirtualHost + name:port> without the NameVirtualHost name:port or you try to use + the Listen directive, your configuration will not work.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + Listen 80<br /> + Listen 8080<br /> + <br /> + NameVirtualHost 172.20.30.40:80<br /> + NameVirtualHost 172.20.30.40:8080<br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + ServerName www.example1.com<br /> + DocumentRoot /www/domain-80<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + ServerName www.example1.com<br /> + DocumentRoot /www/domain-8080<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + ServerName www.example2.org<br /> + DocumentRoot /www/otherdomain-80<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + ServerName www.example2.org<br /> + DocumentRoot /www/otherdomain-8080<br /> + </span> + </VirtualHost> + </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="ip" id="ip">IP-based virtual hosting</a></h2> + + <p>The server has two IP addresses (<code>172.20.30.40</code> and + <code>172.20.30.50</code>) which resolve to the names + <code>www.example1.com</code> and <code>www.example2.org</code> + respectively.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + Listen 80<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Requests for any address not specified in one of the + <code><VirtualHost></code> directives (such as + <code>localhost</code>, for example) will go to the main server, if + there is one.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="ipport" id="ipport">Mixed port-based and ip-based virtual + hosts</a></h2> + + <p>The server machine has two IP addresses (<code>172.20.30.40</code> and + <code>172.20.30.50</code>) which resolve to the names + <code>www.example1.com</code> and <code>www.example2.org</code> + respectively. In each case, we want to run hosts on ports 80 and + 8080.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + Listen 172.20.30.40:80<br /> + Listen 172.20.30.40:8080<br /> + Listen 172.20.30.50:80<br /> + Listen 172.20.30.50:8080<br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + DocumentRoot /www/example1-80<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + DocumentRoot /www/example1-8080<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50:80><br /> + <span class="indent"> + DocumentRoot /www/example2-80<br /> + ServerName www.example1.org<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50:8080><br /> + <span class="indent"> + DocumentRoot /www/example2-8080<br /> + ServerName www.example2.org<br /> + </span> + </VirtualHost> + </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="mixed" id="mixed">Mixed name-based and IP-based + vhosts</a></h2> + + <p>On some of my addresses, I want to do name-based virtual hosts, and + on others, IP-based hosts.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + Listen 80<br /> + <br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example3<br /> + ServerName www.example3.net<br /> + </span> + </VirtualHost><br /> + <br /> + # IP-based<br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example4<br /> + ServerName www.example4.edu<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.60><br /> + <span class="indent"> + DocumentRoot /www/example5<br /> + ServerName www.example5.gov<br /> + </span> + </VirtualHost> + </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">Using <code>Virtual_host</code> and + mod_proxy together</a></h2> + + <p>The following example allows a front-end machine to proxy a + virtual host through to a server running on another machine. In the + example, a virtual host of the same name is configured on a machine + at <code>192.168.111.2</code>. The <code class="directive"><a href="../mod/mod_proxy.html#proxypreservehost on">ProxyPreserveHost On</a></code> directive is + used so that the desired hostname is passed through, in case we are + proxying multiple hostnames to a single machine.</p> + + <div class="example"><p><code> + <VirtualHost *:*><br /> + ProxyPreserveHost On<br /> + ProxyPass / http://192.168.111.2/<br /> + ProxyPassReverse / http://192.168.111.2/<br /> + ServerName hostname.example.com<br /> + </VirtualHost> + </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="default" id="default">Using <code>_default_</code> + vhosts</a></h2> + + <h3><a name="defaultallports" id="defaultallports"><code>_default_</code> vhosts + for all ports</a></h3> + + <p>Catching <em>every</em> request to any unspecified IP address and + port, <em>i.e.</em>, an address/port combination that is not used for + any other virtual host.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + <VirtualHost _default_:*><br /> + <span class="indent"> + DocumentRoot /www/default<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Using such a default vhost with a wildcard port effectively prevents + any request going to the main server.</p> + + <p>A default vhost never serves a request that was sent to an + address/port that is used for name-based vhosts. If the request + contained an unknown or no <code>Host:</code> header it is always + served from the primary name-based vhost (the vhost for that + address/port appearing first in the configuration file).</p> + + <p>You can use <code class="directive"><a href="../mod/mod_alias.html#aliasmatch">AliasMatch</a></code> or + <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> to rewrite any + request to a single information page (or script).</p> + + + <h3><a name="defaultdifferentports" id="defaultdifferentports"><code>_default_</code> vhosts + for different ports</a></h3> + + <p>Same as setup 1, but the server listens on several ports and we want + to use a second <code>_default_</code> vhost for port 80.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + <VirtualHost _default_:80><br /> + <span class="indent"> + DocumentRoot /www/default80<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost _default_:*><br /> + <span class="indent"> + DocumentRoot /www/default<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>The default vhost for port 80 (which <em>must</em> appear before any + default vhost with a wildcard port) catches all requests that were sent + to an unspecified IP address. The main server is never used to serve a + request.</p> + + + <h3><a name="defaultoneport" id="defaultoneport"><code>_default_</code> vhosts + for one port</a></h3> + + <p>We want to have a default vhost for port 80, but no other default + vhosts.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + <VirtualHost _default_:80><br /> + DocumentRoot /www/default<br /> + ...<br /> + </VirtualHost> + </code></p></div> + + <p>A request to an unspecified address on port 80 is served from the + default vhost any other request to an unspecified address and port is + served from the main server.</p> + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="migrate" id="migrate">Migrating a name-based vhost to an + IP-based vhost</a></h2> + + <p>The name-based vhost with the hostname + <code>www.example2.org</code> (from our <a href="#name">name-based</a> example, setup 2) should get its own IP + address. To avoid problems with name servers or proxies who cached the + old IP address for the name-based vhost we want to provide both + variants during a migration phase.<br /> + The solution is easy, because we can simply add the new IP address + (<code>172.20.30.50</code>) to the <code>VirtualHost</code> + directive.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + Listen 80<br /> + ServerName www.example1.com<br /> + DocumentRoot /www/example1<br /> + <br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example3<br /> + ServerName www.example3.net<br /> + ServerAlias *.example3.net<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>The vhost can now be accessed through the new address (as an + IP-based vhost) and through the old address (as a name-based + vhost).</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="serverpath" id="serverpath">Using the <code>ServerPath</code> + directive</a></h2> + + <p>We have a server with two name-based vhosts. In order to match the + correct virtual host a client must send the correct <code>Host:</code> + header. Old HTTP/1.0 clients do not send such a header and Apache has + no clue what vhost the client tried to reach (and serves the request + from the primary vhost). To provide as much backward compatibility as + possible we create a primary vhost which returns a single page + containing links with an URL prefix to the name-based virtual + hosts.</p> + + <div class="example"><h3>Server configuration</h3><p><code> + + + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + # primary vhost<br /> + DocumentRoot /www/subdomain<br /> + RewriteEngine On<br /> + RewriteRule ^/.* /www/subdomain/index.html<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + DocumentRoot /www/subdomain/sub1<br /> + <span class="indent"> + ServerName www.sub1.domain.tld<br /> + ServerPath /sub1/<br /> + RewriteEngine On<br /> + RewriteRule ^(/sub1/.*) /www/subdomain$1<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/subdomain/sub2<br /> + ServerName www.sub2.domain.tld<br /> + ServerPath /sub2/<br /> + RewriteEngine On<br /> + RewriteRule ^(/sub2/.*) /www/subdomain$1<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Due to the <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> + directive a request to the URL + <code>http://www.sub1.domain.tld/sub1/</code> is <em>always</em> served + from the sub1-vhost.<br /> A request to the URL + <code>http://www.sub1.domain.tld/</code> is only + served from the sub1-vhost if the client sent a correct + <code>Host:</code> header. If no <code>Host:</code> header is sent the + client gets the information page from the primary host.<br /> + Please note that there is one oddity: A request to + <code>http://www.sub2.domain.tld/sub1/</code> is also served from the + sub1-vhost if the client sent no <code>Host:</code> header.<br /> + The <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives + are used to make sure that a client which sent a correct + <code>Host:</code> header can use both URL variants, <em>i.e.</em>, + with or without URL prefix.</p> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/examples.html" title="English"> en </a> | +<a href="../ko/vhosts/examples.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/examples.html" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/examples.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/examples.html.ko.euc-kr new file mode 100644 index 00000000..553a9d4a --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/examples.html.ko.euc-kr @@ -0,0 +1,622 @@ +<?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="./">ȣƮ</a></div><div id="page-content"><div id="preamble"><h1>ȣƮ </h1> +<div class="toplang"> +<p><span> : </span><a href="../en/vhosts/examples.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/examples.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/examples.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate"> ֽ ƴմϴ. + ֱٿ ϼ.</div> + + + <p> ǵǴ ȣƮ + Ϸ . Ȳ <a href="name-based.html"≯</a>̳ <a href="ip-based.html">IP</a> ȣƮ + Ʈ Ϸ ̴. Ͻ ڿ + Ͽ Ʈ ϴ 츦 ٷ + ̴.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#purename">IP ּ Ѱ ̸ + Ʈ ϱ.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#twoips"> IP ּҿ ̸ + ȣƮ.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#intraextra">(ο ܺ ּҿ ) + ٸ IP ּҷ ϱ.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#port"> Ʈ ٸ Ʈ + ϱ.</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ip">IP ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ipport">Ʈݰ ip ȥյ + ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#mixed"≯ݰ IP ȥյ + ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#default"><code>_default_</code> ȣƮ + ϱ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#migrate"≯ ȣƮ IP + ȣƮ ű</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#serverpath"><code>ServerPath</code> + þ ϱ</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="purename" id="purename">IP ּ Ѱ ̸ + Ʈ ϱ.</a></h2> + + <p> IP ּҰ Ѱ ְ, DNS ּ(CNAMES) + ǻ Ų. ǻͿ <code>www.example1.com</code> + <code>www.example2.org</code> ϰ ʹ.</p> + + <div class="note"><h3>Note</h3><p>ġ ȣƮ + Ѵٰ ȣƮ DNS ڵ̷ + ʴ´. <em>ݵ</em> DNS IP ּҸ Ű + ̸ ־ Ѵ. ȱ ƹ Ʈ + . ˻غ <code>hosts</code> Ͽ + ߰ , ̴ hosts ǻͿ + ݿȴ.</p> + </div> + + <div class="example"><h3> </h3><p><code> + + + # ġ Ʈ 80 ٸ<br /> + Listen 80<br /> + <br /> + # IP ּҿ ȣƮ û ٸ<br /> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + <br /> + # ٸ þ鵵 ִ<br /> + <br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + <br /> + # ٸ þ鵵 ִ<br /> + <br /> + </span> + </VirtualHost> + </code></p></div> + + <p>ǥ ּҸ ŰǷ, ּ û + ʴ´. <code>www.example1.com</code> + Ͽ ó Ƿ 켱 , + <cite>⺻</cite>Ȥ <cite>ʱ</cite> ȴ. + <code>ServerName</code> þ شʴ û + ù° <code>VirtualHost</code> Ѵ.</p> + + <div class="note"> + <h3></h3> + + <p>Ѵٸ <code>*</code> ý IP + ּҸ ִ. + <code>VirtualHost</code> ƱԸƮ + <code>NameVirtualHost</code> ƱԸƮ ġؾ + <em>Ѵ</em>:</p> + + <div class="example"><p><code> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + # ... + </code></p></div> + + <p> ISP IP ּҸ + IP ּҸ 쿡 <code>*</code> ϴ + ϴ. <code>*</code> IP ּҿ + شϹǷ, IP ּҰ Ǿ + ʿ䰡 .</p> + </div> + + <p> κ ̸ ȣƮ . + ܴ ٸ IP ּҳ Ʈ ٸ Ϸ + ̴.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="twoips" id="twoips"> IP ּҿ ̸ + ȣƮ.</a></h2> + + <div class="note"> + <h3></h3><p>⼭ IP ּҰ + 밡ϴ.</p> + </div> + + <p> IP ּҰ ΰִ. ϳ + (<code>172.20.30.40</code>) "" + <code>server.domain.com</code> ϰ, ٸ ϳ + (<code>172.20.30.50</code>) ȣƮ + ̴.</p> + + <div class="example"><h3> </h3><p><code> + + + Listen 80<br /> + <br /> + # 172.20.30.40 ϴ ""̴<br /> + ServerName server.domain.com<br /> + DocumentRoot /www/mainserver<br /> + <br /> + # ٸ ּҴ<br /> + NameVirtualHost 172.20.30.50<br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + <br /> + # ٸ þ鵵 ִ ...<br /> + <br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + <br /> + # ٸ þ鵵 ִ ...<br /> + <br /> + </span> + </VirtualHost> + </code></p></div> + + <p><code>172.20.30.50</code> ƴ ּҿ û + ּ Ѵ. ȣƮ , <code>Host:</code> + <code>172.20.30.50</code> ûϸ + <code>www.example1.com</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="intraextra" id="intraextra">(ο ܺ ּҿ ) + ٸ IP ּҷ ϱ.</a></h2> + + <p> ǻͿ IP ּҰ ΰ (<code>192.168.1.1</code> + <code>172.20.30.40</code>) ִ. ǻʹ (Ʈ) + Ʈ ܺ (ͳ) Ʈ ̿ ġѴ. Ʈ ۿ + <code>server.example.com</code> ܺ ּҸ + (<code>172.20.30.40</code>) ǹϰ, Ʈ ο + ̸ ּҷ (<code>192.168.1.1</code>) Ѵ.</p> + + <p> <code>VirtualHost</code> Ѱ ο ܺ + 信 ִ.</p> + + <div class="example"><h3> </h3><p><code> + + + NameVirtualHost 192.168.1.1<br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 192.168.1.1 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/server1<br /> + ServerName server.example.com<br /> + ServerAlias server<br /> + </span> + </VirtualHost> + </code></p></div> + + <p> Ʈ û + <code>VirtualHost</code> Ѵ.</p> + + <div class="note"> + <h3>:</h3><p> Ʈ ȣƮ + <code>server.example.com</code> ̸ + <code>server</code> ϴ.</p> + + <p> IP ּ <code>*</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="port" id="port"> Ʈ ٸ Ʈ + ϱ.</a></h2> + + <p> IP Ʈ ٸ Ѵٰ + . ̴ "NameVirtualHost" ± Ʈ ϸ + ϴ. NameVirtualHost name:port <VirtualHost + name:port> Ȥ Listen þ ϸ ȵȴ.</p> + + <div class="example"><h3> </h3><p><code> + + + Listen 80<br /> + Listen 8080<br /> + <br /> + NameVirtualHost 172.20.30.40:80<br /> + NameVirtualHost 172.20.30.40:8080<br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + ServerName www.example1.com<br /> + DocumentRoot /www/domain-80<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + ServerName www.example1.com<br /> + DocumentRoot /www/domain-8080<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + ServerName www.example2.org<br /> + DocumentRoot /www/otherdomain-80<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + ServerName www.example2.org<br /> + DocumentRoot /www/otherdomain-8080<br /> + </span> + </VirtualHost> + </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="ip" id="ip">IP ȣƮ</a></h2> + + <p> <code>www.example1.com</code> + <code>www.example2.org</code> شϴ IP ּҸ + (<code>172.20.30.40</code> <code>172.20.30.50</code>) + .</p> + + <div class="example"><h3> </h3><p><code> + + + Listen 80<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + </span> + </VirtualHost> + </code></p></div> + + <p><code><VirtualHost></code> þ ּҿ + شʴ ּҷ ( , <code>localhost</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="ipport" id="ipport">Ʈݰ ip ȥյ + ȣƮ</a></h2> + + <p> <code>www.example1.com</code> + <code>www.example2.org</code> شϴ IP ּҸ + (<code>172.20.30.40</code> <code>172.20.30.50</code>) + . IP 80 8080 Ʈ ȣƮ .</p> + + <div class="example"><h3> </h3><p><code> + + + Listen 172.20.30.40:80<br /> + Listen 172.20.30.40:8080<br /> + Listen 172.20.30.50:80<br /> + Listen 172.20.30.50:8080<br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + DocumentRoot /www/example1-80<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + DocumentRoot /www/example1-8080<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50:80><br /> + <span class="indent"> + DocumentRoot /www/example2-80<br /> + ServerName www.example1.org<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50:8080><br /> + <span class="indent"> + DocumentRoot /www/example2-8080<br /> + ServerName www.example2.org<br /> + </span> + </VirtualHost> + </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="mixed" id="mixed"≯ݰ IP ȥյ + ȣƮ</a></h2> + + <p>ּ ̸ ȣƮ, ٸ IP + ȣƮ ϰ ʹ.</p> + + <div class="example"><h3> </h3><p><code> + + + Listen 80<br /> + <br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example1<br /> + ServerName www.example1.com<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example3<br /> + ServerName www.example3.net<br /> + </span> + </VirtualHost><br /> + <br /> + # IP-<br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example4<br /> + ServerName www.example4.edu<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.60><br /> + <span class="indent"> + DocumentRoot /www/example5<br /> + ServerName www.example5.gov<br /> + </span> + </VirtualHost> + </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="default" id="default"><code>_default_</code> ȣƮ + ϱ</a></h2> + + <h3><a name="defaultallports" id="defaultallports"> Ʈ + <code>_default_</code> ȣƮ</a></h3> + + <p> ȣƮ ش IP ּҿ Ʈ + <em></em> û óϱ.</p> + + <div class="example"><h3> </h3><p><code> + + + <VirtualHost _default_:*><br /> + <span class="indent"> + DocumentRoot /www/default<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>default(⺻) ȣƮ Ʈ ϵī带 Ͽ û + ּ .</p> + + <p>default ȣƮ ̸ ȣƮ ϴ + ּ/Ʈ û ʴ´. ų + <code>Host:</code> û ̸ + ȣƮ(Ͽ + ּ/Ʈ ó ȣƮ) Ѵ.</p> + + <p><code class="directive"><a href="../mod/mod_alias.html#aliasmatch">AliasMatch</a></code> + <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> + Ͽ û Ư (Ȥ ũƮ) + ۼ(rewrite) ִ.</p> + + + <h3><a name="defaultdifferentports" id="defaultdifferentports"> Ʈ + <code>_default_</code> ȣƮ</a></h3> + + <p> , Ʈ ٸ 80 + Ʈ ؼ ߰ <code>_default_</code> ȣƮ + ϰ ʹ.</p> + + <div class="example"><h3> </h3><p><code> + + + <VirtualHost _default_:80><br /> + <span class="indent"> + DocumentRoot /www/default80<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost _default_:*><br /> + <span class="indent"> + DocumentRoot /www/default<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>80 Ʈ default ȣƮ (<em>ݵ</em> + ϵī Ʈ ⺻ ȣƮ ; Ѵ) + IP ּҷ û Ѵ. + ּ û Ѵ.</p> + + + <h3><a name="defaultoneport" id="defaultoneport"> Ʈ + <code>_default_</code> ȣƮ</a></h3> + + <p>80 Ʈ ؼ default ȣƮ ʹ.</p> + + <div class="example"><h3> </h3><p><code> + + + <VirtualHost _default_:80><br /> + DocumentRoot /www/default<br /> + ...<br /> + </VirtualHost> + </code></p></div> + + <p>Ʈ 80 ּҿ û ⺻ + ȣƮ ϰ, ٸ ּҿ Ʈ + û Ѵ.</p> + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="migrate" id="migrate"≯ ȣƮ IP + ȣƮ ű</a></h2> + + <p>(<a href="#name"≯</a> ù° ) ȣƮ + <code>www.example2.org</code> ̸ ȣƮ + ڽ IP ּҸ Ѵ. ̸ ȣƮ + IP ּҸ ijϴ Ӽ Ͻÿ ϱ + ű θ ϰ ʹ.<br /> + <code>VirtualHost</code> þ IP ּҸ + (<code>172.20.30.50</code>) ߰ϸǹǷ .</p> + + <div class="example"><h3> </h3><p><code> + + + Listen 80<br /> + ServerName www.example1.com<br /> + DocumentRoot /www/example1<br /> + <br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /www/example2<br /> + ServerName www.example2.org<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/example3<br /> + ServerName www.example3.net<br /> + ServerAlias *.example3.net<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p> (IP ȣƮ ) ο ּҿ (̸ + ȣƮ ) ּ ȣƮ + ִ.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="serverpath" id="serverpath"><code>ServerPath</code> + þ ϱ</a></h2> + + <p> ̸ ȣƮ ִ. ùٸ + ȣƮ ϱ Ŭ̾Ʈ ùٸ + <code>Host:</code> Ѵ. HTTP/1.0 + Ŭ̾Ʈ ϸ ġ Ŭ̾Ʈ + ȣƮ ϴ ( + ȣƮ û Ѵ). ȣȯ + ϱ ȣƮ , ̸ + ȣƮ URL λ縦 ϴ ũ + д.</p> + + <div class="example"><h3> </h3><p><code> + + + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + # primary vhost<br /> + DocumentRoot /www/subdomain<br /> + RewriteEngine On<br /> + RewriteRule ^/.* /www/subdomain/index.html<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + DocumentRoot /www/subdomain/sub1<br /> + <span class="indent"> + ServerName www.sub1.domain.tld<br /> + ServerPath /sub1/<br /> + RewriteEngine On<br /> + RewriteRule ^(/sub1/.*) /www/subdomain$1<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /www/subdomain/sub2<br /> + ServerName www.sub2.domain.tld<br /> + ServerPath /sub2/<br /> + RewriteEngine On<br /> + RewriteRule ^(/sub2/.*) /www/subdomain$1<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> þ + URL <code>http://www.sub1.domain.tld/sub1/</code> + û <em></em> subl-ȣƮ Ѵ.<br /> + Ŭ̾Ʈ ùٸ <code>Host:</code> ٸ, + URL <code>http://www.sub1.domain.tld/</code> û + subl-ȣƮ Ѵ. <code>Host:</code> + Ŭ̾Ʈ ȣƮ ִ + Եȴ.<br /> ϶: Ŭ̾Ʈ + <code>Host:</code> + <code>http://www.sub2.domain.tld/sub1/</code> û + subl-ȣƮ Ѵ.<br /> + <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> + þ Ͽ ùٸ <code>Host:</code> + Ŭ̾Ʈ (<em> </em>, URL ġ簡 ְų ) + URL ִ.</p> + + </div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../en/vhosts/examples.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/examples.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/examples.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/apache2/manual/vhosts/examples.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/examples.html.tr.utf8 new file mode 100644 index 00000000..044bf8e6 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/examples.html.tr.utf8 @@ -0,0 +1,641 @@ +<?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>Sanal Konak Örnekleri - 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="./">Sanal Konaklar</a></div><div id="page-content"><div id="preamble"><h1>Sanal Konak Örnekleri</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/examples.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/examples.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/examples.html" title="Türkçe"> tr </a></p> +</div> + + + <p>Bu belgede sanal konaklarla ile ilgili olarak karşılaşılması olası tüm + senaryolara yer verilmeye çalışılmıştır. Buradaki senaryolar, tek bir + sunucu üzerinde <a href="name-based.html">isme dayalı</a> veya <a href="ip-based.html">IP’ye dayalı</a> sanal konaklar aracılığıyla çok + sayıda sitenin sunumu ile ilgilidir. + </p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#purename">Tek bir IP ile çok sayıda isme dayalı site</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#twoips">IP adresleri farklı çok sayıda isme dayalı site</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#intraextra">Aynı içeriği farklı IP adresleriyle sunmak + (örn., dahili ve harici ağlara)</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#port">Farklı portlarla farklı siteler</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ip">IP’ye dayalı sanal konaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ipport">Hem IP’ye hem de porta dayalı sanal konaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#mixed">Hem isme hem de IP‘ye dayalı sanal konaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#proxy"><code>Virtualhost</code> ve + <code>mod_proxy</code>’nin birlikte kullanımı</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#default"><code>_default_</code> sanal konakları</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#migrate">Bir isme dayalı sanal konağı bir IP’ye dayalı + sanal konakla yansılamak</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#serverpath"><code>ServerPath</code> yönergesinin kullanımı</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="purename" id="purename">Tek bir IP ile çok sayıda isme dayalı site</a></h2> + + + <p>Bu örnekte, makinenizin tek bir IP adresine sahip olduğunu ve bu + makineye <code>mesela.dom</code> ve <code>faraza.dom</code> şeklinde + (DNS A kayıtları sayesinde) farklı isimlerle erişilebildiğini + varsayalım.</p> + + <div class="note"><h3>Bilginize</h3><p>Apache sunucusu üzerinde sanal konakları + yapılandırmakla bu konak isimleri için sihirli bir şekilde DNS + kayıtlarının da oluşturulmasını sağlamış olmazsınız. Bu isimler için + ilgili DNS kayıtlarında sizin IP adresinize çözümlenen A kayıtlarının + olması gerekir, yoksa sitenize kimse erişemez. Sitelere erişimi yerel + olarak denemek isterseniz, bu girdileri <code>hosts</code> dosyanıza + yazabilirsiniz. Fakat bu sadece sizin makinenizde çalışır. Yerel + ağınızdaki her makinenin <code>hosts</code> dosyasına bu girdileri + yazarak yerel ağdan erişimi bu yolla sağlayabilirsiniz ama dış ağdan + gelecek ziyaretçileriniz için DNS kayıtlarınızın olması şarttır.</p> + </div> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + # Apache’nin 80. portu dinlediğinden emin olalım<br /> + Listen 80<br /> + <br /> + # Sanal konak istekleri için bütün IP adresleri dinlensin.<br /> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + DocumentRoot /siteler/mesela<br /> + ServerName mesela.dom<br /> + <br /> + # Diğer yönergeler, burada ...<br /> + <br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + DocumentRoot /siteler/faraza<br /> + ServerName faraza.dom<br /> + <br /> + # Diğer yönergeler, burada ...<br /> + <br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Yıldız imleri tüm adreslerle eşleşmeyi sağladığından ana sunucu + (yapılandırma dosyası genelindeki yapılandırma - sunucu geneli) + erişilebilir olmayacaktır. <code>mesela.dom</code> yapılandırma + dosyasındaki ilk sanal konak olduğundan en yüksek önceliğe sahiptir ve + <cite>öntanımlı</cite> veya <cite>baskın</cite> site olarak davranır. + Yani, hiçbir <code>ServerName</code> yönergesi ile eşleşmeyen bir istek + alındığında bu istek ilk <code>VirtualHost</code> yapılandırması ile + karşılanır.</p> + + <div class="note"><h3>Bilginize</h3> + <p>İsterseniz, <code>*</code> yerine kendi IP adresinizi yazabilirsiniz. + Ancak bu durumda bunu hem <code>VirtualHost</code> hem de + <code>NameVirtualHost</code> için yapmalısınız:</p> + + <div class="example"><p><code> + NameVirtualHost 192.168.1.22<br /> + <br /> + <VirtualHost 192.168.1.22><br /> + # vs. ... + </code></p></div> + + <p>Bununla birlikte, IP adresinin önceden kestirilebilir olmadığı + sistemlerde, örneğin, hizmet sağlayıcınıza çevirmeli ağ ile bağlanıyor + ve onun rasgele atadığı bir IP adresi için bir devingen DNS çözümü + kullanıyorsanız, IP adresi değil de <code>*</code> kullanmak daha çok + işinize yarayacaktır. Yıldız imi her IP adresi ile eşleşeceğinden IP + adresiniz değişse bile bu yapılandırmayı değiştirmeden + kullanabilirsiniz.</p> + </div> + + <p>Yukarıdaki yapılandırmayı hemen hemen tüm isme dayalı sanal konaklar + için kullanabilirsiniz. Bu yapılandırmanın çalışmayacağı tek durum, + farklı içerikleri farklı IP adreslerinden sunma gereğiyle + karşılaşmaktı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="twoips" id="twoips">IP adresleri farklı çok sayıda isme dayalı site</a></h2> + + + <div class="note"><h3>Bilginize</h3> + <p>Burada açıklanan teknikler istendiği kadar çok IP adresine + genişletilebilir.</p> + </div> + + <p>Sunucunun iki IP adresi olsun. Birinden "ana sunucu" + (<code>192.168.1.2</code>) diğerinden <code>mesela.dom</code> + <code>192.168.2.2</code> hizmet versin. Bu arada başka sanal konakları + da sunabilelim istiyoruz.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + Listen 80<br /> + <br /> + # Bu, 192.168.1.2 adresindeki "ana sunucu" olsun<br /> + ServerName sunucu.faraza.dom<br /> + DocumentRoot /siteler/anasunucu<br /> + <br /> + # Burası da diğer adres için<br /> + NameVirtualHost 192.168.2.2<br /> + <br /> + <VirtualHost 192.168.2.2><br /> + <span class="indent"> + DocumentRoot /siteler/mesela<br /> + ServerName mesela.dom<br /> + <br /> + # Diğer yönergeler, burada ...<br /> + <br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 192.168.2.2><br /> + <span class="indent"> + DocumentRoot /siteler/falanca<br /> + ServerName falanca.dom<br /> + <br /> + # Diğer yönergeler, burada ...<br /> + <br /> + </span> + </VirtualHost> + </code></p></div> + + <p><code>192.168.2.2</code> adresinden gelmeyen tüm isteklere ana sunucu + (<code>sunucu.faraza.dom</code>), <code>192.168.2.2</code> adresinden + gelen sunucu ismi belirtmeyenler ile <code>Host:</code> başlığı + belirtmeyenlere ise <code>mesela.dom</code> hizmet verecektir.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="intraextra" id="intraextra">Aynı içeriği farklı IP adresleriyle sunmak + (örn., dahili ve harici ağlara)</a></h2> + + <p>Sunucu makine iki IP adresine sahip olsun. Biri iç ağa + (<code>192.168.1.1</code>) diğeri dış ağa (<code>172.20.30.40</code>) + bakıyor olsun. <code>sunucu.mesela.dom</code> ismi dış ağda dış ağa + bakan IP’ye, iç ağda ise iç ağa bakan IP’ye çözümleniyor olsun.</p> + + <p>Bu durumda, sunucu hem iç hem de dış ağdan gelen isteklere aynı içerik, + dolayısıyla aynı <code>VirtualHost</code> bölümü ile hizmet + verebilir.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + NameVirtualHost 192.168.1.1<br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 192.168.1.1 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /siteler/sunucu<br /> + ServerName sunucu.mesela.dom<br /> + ServerAlias sunucu<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Artık, hem iç hem de dış ağdan gelen isteklere aynı + <code>VirtualHost</code> bölümünden hizmet sunulacaktır.</p> + + <div class="note"><h3>Bilginize:</h3> + <p>İç ağdan istek yapan biri, tam nitelenmiş konak ismi + <code>sunucu.mesela.dom</code> yerine makine ismini + (<code>sunucu</code>) kullanabilir (<code>ServerAlias sunucu</code> + satırına dikkat).</p> + + <p>Ayrıca, yukarıdaki gibi iki ayrı IP adresi belirtmek yerine sadece + <code>*</code> belirtmekle sunucunun tüm IP adreslerine yine aynı + içerikle yanıt vereceğine dikkat ediniz.</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="port" id="port">Farklı portlarla farklı siteler</a></h2> + + <p>Aynı IP adresine sahip çok sayıda konak ismine sahip olduğunuzu ve + bunların bazılarının farklı portları kullanmasını istediğinizi + varsayalım. <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + yönergesi ile port tanımlamak suretiyle bunu mümkün kılabilirsiniz. + <code>NameVirtualHost <em>isim:port</em></code> tanımı yapmadan + veya bunun yerine <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + kullanarak <code>VirtualHost <em>isim:port</em></code> kullanmaya + kalkışırsanız, yapılandırmanız çalışmayacaktır.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + Listen 80<br /> + Listen 8080<br /> + <br /> + NameVirtualHost 172.20.30.40:80<br /> + NameVirtualHost 172.20.30.40:8080<br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + ServerName mesela.dom<br /> + DocumentRoot /siteler/mesela-80<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + ServerName mesela.dom<br /> + DocumentRoot /siteler/mesela-8080<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + ServerName faraza.dom<br /> + DocumentRoot /siteler/faraza-80<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + ServerName faraza.dom<br /> + DocumentRoot /siteler/faraza-8080<br /> + </span> + </VirtualHost> + </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="ip" id="ip">IP’ye dayalı sanal konaklar</a></h2> + + <p>Sunucu makinenin, biri <code>mesela.dom</code> adından çözümlenen + <code>172.20.30.40</code>, diğeri <code>faraza.dom</code> adından + çözümlenen <code>172.20.30.50</code> diye iki IP adresi olsun.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + Listen 80<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /siteler/mesela<br /> + ServerName mesela.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /siteler/faraza<br /> + ServerName faraza.dom<br /> + </span> + </VirtualHost> + </code></p></div> + + <p><code><VirtualHost></code> yönergelerinde belirtilmeyen + adreslerle yapılan isteklere (örneğin, <code>localhost</code>) sunucu + genelindeki yapılandırma ile ana sunucu yanıt verecektir.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="ipport" id="ipport">Hem IP’ye hem de porta dayalı sanal konaklar</a></h2> + + + <p>Sunucu makinenin, biri <code>mesela.dom</code> adından çözümlenen + <code>172.20.30.40</code>, diğeri <code>faraza.dom</code> adından + çözümlenen <code>172.20.30.50</code> diye iki IP adresi olsun ve iki + konak da hem 80 hem de 8080 portlarında çalışsınlar istiyoruz.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + Listen 172.20.30.40:80<br /> + Listen 172.20.30.40:8080<br /> + Listen 172.20.30.50:80<br /> + Listen 172.20.30.50:8080<br /> + <br /> + <VirtualHost 172.20.30.40:80><br /> + <span class="indent"> + DocumentRoot /siteler/mesela-80<br /> + ServerName mesela.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40:8080><br /> + <span class="indent"> + DocumentRoot /siteler/mesela-8080<br /> + ServerName mesela.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50:80><br /> + <span class="indent"> + DocumentRoot /siteler/faraza-80<br /> + ServerName faraza.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.50:8080><br /> + <span class="indent"> + DocumentRoot /siteler/faraza-8080<br /> + ServerName faraza.dom<br /> + </span> + </VirtualHost> + </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="mixed" id="mixed">Hem isme hem de IP‘ye dayalı sanal konaklar</a></h2> + + + <p>Bazı adreslerde isme dayalı, bazılarında da IP’ye dayalı sanal konaklar + çalışsın istersek...</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + Listen 80<br /> + <br /> + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /siteler/mesela<br /> + ServerName mesela.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /siteler/faraza<br /> + ServerName faraza.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /siteler/falanca<br /> + ServerName falanca.dom<br /> + </span> + </VirtualHost><br /> + <br /> + # IP-based<br /> + <VirtualHost 172.20.30.50><br /> + <span class="indent"> + DocumentRoot /siteler/filanca<br /> + ServerName filanca.dom<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.60><br /> + <span class="indent"> + DocumentRoot /siteler/fesmekan<br /> + ServerName fesmekan.dom<br /> + </span> + </VirtualHost> + </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"><code>Virtualhost</code> ve + <code>mod_proxy</code>’nin birlikte kullanımı</a></h2> + + <p>Bu örnekte bir arabirimi dışarıya bakan bir makinede, başka bir + makinede çalışan bir sunucuya sanal konak olarak, bir vekil sunucu + çalıştırmak istediğimizi varsayıyoruz. <code>192.168.111.2</code> IP + adresli bir makinede aynı isimde bir sanal konak yapılandırılmış olsun. + Çok sayıda konak ismi için vekil olarak tek bir makine kullandığımızdan + ve konak isminin de aktarılmasını arzuladığımızdan <code class="directive"><a href="../mod/mod_proxy.html#proxypreservehost on">ProxyPreserveHost On</a></code> yönergesini + kullandık.</p> + + <div class="example"><p><code> + <VirtualHost *:*><br /> + <span class="indent"> + ProxyPreserveHost On<br /> + ProxyPass / http://192.168.111.2/<br /> + ProxyPassReverse / http://192.168.111.2/<br /> + ServerName konak.mesela.dom<br /> + </span> + </VirtualHost> + </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="default" id="default"><code>_default_</code> sanal konakları</a></h2> + + <h3><a name="defaultallports" id="defaultallports">Tüm portlar için <code>_default_</code></a></h3> + + + <p>Bir IP adresi ve port belirtilmeyen veya hiçbir sanal konağın hiçbir + adresi/portu ile eşleşmeyen istekleri yakalamak istersek...</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + + <VirtualHost _default_:*><br /> + <span class="indent"> + DocumentRoot /siteler/default<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Bütün portlarla eşleşen böyle bir öntanımlı sanal konağın kullanımı + hiçbir isteğin ana sunucuya gitmemesi sonucunu doğurur.</p> + + <p>Bir öntanımlı sanal konak, asla, isme dayalı sanal konaklar için + kullanılmış bir adrese/porta gönderilmiş bir isteğe hizmet sunmaz. Eğer + istek bilinmeyen bir <code>Host:</code> başlığına sahipse veya hiç + <code>Host:</code> başlığı içermiyorsa isteğe daima ilk (yapılandırma + dosyasındaki ilk) isme dayalı sanal konak hizmet sunar.</p> + + <p>Her isteği tek bir bilgilendirme sayfasına (veya betiğe) yönlendirmek + isterseniz <code class="directive"><a href="../mod/mod_alias.html#aliasmatch">AliasMatch</a></code> veya + <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> yönergesini + kullanabilirsiniz.</p> + + + <h3><a name="defaultdifferentports" id="defaultdifferentports">Farklı portlardan <code>_default_</code></a></h3> + + + <p>Önceki yapılandırmaya ek olarak 80. portta ayrı bir + <code>_default_</code> sanal konağı kullanmak istersek...</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + + <VirtualHost _default_:80><br /> + <span class="indent"> + DocumentRoot /siteler/default80<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost _default_:*><br /> + <span class="indent"> + DocumentRoot /siteler/default<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>80. porttan hizmet sunan <code>_default_</code> sanal konağı IP adresi + belirtilmeyen tüm istekleri yakalar, bunu yapabilmesi için yapılandırma + dosyasında tüm portlara hizmet sunan benzerinden önce yer almalıdır. Bu + durumda ana sunucu hiçbir isteğe yanıt vermeyecektir.</p> + + + <h3><a name="defaultoneport" id="defaultoneport">Tek portluk <code>_default_</code></a></h3> + + + <p><code>_default_</code> sanal konağının sadece 80. porttan hizmet + sunmasını istersek...</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + + <VirtualHost _default_:80><br /> + DocumentRoot /siteler/default<br /> + ...<br /> + </VirtualHost> + </code></p></div> + + <p>80. porttan gelen IP adresi belirtilmemiş isteklere + <code>_default_</code> sanal konağı, diğer portlardan gelen adres + belirtilmemiş isteklere ise ana sunucu hizmet verecektir.</p> + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="migrate" id="migrate">Bir isme dayalı sanal konağı bir IP’ye dayalı + sanal konakla yansılamak</a></h2> + + <p>İsme dayalı sanal konak örneklerinin <a href="#twoips">2. sinde</a> adı + geçen <code>falanca.dom</code> bu örnekte kendi IP adresinden hizmet + veriyor olsun. İsme dayalı sanal konağı eski IP adresiyle kaydetmiş + vekiller ve isim sunucularından kaynaklanacak olası sorunlardan kaçınmak + için yansılama sırasında sanal konağı hem eski hem de yeni IP adresiyle + sunmamız lazım.</p> + + <p>Çözüm kolay, çünkü yapacağımız sadece <code>VirtualHost</code> + yönergesine yeni IP adresini (<code>192.168.2.2</code>) eklemek olacak.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + + Listen 80<br /> + ServerName mesela.dom<br /> + DocumentRoot /siteler/mesela<br /> + <br /> + <VirtualHost 192.168.1.2><br /> + <br /> + <VirtualHost 192.168.1.2 192.168.2.2><br /> + <span class="indent"> + DocumentRoot /siteler/falanca<br /> + ServerName falanca.dom<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 192.168.1.2><br /> + <span class="indent"> + DocumentRoot /siteler/faraza<br /> + ServerName faraza.dom<br /> + ServerAlias *.faraza.dom<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p>Böylece sanal konağa hem yeni (bir IP’ye dayalı sanal konak olarak) + hem de eski adresinden (bir isme dayalı sanal konak olarak) + erişilebilecektir.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="serverpath" id="serverpath"><code>ServerPath</code> yönergesinin kullanımı</a></h2> + + + <p>İsme dayalı iki sanal konağı olan bir sunucumuz olsun. Doğru sanal + konağa erişebilmek için istemcinin doğru <code>Host:</code> başlığı + göndermesi gerekir. Eski HTTP/1.0 istemcileri böyle bir başlık + göndermedikleri için Apache istemcinin hangi sanal konağa erişmek + istediğini bilemez (ve isteğe ilk sanal konaktan hizmet sunar). Daha iyi + bir geriye uyumluluk sağlamak için isme dayalı sanal konağa bir önek + bağlantısı içeren bir bilgilendirme sayfası sunmak üzere yeni bir sanal + konak oluşturabiliriz.</p> + + <div class="example"><h3>Sunucu yapılandırması</h3><p><code> + + + NameVirtualHost 172.20.30.40<br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + # ilk sanal konak<br /> + DocumentRoot /siteler/baska<br /> + RewriteEngine On<br /> + RewriteRule ^/.* /siteler/baska/index.html<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + DocumentRoot /siteler/baska/bir<br /> + <span class="indent"> + ServerName bir.baska.tld<br /> + ServerPath /bir/<br /> + RewriteEngine On<br /> + RewriteRule ^(/bir/.*) /siteler/baska$1<br /> + # ...<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost 172.20.30.40><br /> + <span class="indent"> + DocumentRoot /siteler/baska/iki<br /> + ServerName iki.baska.tld<br /> + ServerPath /iki/<br /> + RewriteEngine On<br /> + RewriteRule ^(/iki/.*) /siteler/baska$1<br /> + # ...<br /> + </span> + </VirtualHost> + </code></p></div> + + <p><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> yönergesinden dolayı + <code>http://bir.baska.tld/bir/</code> şeklinde yapılan isteklere + <em>daima</em> “bir” sanal konağı hizmet sunacaktır.</p> + + <p><code>http://bir.baska.tld/</code> şeklinde yapılan isteklere ise + istemcinin doğru <code>Host:</code> başlığı göndermesi şartıyla + “bir” sanal konağı hizmet sunacaktır. İstemci, bir + <code>Host:</code> başlığı göndermediği takdirde ilk konaktan bir + bilgilendirme sayfası alacaktır.</p> + + <p>Yalnız buradaki bir tuhaflığa dikkat edin: Eğer istemci bir + <code>Host:</code> başlığı göndermeden + <code>http://iki.baska.tld/bir/</code> şeklinde bir istek yaparsa bu + isteğe de “bir” sanal konağı hizmet sunacaktır.</p> + + <p><code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> yönergesi, bir + istemcinin, bir URL öneki belirtsin ya da belirtmesin doğru + <code>Host:</code> başlığı gönderdiğinden emin olmak için + kullanılmıştır.</p> + + </div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/examples.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/examples.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/examples.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/apache2/manual/vhosts/fd-limits.html b/rubbos/app/apache2/manual/vhosts/fd-limits.html new file mode 100644 index 00000000..9dc971e1 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/fd-limits.html @@ -0,0 +1,17 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: fd-limits.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: fd-limits.html.ja.utf8 +Content-Language: ja +Content-type: text/html; charset=UTF-8 + +URI: fd-limits.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: fd-limits.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/fd-limits.html.en b/rubbos/app/apache2/manual/vhosts/fd-limits.html.en new file mode 100644 index 00000000..4649f65f --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/fd-limits.html.en @@ -0,0 +1,133 @@ +<?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>File Descriptor Limits - 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> > <a href="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>File Descriptor Limits</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/vhosts/fd-limits.html" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + + <p>When using a large number of Virtual Hosts, Apache may run + out of available file descriptors (sometimes called <cite>file + handles</cite>) if each Virtual Host specifies different log + files. The total number of file descriptors used by Apache is + one for each distinct error log file, one for every other log + file directive, plus 10-20 for internal use. Unix operating + systems limit the number of file descriptors that may be used + by a process; the limit is typically 64, and may usually be + increased up to a large hard-limit.</p> + + <p>Although Apache attempts to increase the limit as required, + this may not work if:</p> + + <ol> + <li>Your system does not provide the <code>setrlimit()</code> + system call.</li> + + <li>The <code>setrlimit(RLIMIT_NOFILE)</code> call does not + function on your system (such as Solaris 2.3)</li> + + <li>The number of file descriptors required exceeds the hard + limit.</li> + + <li>Your system imposes other limits on file descriptors, + such as a limit on stdio streams only using file descriptors + below 256. (Solaris 2)</li> + </ol> + + <p>In the event of problems you can:</p> + + <ul> + <li>Reduce the number of log files; don't specify log files + in the <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + sections, but only log to the main log files. (See <a href="#splitlogs">Splitting up your log files</a>, below, for more + information on doing this.)</li> + + <li> + If you system falls into 1 or 2 (above), then increase the + file descriptor limit before starting Apache, using a + script like + + <div class="example"><p><code> + <code>#!/bin/sh<br /> + ulimit -S -n 100<br /> + exec httpd</code> + </code></p></div> + </li> + </ul> + + <p>Please see the <a href="../misc/descriptors.html">Descriptors and Apache</a> + document containing further details about file descriptor + problems and how they can be solved on your operating + 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="splitlogs" id="splitlogs">Splitting up your log files</a></h2> + +<p>If you want to log multiple virtual hosts to the same log file, you +may want to split up the log files afterwards in order to run +statistical analysis of the various virtual hosts. This can be +accomplished in the following manner.</p> + +<p>First, you will need to add the virtual host information to the log +entries. This can be done using the <code class="directive"><a href="../mod/mod_log_config.html# logformat"> +LogFormat</a></code> +directive, and the <code>%v</code> variable. Add this to the beginning +of your log format string:</p> + +<div class="example"><p><code> +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost<br /> +CustomLog logs/multiple_vhost_log vhost +</code></p></div> + +<p>This will create a log file in the common log format, but with the +canonical virtual host (whatever appears in the +<code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> directive) prepended to +each line. (See <code class="directive"><a href="../mod/mod_log_config.html#custom log formats">Custom Log Formats</a></code> for +more about customizing your log files.)</p> + +<p>When you wish to split your log file into its component parts (one +file per virtual host) you can use the program <code><a href="../programs/other.html">split-logfile</a></code> to accomplish +this. You'll find this program in the <code>support</code> directory +of the Apache distribution.</p> + +<p>Run this program with the command:</p> + +<div class="example"><p><code> +split-logfile < /logs/multiple_vhost_log +</code></p></div> + +<p>This program, when run with the name of your vhost log file, will +generate one file for each virtual host that appears in your log file. +Each file will be called <code>hostname.log</code>.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/fd-limits.html" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.html" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/fd-limits.html.ja.utf8 b/rubbos/app/apache2/manual/vhosts/fd-limits.html.ja.utf8 new file mode 100644 index 00000000..91682507 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/fd-limits.html.ja.utf8 @@ -0,0 +1,131 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ja" xml:lang="ja"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>ファイル記述子の限界 - Apache HTTP サーバ</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/">モジュール</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 サーバ バージョン 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 サーバ</a> > <a href="http://httpd.apache.org/docs/">ドキュメンテーション</a> > <a href="../">バージョン 2.0</a> > <a href="./">バーチャルホスト</a></div><div id="page-content"><div id="preamble"><h1>ファイル記述子の限界</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/vhosts/fd-limits.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + + <p>たくさんのバーチャルホストを運用する場合、もし、 + 各バーチャルホストごとに異なるログファイルが指定してあると、 + Apache がファイル記述子 (<cite>ファイルハンドル</cite>とも呼ばれます) + を使い切ってしまうことがあります。Apache が使用するファイル + 記述子の数は、各エラーログファイルにつき 1 つ、他のログファイルの + ディレクティブにつき 1 つ、さらに内部で使用する 10 から 20、 + の合計になります。Unix オペレーティングシステムではプロセスごとに + 使用可能なファイル記述子の数を制限しています。たいていの場合は 64 で、 + 普通は大きな値のハードリミットまで増やすことができます。</p> + + <p>Apache は必要に応じて上限を拡大しようと試みますが、 + 以下のような場合にはうまくいかないかもしれません。</p> + + <ol> + <li>利用しているシステムで <code>setrlimit()</code> + システムコールが提供されていない。</li> + + <li>システム上で <code>setrlimit</code>(RLIMIT_NOFILE) が動作しない + (たとえば Solaris 2.3 のように)。</li> + + <li>要求されるファイル記述子の数が + ハードリミットを超えてしまう。</li> + + <li>システムにファイル記述子に関して別の制限が存在してしまっている。 + たとえば、stdio ストリームではファイル記述子を 256 以上使えない + (Solaris 2)、など。</li> + </ol> + + <p>問題が発生した時に取り得る対処方法は次のとおり:</p> + + <ul> + <li>ログファイルの数を減らす。<code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + セクションでログファイルを指定せず、メインのログファイルにのみ記録する。 + (これに関する詳しい情報は以下の<a href="#splitlogs">ログファイルの分割</a>を読んでください。)</li> + + <li> + もし、前述の 1 または 2 の場合であれば、 + Apache を起動する前にファイル記述子を増やします。 + たとえば次のようなスクリプトを使います。 + + <div class="example"><p><code> + <code>#!/bin/sh<br /> + ulimit -S -n 100<br /> + exec httpd</code> + </code></p></div> + </li> + </ul> + + <p>ファイル記述子の問題についての詳細や、 + オペレーティングシステムごとの解決方法については「<a href="../misc/descriptors.html">ファイル記述子と + Apache</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="splitlogs" id="splitlogs">ログファイルの分割</a></h2> + +<p>複数のバーチャルホストのログを同じログファイルに収集しようとしているときには、 +各バーチャルホストについて統計的な解析を実行するために後でログファイルを +分割したくなるかもしれません。これは以下のようにして実現できます。</p> + +<p>まず、バーチャルホストの情報をログのエントリに追加する必要があります。 +これは <code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> +ディレクティブの <code>%v</code> 変数を使うことでできます。 +これをログのフォーマット文字列の先頭に追加します:</p> + +<div class="example"><p><code> +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost<br /> +CustomLog logs/multiple_vhost_log vhost +</code></p></div> + +<p>これは common log format のログを作成しますが、それぞれの行の先頭に +正規化されたバーチャルホストの名前 +(<code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> +ディレクティブに書かれているもの) が付加されます。 +(ログファイルのカスタマイズの詳細については <a href="../mod/mod_log_config.html#formats">Custom Log Formats</a> を +読んでください。)</p> + +<p>ログファイルを各部分 (バーチャルホスト毎に 1 ファイル) に分けたいときは、 +<code><a href="../programs/other.html">split-logfile</a></code> +を使って行なうことができます。プログラムは Apache 配布の +<code>support</code> ディレクトリにあります。</p> + +<p>以下のようなコマンドでこのプログラムを実行します:</p> + +<div class="example"><p><code> +split-logfile < /logs/multiple_vhost_log +</code></p></div> + +<p>このプログラムはバーチャルホストのログファイルの名前とともに実行され、 +ログファイルに現れるそれぞれのバーチャルホスト毎に一つのファイルを作成します。 +それぞれのファイルは <code>ホスト名.log</code> という名前になります。</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/fd-limits.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.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/apache2/manual/vhosts/fd-limits.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/fd-limits.html.ko.euc-kr new file mode 100644 index 00000000..fc23ee20 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/fd-limits.html.ko.euc-kr @@ -0,0 +1,126 @@ +<?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>ϱ(file descriptor) Ѱ - 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/"></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="./">ȣƮ</a></div><div id="page-content"><div id="preamble"><h1>ϱ(file descriptor) Ѱ</h1> +<div class="toplang"> +<p><span> : </span><a href="../en/vhosts/fd-limits.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + + <p>ȣƮ ϰ ȣƮ ٸ + α ϸ, ġ 밡 ϱ(file + descriptor, <cite>ڵ(file handle)</cite>̶ + θ) ִ. ġ ϴ ϱ + αϴ Ѱ, ٸ α þ + Ѱ, ߰ ο뵵 10-20 . н ü + μ ִ ϱ Ѵ. Ѱ + 64, ̺ ū hard-limit ø ִ.</p> + + <p>ġ Ѱ踦 ʿѸŭ ø , ϴ + 찡 ִ:</p> + + <ol> + <li>ý <code>setrlimit()</code> ýȣ + ʴ´.</li> + + <li>(Solaris 2.3 ) ýۿ + <code>setrlimit(RLIMIT_NOFILE)</code> Լ + ʴ´.</li> + + <li>ʿ ϱ hard limit .</li> + + <li>(Solaris 2) ý stdio Ʈ 256 + ϱڸ ϵ ϴ ϱڿ + Ѵ.</li> + </ol> + + <p> ذå:</p> + + <ul> + <li>α δ. <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> ǿ α + ʰ α Ѵ. ( ڼ + Ʒ <a href="#splitlogs">α </a> ϶.)</li> + + <li> + ϴ ý () 1° 2° 쿡 شѴٸ, + ũƮ ġ ϱ ϱ + Ѱ踦 ø. + + <div class="example"><p><code> + <code>#!/bin/sh<br /> + ulimit -S -n 100<br /> + exec httpd</code> + </code></p></div> + </li> + </ul> + + <p>ϱ ü ذ + ڼ <a href="../misc/descriptors.html">ϱڿ + ġ</a> ϶.</p> + +</div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="splitlogs" id="splitlogs">α </a></h2> + +<p> ȣƮ α Ѵٸ ߿ +ȣƮ м α ̴. + ۾ ִ.</p> + +<p> α ȣƮ ߰Ѵ. ̸ +<code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> +þ <code>%v</code> Ѵ. α +Ĺڿ տ ߰Ѵ:</p> + +<div class="example"><p><code> +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost<br /> +CustomLog logs/multiple_vhost_log vhost +</code></p></div> + +<p> common α տ (<code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> þ ) +ȣƮ Ͽ α Ѵ. (α +ǿ <code class="directive"><a href="../mod/mod_log_config.html# α"> α</a></code> +϶.)</p> + +<p>α (ȣƮ Ͼ) ʹٸ <code><a href="../programs/other.html">split-logfile</a></code> α +Ѵ. α ġ <code>support</code> +丮 ִ.</p> + +<p> α Ѵ:</p> + +<div class="example"><p><code> +split-logfile < /logs/multiple_vhost_log +</code></p></div> + +<p>ȣƮ α α ϸ αϿ + ȣƮ ϳ . ϸ +<code>hostname.log</code>̴.</p> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../en/vhosts/fd-limits.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.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/apache2/manual/vhosts/fd-limits.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/fd-limits.html.tr.utf8 new file mode 100644 index 00000000..d6024726 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/fd-limits.html.tr.utf8 @@ -0,0 +1,128 @@ +<?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>Dosya Tanıtıcı Sınırları - 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> > <a href="./">Sanal Konaklar</a></div><div id="page-content"><div id="preamble"><h1>Dosya Tanıtıcı Sınırları</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/fd-limits.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.html" title="Türkçe"> tr </a></p> +</div> + + + <p>Çok büyük sayıda sanal konak kullanıyorsanız ve bunların her biri için + ayrı günlük kayıtları tutuyorsanız, Apache dosya tanıtıcılarını + tüketebilir. Apache tarafından, dahili olarak 10-20 dosya tanıtıcıya ek + olarak her hata günlüğü için bir ve her diğer günlük kaydı için bir dosya + tanıcı kullanılır. Unix işletim sisteminde dosya tanıtıcıların sayısı + süreç başına 64 taneyle sınırlıdır ve gerekirse donanıma bağlı olarak + arttırılabilir.</p> + + <p>Apache gerektiğinde bu sınırı kendisi arttırmaya çalışırsa da bu her + zaman mümkün olmaz. Şöyle ki:</p> + + <ol> + <li>Sisteminiz <code>setrlimit()</code> sistem çağrısını + sağlamıyordur.</li> + + <li>Sisteminizde <code>setrlimit(RLIMIT_NOFILE)</code> çağrısı hiçbir işe + yaramıyordur (örneğin, Solaris 2.3).</li> + + <li>Dosya tanıtıcılarının sayısı donanıma bağlı olarak daha fazla + arttırılamıyordur.</li> + + <li>Sisteminiz dosya tanıtıcı sayısını başka sınırlara bağlı kılmıştır: + örneğin stdio akımları ile ilgili sınır, dosya tanıtıcı sayısının + 256’nın altında ollmasını gerektiriyordur (Solaris 2).</li> + </ol> + + <p>Böyle sorunlar karşısında yapabilecekleriniz:</p> + + <ul><li>Ana günlük dosyaları hariç, <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümlerinde günlük dosyası + belirtmeyerek günlük dosyası sayısını düşürürsünüz. (Bunun nasıl + yapılacağını öğrenmek için <a href="#splitlogs">Günlük kayıtlarının + ayrıştırılması</a> bölümüne bakınız.)</li> + + <li>Sisteminizde serbest dosya tanıtıcı sayısı 1-2 civarına düşerse + Apache’yi aşağıdaki gibi bir betikle yeniden çalıştırarak dosya + tanıtıcı sayısını arttırabilirsiniz: + + <div class="example"><p><code> + <code>#!/bin/sh<br /> + ulimit -S -n 100<br /> + exec httpd</code> + </code></p></div> + </li> + </ul> + + <p>Dosya tanıtıcılarla ilgili sorunlar ve bunların işletim sisteminizde + nasıl çözülebileceğiyle ilgili bilgi edinmek için <a href="../misc/descriptors.html">Dosya Tanıtıcılar ve Apache</a> + belgesine bakı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="splitlogs" id="splitlogs">Günlük kayıtlarının ayrıştırılması</a></h2> + + <p>Günlük dosyalarını çok sayıda sanal konak için ortak olarak + kullanıyorsanız, sanal konaklar için istatistiksel çözümlemeler yapmak + amacıyla sırası geldiğinde bunları ayrıştırabilirsiniz. Bu işlem aşağıda + anlatıldığı gibi yapılabilir.</p> + + <p>İlk iş olarak, sanal konak bilgilerini günlük girdilerine eklemeniz + gerekir. Bu işlem, <code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> yönergesi ve + <code>%v</code> biçem değişkeni ile yapılabilir. Günlük girdisi biçem + dizgesinin başına bunu ekleyiniz:</p> + + <div class="example"><p><code> + LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost<br /> + CustomLog logs/multiple_vhost_log vhost + </code></p></div> + + <p>Bu yapılandırma ile her günlük kaydının başında sanal konağın + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> yönergesine belirtilen + ismi eklenir. (Günlük dosyalarınızın kişiselleştirilmesi ile ilgili daha + fazla bilgi için <a href="../mod/mod_log_config.html#formats">Günlük + Girdilerinin Kişiselleştirilmesi</a> konusuna bakınız.)</p> + + <p>Günlük dosyanızdaki kayıtları bileşenlere göre gruplamak isterseniz + <code><a href="../programs/other.html">split-logfile</a></code> + programını kullanabilirsiniz. Bu programı Apache dağıtımının + <code>support</code> dizininde bulabilirsiniz.</p> + + <p>Programı aşağıdaki gibi çalıştırın:</p> + + <div class="example"><p><code> + split-logfile < /logs/multiple_vhost_log + </code></p></div> + + <p>Bu programı sanal konaklar için tuttuğunuz günlük dosyasının ismini + argüman olarak belirterek çalıştırdığınızda o dosyadaki kayıtlardan her + sanal konak için ayrı bir günlük dosyası + (<code><em>konakadı</em>.log</code>) üretilir.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/fd-limits.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ja/vhosts/fd-limits.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/fd-limits.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/fd-limits.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/apache2/manual/vhosts/index.html b/rubbos/app/apache2/manual/vhosts/index.html new file mode 100644 index 00000000..b2002505 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html @@ -0,0 +1,29 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: index.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.utf8 +Content-Language: ja +Content-type: text/html; charset=UTF-8 + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: index.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R + +URI: index.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/index.html.de b/rubbos/app/apache2/manual/vhosts/index.html.de new file mode 100644 index 00000000..fcceffa5 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.de @@ -0,0 +1,112 @@ +<?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="de" xml:lang="de"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache-Dokumentation zu virtuellen Hosts - 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/">Module</a> | <a href="../mod/directives.html">Direktiven</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossar</a> | <a href="../sitemap.html">Seitenindex</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/">Dokumentation</a> > <a href="../">Version 2.0</a></div><div id="page-content"><div id="preamble"><h1>Apache-Dokumentation zu virtuellen Hosts</h1> +<div class="toplang"> +<p><span>Verfgbare Sprachen: </span><a href="../de/vhosts/" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + <p>Der Begriff <cite>virtueller Host</cite> <span class="transnote">(<em>Anm.d..:</em> engl. 'virtual + host')</span> bezieht sich auf die Praxis, mehr als ein Webangebot + (z.B. <code>www.company1.com</code> und <code>www.company2.com</code>) + auf einer einzigen Maschine zu betreiben. Virtuelle Hosts knnen + "<a href="ip-based.html">IP-basiert</a>" sein, was bedeutet, dass jedes + Webangebot eine andere IP besitzt, oder "<a href="name-based.html">Namens-basiert</a>", was bedeutet, dass + unter jeder IP-Adresse mehrere Namen laufen. Die Tatsache, dass sie + auf dem gleichen physischen Server laufen, ist fr den Endbenutzer + nicht offensichtlich.</p> + + <p>Der Apache war einer der ersten Server, der IP-basierte + virtuelle Hosts von Haus aus direkt untersttzt hat. Seit Version 1.1 + untersttzt der Apache sowohl IP-basierte als auch namensbasierte + virtuelle Hosts (vhosts). Letzteres wird zuweilen auch + <em>Host-basiert</em> oder <em>non-IP-Virtual-Host</em> genannt.</p> + + <p>Nachfolgend finden Sie eine Liste von Dokumenten, die alle Details + der Untersttzung von virtuellen Hosts ab Apache Version 1.3 + beschreiben.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support">Untersttzung virtueller Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives">Konfigurationsdirektiven</a></li> +</ul><h3>Siehe auch</h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html">Namensbasierte virtuelle Hosts</a></li><li><a href="ip-based.html">IP-basierte virtuelle Hosts</a></li><li><a href="examples.html">Beispiele fr virtuelle + Hosts</a></li><li><a href="fd-limits.html">Datei-Deskriptor-Begrenzungen</a></li><li><a href="mass.html">Massen-Virtual-Hosting</a></li><li><a href="details.html">Zuweisung virtueller Hosts</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="support" id="support">Untersttzung virtueller Hosts</a></h2> + + <ul> + <li><a href="name-based.html">Namensbasierte virtuelle Hosts</a> (Mehr + als ein Webangebot pro IP-Adresse)</li> + <li><a href="ip-based.html">IP-basierte virtuelle Hosts</a> (Eine + IP-Adresse fr jedes Webangebot)</li> + <li><a href="examples.html">Beispiele fr virtuelles Hosts in + typischen Installationen</a></li> + <li><a href="fd-limits.html">Datei-Deskriptor-Begrenzungen</a> (oder + <em>Zu viele Protokolldateien</em>)</li> + <li><a href="mass.html">Dynamisch konfiguriertes + Massen-Virtual-Hosting</a></li> + <li><a href="details.html">Tiefergehende Errterung der Zuweisung + virtueller Hosts</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="directives" id="directives">Konfigurationsdirektiven</a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p>Bei der Suche von Fehlern in Ihrer Virtual-Host-Konfiguration ist + die Apache-Befehlszeilenoption <code>-S</code> mglicherweise + hilfreich. Geben Sie dazu den folgenden Befehl ein:</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p>Diese Anweisung gibt eine Beschreibung aus, wie der Apache die + Konfigurationsdatei analysiert hat. Eine sorgfltige + berprfung der IP-Adressen und Servernamen kann helfen, + Konfigurationsfehler aufzudecken. (Lesen Sie die Dokumentation zum + <code class="program"><a href="../programs/httpd.html">httpd</a></code>-Programm fr weitere + Befehlszeilenoptionen.)</p> +</div></div> +<div class="bottomlang"> +<p><span>Verfgbare Sprachen: </span><a href="../de/vhosts/" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Lizenziert unter der <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Module</a> | <a href="../mod/directives.html">Direktiven</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossar</a> | <a href="../sitemap.html">Seitenindex</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/apache2/manual/vhosts/index.html.en b/rubbos/app/apache2/manual/vhosts/index.html.en new file mode 100644 index 00000000..31b11b4c --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.en @@ -0,0 +1,112 @@ +<?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 Virtual Host 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"><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 Virtual Host documentation</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + + <p>The term <cite>Virtual Host</cite> refers to the practice of + running more than one web site (such as + <code>www.company1.com</code> and <code>www.company2.com</code>) + on a single machine. Virtual hosts can be "<a href="ip-based.html">IP-based</a>", meaning that you have a + different IP address for every web site, or "<a href="name-based.html">name-based</a>", meaning that you have + multiple names running on each IP address. The fact that they + are running on the same physical server is not apparent to the + end user.</p> + + <p>Apache was one of the first servers to support IP-based + virtual hosts right out of the box. Versions 1.1 and later of + Apache support both IP-based and name-based virtual hosts + (vhosts). The latter variant of virtual hosts is sometimes also + called <em>host-based</em> or <em>non-IP virtual hosts</em>.</p> + + <p>Below is a list of documentation pages which explain all + details of virtual host support in Apache version 1.3 and + later.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support">Virtual Host Support</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives">Configuration directives</a></li> +</ul><h3>See also</h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html">Name-based virtual +hosts</a></li><li><a href="ip-based.html">IP-based virtual hosts</a></li><li><a href="examples.html">Virtual host examples</a></li><li><a href="fd-limits.html">File descriptor limits</a></li><li><a href="mass.html">Mass virtual hosting</a></li><li><a href="details.html">Details of host matching</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="support" id="support">Virtual Host Support</a></h2> + + <ul> + <li><a href="name-based.html">Name-based Virtual Hosts</a> (More + than one web site per IP address)</li> + <li><a href="ip-based.html">IP-based Virtual Hosts</a> (An IP + address for each web site)</li> + <li><a href="examples.html">Virtual Host examples for common + setups</a></li> + <li><a href="fd-limits.html">File Descriptor Limits</a> (or, + <em>Too many log files</em>)</li> + <li><a href="mass.html">Dynamically Configured Mass Virtual + Hosting</a></li> + <li><a href="details.html">In-Depth Discussion of Virtual Host + Matching</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="directives" id="directives">Configuration directives</a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p>If you are trying to debug your virtual host configuration, you + may find the Apache <code>-S</code> command line switch + useful. That is, type the following command:</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p>This command will dump out a description of how Apache parsed + the configuration file. Careful examination of the IP addresses and + server names may help uncover configuration mistakes. (See + the docs for the <code class="program"><a href="../programs/httpd.html">httpd</a></code> program for + other command line options)</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/index.html.es b/rubbos/app/apache2/manual/vhosts/index.html.es new file mode 100644 index 00000000..449b8005 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.es @@ -0,0 +1,119 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Documentacin sobre Hosting Virtual en Apache - Servidor HTTP Apache</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/">Mdulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="../faq/">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa de este sitio web</a></p> +<p class="apache">Versin 2.0 del Servidor HTTP Apache</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/">Servidor HTTP</a> > <a href="http://httpd.apache.org/docs/">Documentacin</a> > <a href="../">Versin 2.0</a></div><div id="page-content"><div id="preamble"><h1>Documentacin sobre Hosting Virtual en Apache</h1> +<div class="toplang"> +<p><span>Idiomas disponibles: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" title="Espaol"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + + <p>El trmino <cite>Hosting Virtual</cite> se refiere a hacer + funcionar ms de un sitio web (tales como + <code>www.company1.com</code> y <code>www.company2.com</code>) en + una sola mquina. Los sitios web virtuales pueden estar "<a href="ip-based.html">basados en direcciones IP</a>", lo que + significa que cada sitio web tiene una direccin IP diferente, o + "<a href="name-based.html">basados en nombres diferentes</a>", lo + que significa que con una sola direccin IP estn funcionando + sitios web con diferentes nombres (de dominio). El hecho de que estn + funcionando en la misma mquina fsica pasa completamente + desapercibido para el usuario que visita esos sitios web.</p> + + <p>Apache fue uno de los primeros servidores web en soportar + hosting virtual basado en direcciones IP. Las versiones 1.1 y + posteriores de Apache soportan hosting virtual (vhost) basado tanto + en direcciones IP como basado en nombres. sta ltima variante de + hosting virtual se llama algunas veces <em>basada en host</em> o + <em>hosting virtual no basado en IP</em>.</p> + + <p>Ms abajo se muestra un listado de documentos que explican en + detalle cmo funciona el hosting virtual en las versiones de + Apache 1.3 y posteriores.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support">Soporte de Hosting Virtual</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives">Directivas de configuracin</a></li> +</ul><h3>Consulte tambin</h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html">Hosting virtual basado en nombres</a></li><li><a href="ip-based.html">Hosting virtual basado en IPs</a></li><li><a href="examples.html">Ejemplo de Hosting Virtual</a></li><li><a href="fd-limits.html">Lmites de descriptores de ficheros</a></li><li><a href="mass.html">Hosting virtual masivo</a></li><li><a href="details.html">Detalles del proceso de seleccin de +host virtual</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="support" id="support">Soporte de Hosting Virtual</a></h2> + + <ul> + <li><a href="name-based.html">Hosting virtual basado en + nombres</a> (Ms de un sitio web con una sola direccin IP)</li> + <li><a href="ip-based.html">Hosting virtual basado en IPs</a> + (Una direccin IP para cada sitio web)</li> + <li><a href="examples.html">Ejemplos tpicos de + configuracin para usar hosting virtual</a></li> + <li><a href="fd-limits.html">Lmites a los descriptores de + ficheros</a> (o, <em>demasiados ficheros de registro</em>)</li> + <li><a href="mass.html">Configuracin dinmica de + Hosting virtual masivo</a></li> + <li><a href="details.html">Discusin en profundidad sobre el + proceso de seleccin de hosting virtual</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="directives" id="directives">Directivas de configuracin</a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p>Si est tratando de solucionar problemas de + configuracin de su hosting virtual, puede que le sea de + utilidad usar la opcin de lnea de comandos de Apache + <code>-S</code>. Es decir, el siguiente comando:</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p>Este comando le devolver una descripcin de + cmo Apache analiza e interpreta el fichero de + configuracin. Para saber si contiene errores de + configuracin, es conveniente que examine con atencin + las direcciones IP y los nombres de servidor que est + usando. (Consulte la documentacin sobre el programa + <code class="program"><a href="../programs/httpd.html">httpd</a></code> para obtener informacin sobre otras + opciones de lnea de comandos)</p> + +</div></div> +<div class="bottomlang"> +<p><span>Idiomas disponibles: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" title="Espaol"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licencia bajo los trminos de la <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Mdulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="../faq/">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa de este sitio web</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/apache2/manual/vhosts/index.html.ja.utf8 b/rubbos/app/apache2/manual/vhosts/index.html.ja.utf8 new file mode 100644 index 00000000..dd975d2e --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.ja.utf8 @@ -0,0 +1,108 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ja" xml:lang="ja"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache バーチャルホスト説明書 - Apache HTTP サーバ</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 サーバ バージョン 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 サーバ</a> > <a href="http://httpd.apache.org/docs/">ドキュメンテーション</a> > <a href="../">バージョン 2.0</a></div><div id="page-content"><div id="preamble"><h1>Apache バーチャルホスト説明書</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate">This translation may be out of date. Check the + English version for recent changes.</div> + + + <p><cite>バーチャルホスト</cite>という用語は、1 台のマシン上で + (<code>www.company1.com</code> and <code>www.company2.com</code> のような) + 二つ以上のウェブサイトを扱う運用方法のことを指します。 + バーチャルホストには、各ウェブサイトに違う IP アドレスがある + 「<a href="ip-based.html">IP ベース</a>」と、それぞれの IP アドレスに + 複数の名前がある「<a href="name-based.html">名前ベース</a>」とがあります。 + 複数のサイトが物理的に同じサーバで扱われている、ということはエンドユーザには + 明らかではありません。</p> + + <p>Apache は、特に手を入れない状態で IP ベースのバーチャルホスト + をサポートした最初のサーバの一つです。バージョン 1.1 以降の Apache + では、IP ベースとネームベースのバーチャルホストの両方をサポート + しています。ネームベースのバーチャルホストは、<em>ホストベース</em>あるいは + <em>非 IP ベース</em>のバーチャルホストと呼ばれることもあります。</p> + + <p>以下のページでは、Apache バージョン 1.3 + 以降でのバーチャルホストのサポートについての詳細を説明します。</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support">バーチャルホストのサポート</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives">設定ディレクティブ</a></li> +</ul><h3>参照</h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html">ネームベースのバーチャルホスト</a></li><li><a href="ip-based.html">IP ベースのバーチャルホスト</a></li><li><a href="examples.html">バーチャルホストの一般的な設定例</a></li><li><a href="fd-limits.html">ファイル記述子の限界</a></li><li><a href="mass.html">大量のバーチャルホストの設定</a></li><li><a href="details.html">バーチャルホストのマッチングについての詳細</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="support" id="support">バーチャルホストのサポート</a></h2> + + <ul> + <li><a href="name-based.html">ネームベースのバーチャルホスト</a> + (一つの IP アドレスに複数のウェブサイト)</li> + <li><a href="ip-based.html">IP ベースのバーチャルホスト</a> + (各ウェブサイトに IP アドレス)</li> + <li><a href="examples.html">バーチャルホストの一般的な設定例</a></li> + <li><a href="fd-limits.html">ファイル記述子の限界</a> + (または、<em>多過ぎるログファイル</em>)</li> + <li><a href="mass.html">大量のバーチャルホストの設定</a></li> + <li><a href="details.html">バーチャルホストのマッチングについての詳細</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="directives" id="directives">設定ディレクティブ</a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p>バーチャルホストの設定のデバッグをするには + Apache のコマンドラインスイッチ <code>-S</code> が便利です。 + つまり、以下のコマンドを入力します:</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p>このコマンドは Apache が設定ファイルをどう解析したかについて出力します。 + IP アドレスとサーバ名を注意深く調べれば、 + 設定の間違いを見つける助けになるでしょう。 + (他のコマンドラインのオプションは <a href="../programs/httpd.html">httpd プログラムの説明文書</a>を見てください)</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" 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/apache2/manual/vhosts/index.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/index.html.ko.euc-kr new file mode 100644 index 00000000..fe4fb775 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.ko.euc-kr @@ -0,0 +1,110 @@ +<?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></div><div id="page-content"><div id="preamble"><h1>ġ ȣƮ </h1> +<div class="toplang"> +<p><span> : </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate"> ֽ ƴմϴ. + ֱٿ ϼ.</div> + + + <p><cite>ȣƮ (Virtual Host)</cite> ǻͿ + Ʈ ( , <code>www.company1.com</code> + <code>www.company2.com</code>) Ѵ. + ȣƮ Ʈ ٸ IP ּҸ ϴ + "<a href="ip-based.html">IP (IP-based)</a>" İ + IP ּҴ ̸ "<a href="name-based.html"≯ (name-based)</a>" + ִ. Ʈ ִٴ ڴ + ġä Ѵ.</p> + + <p>ġ ⺻ IP ȣƮ â + ϳ. ġ 1.1 ̻ IPݰ ̸ + ȣƮ Ѵ. ̸ ȣƮ + <em>ȣƮ (host-based)</em> Ǵ <em>IP ȣƮ + (non-IP virtual hosts)</em> θ.</p> + + <p> ġ 1.3 ̻ ȣƮ ڼ + ̴.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support">ȣƮ </a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives"> þ</a></li> +</ul><h3></h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html"≯ ȣƮ</a></li><li><a href="ip-based.html">IP ȣƮ</a></li><li><a href="examples.html">ȣƮ </a></li><li><a href="fd-limits.html">ϱ Ѱ</a></li><li><a href="mass.html">뷮 ȣƮ</a></li><li><a href="details.html">ȣƮ ã ڼ </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="support" id="support">ȣƮ </a></h2> + + <ul> + <li><a href="name-based.html"≯ ȣƮ</a> + (IP ּҴ Ʈ)</li> + <li><a href="ip-based.html">IP ȣƮ</a> ( + Ʈ IP ּ)</li> + <li><a href="examples.html">Ϲ ȣƮ </a></li> + <li><a href="fd-limits.html">ϱ(file descriptor) + Ѱ</a> (, <em>ʹ α</em>)</li> + <li><a href="mass.html">뷮 ȣƮ + ϱ</a></li> + <li><a href="details.html">ȣƮ ã ڼ + </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="directives" id="directives"> þ</a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p>ȣƮ ƮҶ ġ <code>-S</code> + ɼ ϴ. , Ѵ:</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p> ɾ ġ Ͽ + Ѵ. IP ּҿ ڼ 캸 + Ǽ ߰ϴµ ̴. (ٸ ɼǵ + <a href="../programs/httpd.html">httpd α </a> + ϶.)</p> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" 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/apache2/manual/vhosts/index.html.ru.koi8-r b/rubbos/app/apache2/manual/vhosts/index.html.ru.koi8-r new file mode 100644 index 00000000..da6f38a5 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.ru.koi8-r @@ -0,0 +1,107 @@ +<?xml version="1.0" encoding="KOI8-R"?> +<!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="ru" xml:lang="ru"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title> Apache - HTTP Apache</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">HTTP Apache 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 </a> > <a href="http://httpd.apache.org/docs/"></a> > <a href="../"> 2.0</a></div><div id="page-content"><div id="preamble"><h1> Apache</h1> +<div class="toplang"> +<p><span> : </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" title="Russian"> ru </a> | +<a href="../tr/vhosts/" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + + <p> <cite> </cite> + - (, + <code>www.company1.com</code> <code>www.company2.com</code>) + . «<a href="ip-based.html"> IP-</a>», + IP , «<a href="name-based.html"> </a>», + ͣ IP-. , + , + .</p> + + <p>Apache , IP- + . Apache 1.1 + IP-, , . + + <em>-</em> <em>-IP </em>.</p> + + <p> , + Apache 1.3 .</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support"> </a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives"> </a></li> +</ul><h3>. </h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html"> , </a></li><li><a href="ip-based.html">IP- </a></li><li><a href="examples.html"> </a></li><li><a href="fd-limits.html"> </a></li><li><a href="mass.html"> </a></li><li><a href="details.html"> </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="support" id="support"> </a></h2> + + <ul> + <li><a href="name-based.html"> , </a> + ( - IP ).</li> + <li><a href="ip-based.html">IP- </a> ( + IP -).</li> + <li><a href="examples.html"> </a>.</li> + <li><a href="fd-limits.html"> </a> (, + <em>Too many log files</em>)</li> + <li><a href="mass.html"> </a></li> + <li><a href="details.html"> </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="directives" id="directives"> </a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p> , + Apache <code>-S</code> . + , :</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p> , Apache + . IP ͣ + . ( + <code class="program"><a href="../programs/httpd.html">httpd</a></code> + .)</p> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" title="Russian"> ru </a> | +<a href="../tr/vhosts/" 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/apache2/manual/vhosts/index.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/index.html.tr.utf8 new file mode 100644 index 00000000..c9c54a51 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/index.html.tr.utf8 @@ -0,0 +1,107 @@ +<?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 Sanal Konak Belgeleri - 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></div><div id="page-content"><div id="preamble"><h1>Apache Sanal Konak Belgeleri</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" title="Türkçe"> tr </a></p> +</div> + + + <p><cite>Sanal Konak</cite> (Virtual Host) terimi tek bir makine üzerinde + birden fazla sitenin (www.sirket1.dom, www.sirket2.dom gibi) barındırılma + uygulamasını betimler. Sanal konaklar, "<a href="ip-based.html">IP’ye dayalı</a>" veya "<a href="name-based.html">isme dayalı</a>" olabilir; birincisinde, her site + ayrı bir IP adresinden sunulurken, ikincisinde her IP adresinde birden + fazla site sunulur. Olayda aynı fiziksel sunucu kullanıldığı halde bu + sunucu son kullanıcıya görünür değildir.</p> + + <p>Apache yazılımsal olarak IP’ye dayalı sanal konakları destekleyen ilk + sunuculardan biridir. 1.1 sürümünden itibaren Apache hem IP’ye dayalı hem + de isme dayalı sanal konakları desteklemektedir. İsme dayalı sanal + konaklara bazen <em>konağa dayalı</em> sanal konaklar veya <em>IP’ye + dayanmayan</em> sanal konaklar da denmektedir.</p> + + <p>Aşağıda, Apache’nin 1.3 sürümü ve sonrası için sanal konak desteğini bütün + ayrıntıları ile açıklayan belgeler listelenmiştir.</p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#support">Sanal Konak Desteği</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#directives">Yapılandırma Yönergeleri</a></li> +</ul><h3>Ayrıca bakınız:</h3><ul class="seealso"><li><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li><li><a href="name-based.html">İsme Dayalı Sanal Konaklar</a></li><li><a href="ip-based.html">IP Adresine Dayalı Sanal Konaklar</a></li><li><a href="examples.html">Sanal Konak Örnekleri</a></li><li><a href="fd-limits.html">Dosya Tanıtıcı Sınırları</a></li><li><a href="mass.html">Kütlesel Sanal Konaklık</a></li><li><a href="details.html">Ayrıntılı olarak Konak Eşleme</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="support" id="support">Sanal Konak Desteği</a></h2> + + <ul> + <li><a href="name-based.html">İsme Dayalı Sanal Konaklar</a> (Her IP + adresinde birden fazla site)</li> + <li><a href="ip-based.html">IP Adresine Dayalı Sanal Konaklar</a> (Her site + için ayrı IP adresi)</li> + <li><a href="examples.html">Çok kullanılan sanal konak yapılandırma + örnekleri</a></li> + <li><a href="fd-limits.html">Dosya Tanıtıcı Sınırları</a> (veya, + <em>çok fazla günlük dosyası</em>)</li> + <li><a href="mass.html">Devingen olarak Yapılandırılan Kütlesel Sanal + Barındırma</a></li> + <li><a href="details.html">Konak Eşlemenin Derinliğine İncelenmesi</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="directives" id="directives">Yapılandırma Yönergeleri</a></h2> + + <ul> + <li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li> + <li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li> + <li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li> + <li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li> + </ul> + + <p>Sanal konak yapılandırmanız üzerinde hata ayıklamaya çalışıyorsanız + Apache’nin <code>-S</code> komut satırı seçeneği şu şekilde çok işinize + yarayabilir:</p> + + <div class="example"><p><code> + /usr/local/apache2/bin/httpd -S + </code></p></div> + + <p>Bu komut, yapılandırma dosyasının Apache yorumunu dökümler. IP + adreslerinin ve sunucu isimlerinin dikkatli bir incelemesi, yapılandırma + yanlışlarınızı keşfetmenize yardımcı olabilir. (Diğer komut satırı + seçenekleri için <code class="program"><a href="../programs/httpd.html">httpd</a></code> programının belgelerine + bakınız.)</p> + +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../de/vhosts/" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../ru/vhosts/" hreflang="ru" rel="alternate" title="Russian"> ru </a> | +<a href="../tr/vhosts/" 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/apache2/manual/vhosts/ip-based.html b/rubbos/app/apache2/manual/vhosts/ip-based.html new file mode 100644 index 00000000..f2417b60 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/ip-based.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: ip-based.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ip-based.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: ip-based.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/ip-based.html.en b/rubbos/app/apache2/manual/vhosts/ip-based.html.en new file mode 100644 index 00000000..51fa0b07 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/ip-based.html.en @@ -0,0 +1,160 @@ +<?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 IP-based Virtual Host Support - 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="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>Apache IP-based Virtual Host Support</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/vhosts/ip-based.html" title="English"> en </a> | +<a href="../ko/vhosts/ip-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/ip-based.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">System requirements</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#howto">How to set up Apache</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#multiple">Setting up multiple daemons</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#single">Setting up a single daemon + with virtual hosts</a></li> +</ul><h3>See also</h3><ul class="seealso"><li> +<a href="name-based.html">Name-based Virtual Hosts Support</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="requirements" id="requirements">System requirements</a></h2> + + <p>As the term <cite>IP-based</cite> indicates, the server + <strong>must have a different IP address for each IP-based + virtual host</strong>. This can be achieved by the machine + having several physical network connections, or by use of + virtual interfaces which are supported by most modern operating + systems (see system documentation for details, these are + frequently called "ip aliases", and the "ifconfig" command is + most commonly used to set them up).</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="howto" id="howto">How to set up Apache</a></h2> + + <p>There are two ways of configuring apache to support multiple + hosts. Either by running a separate <code class="program"><a href="../programs/httpd.html">httpd</a></code> daemon for + each hostname, or by running a single daemon which supports all the + virtual hosts.</p> + + <p>Use multiple daemons when:</p> + + <ul> + <li>There are security partitioning issues, such as company1 + does not want anyone at company2 to be able to read their + data except via the web. In this case you would need two + daemons, each running with different <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code>, <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code>, <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, and <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> settings.</li> + + <li>You can afford the memory and <a href="../misc/descriptors.html">file descriptor + requirements</a> of listening to every IP alias on the + machine. It's only possible to <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> to the "wildcard" + address, or to specific addresses. So if you have a need to + listen to a specific address for whatever reason, then you + will need to listen to all specific addresses. (Although one + <code class="program"><a href="../programs/httpd.html">httpd</a></code> could listen to N-1 of the addresses, and another could + listen to the remaining address.)</li> + </ul> + + <p>Use a single daemon when:</p> + + <ul> + <li>Sharing of the httpd configuration between virtual hosts + is acceptable.</li> + + <li>The machine services a large number of requests, and so + the performance loss in running separate daemons may be + significant.</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="multiple" id="multiple">Setting up multiple daemons</a></h2> + + <p>Create a separate <code class="program"><a href="../programs/httpd.html">httpd</a></code> installation for each + virtual host. For each installation, use the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the + configuration file to select which IP address (or virtual host) + that daemon services. e.g.</p> + + <div class="example"><p><code> + Listen www.smallco.com:80 + </code></p></div> + + <p>It is recommended that you use an IP address instead of a + hostname (see <a href="../dns-caveats.html">DNS caveats</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="single" id="single">Setting up a single daemon + with virtual hosts</a></h2> + + <p>For this case, a single httpd will service requests for the + main server and all the virtual hosts. The <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> directive + in the configuration file is used to set the values of <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code>, <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>, <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code> and <code class="directive"><a href="../mod/mod_log_config.html#transferlog">TransferLog</a></code> + or <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> + configuration directives to different values for each virtual + host. e.g.</p> + + <div class="example"><p><code> + <VirtualHost www.smallco.com><br /> + ServerAdmin webmaster@mail.smallco.com<br /> + DocumentRoot /groups/smallco/www<br /> + ServerName www.smallco.com<br /> + ErrorLog /groups/smallco/logs/error_log<br /> + TransferLog /groups/smallco/logs/access_log<br /> + </VirtualHost><br /> + <br /> + <VirtualHost www.baygroup.org><br /> + ServerAdmin webmaster@mail.baygroup.org<br /> + DocumentRoot /groups/baygroup/www<br /> + ServerName www.baygroup.org<br /> + ErrorLog /groups/baygroup/logs/error_log<br /> + TransferLog /groups/baygroup/logs/access_log<br /> + </VirtualHost> + </code></p></div> + + <p>It is recommended that you use an IP address instead of a + hostname (see <a href="../dns-caveats.html">DNS caveats</a>).</p> + + <p>Almost <strong>any</strong> configuration directive can be + put in the VirtualHost directive, with the exception of + directives that control process creation and a few other + directives. To find out if a directive can be used in the + VirtualHost directive, check the <a href="../mod/directive-dict.html#Context">Context</a> using the + <a href="../mod/directives.html">directive index</a>.</p> + + <p><code class="directive"><a href="../mod/mod_suexec.html#suexecusergroup">SuexecUserGroup</a></code> + may be used inside a + VirtualHost directive if the <a href="../suexec.html">suEXEC + wrapper</a> is used.</p> + + <p><em>SECURITY:</em> When specifying where to write log files, + be aware of some security risks which are present if anyone + other than the user that starts Apache has write access to the + directory where they are written. See the <a href="../misc/security_tips.html">security tips</a> document + for details.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/ip-based.html" title="English"> en </a> | +<a href="../ko/vhosts/ip-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/ip-based.html" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/ip-based.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/ip-based.html.ko.euc-kr new file mode 100644 index 00000000..96fd784b --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/ip-based.html.ko.euc-kr @@ -0,0 +1,150 @@ +<?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>ġ IP ȣƮ - 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="./">ȣƮ</a></div><div id="page-content"><div id="preamble"><h1>ġ IP ȣƮ </h1> +<div class="toplang"> +<p><span> : </span><a href="../en/vhosts/ip-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/ip-based.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/ip-based.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate"> ֽ ƴմϴ. + ֱٿ ϼ.</div> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">ý 䱸</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#howto">ġ </a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#multiple"> ϱ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#single"> ϳ ȣƮ ϱ</a></li> +</ul><h3></h3><ul class="seealso"><li> +<a href="name-based.html"≯ ȣƮ </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="requirements" id="requirements">ý 䱸</a></h2> + + <p><cite>IP</cite>̶ ǹϵ + <strong>IP ȣƮ ٸ IP ּҸ + Ѵ</strong>. ̴ ǻ Ʈ + ϰų, ֱ ü ϴ ̽ + (ڼ ý ϶. "ip aliases" + ϸ, "ifconfig" ɾ ) Ͽ ϴ.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="howto" id="howto">ġ </a></h2> + + <p> ȣƮ ϵ ġ ϴ ΰ. + ϳ ȣƮ ϴ + ̰, ٸ ϳ ȣƮ ϴ Ѱ + ϴ ̴.</p> + + <p> ϳ:</p> + + <ul> + <li>ȸ2 ڰ ̿ ȸ1 ڷḦ + ϴ Ȼ ʿ . + ٸ <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code>, <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code>, <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> ؾ Ѵ.</li> + + <li> ְ, ǻ IP ٸ + <a href="../misc/descriptors.html">ϱ(file descriptor) + 䱸</a> Ѵ. "ϵī" Ư ּҸ <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> ִ. + Ư ּҸ ٸ ʿ䰡 ִٸ, ( + ּҸ ּҸ ٸ ٸ + ּҸ ٸ ) ּ + θ ٷ Ѵ.</li> + </ul> + + <p> Ѱ ϳ:</p> + + <ul> + <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="multiple" id="multiple"> ϱ</a></h2> + + <p> ȣƮ ġѴ. + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> þ + IP ּ(Ȥ ȣƮ) ش. + ,</p> + + <div class="example"><p><code> + Listen www.smallco.com:80 + </code></p></div> + + <p>ȣƮ ٴ IP ּҸ ϱ ٶ. + (<a href="../dns-caveats.html">DNS </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="single" id="single"> ϳ ȣƮ ϱ</a></h2> + + <p> Ѱ ּ ȣƮ + û Ѵ. <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> þ ȣƮ + ٸ <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code>, + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>, <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code>, <code class="directive"><a href="../mod/mod_log_config.html#transferlog">TransferLog</a></code>, + <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> + þ Ѵ. ,</p> + + <div class="example"><p><code> + <VirtualHost www.smallco.com><br /> + ServerAdmin webmaster@mail.smallco.com<br /> + DocumentRoot /groups/smallco/www<br /> + ServerName www.smallco.com<br /> + ErrorLog /groups/smallco/logs/error_log<br /> + TransferLog /groups/smallco/logs/access_log<br /> + </VirtualHost><br /> + <br /> + <VirtualHost www.baygroup.org><br /> + ServerAdmin webmaster@mail.baygroup.org<br /> + DocumentRoot /groups/baygroup/www<br /> + ServerName www.baygroup.org<br /> + ErrorLog /groups/baygroup/logs/error_log<br /> + TransferLog /groups/baygroup/logs/access_log<br /> + </VirtualHost> + </code></p></div> + + <p>ȣƮ ٴ IP ּҸ ϱ ٶ. + (<a href="../dns-caveats.html">DNS </a> )</p> + + <p>VirtualHost þ ȿ μ Ÿ þ + ϰ <strong></strong> þ + ִ. VirtualHost þ ȿ þ ִ + ˷ <a href="../mod/directives.html">þ </a> + <a href="../mod/directive-dict.html#Context"></a> + Ȯ϶.</p> + + <p><a href="../suexec.html">suEXEC α</a> + Ѵٸ VirtualHost þ ȿ <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code> ִ.</p> + + <p><em>:</em> ϴ ڿܿ ٸ + α ִ 丮 ִٸ + ϶. ڼ <a href="../misc/security_tips.html"> </a> ϶.</p> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../en/vhosts/ip-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/ip-based.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/ip-based.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/apache2/manual/vhosts/ip-based.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/ip-based.html.tr.utf8 new file mode 100644 index 00000000..78bf8a49 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/ip-based.html.tr.utf8 @@ -0,0 +1,165 @@ +<?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’de IP’ye Dayalı Sanal Konak Desteği - 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="./">Sanal Konaklar</a></div><div id="page-content"><div id="preamble"><h1>Apache’de IP’ye Dayalı Sanal Konak Desteği</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/ip-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/ip-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/ip-based.html" title="Türkçe"> tr </a></p> +</div> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">Sistem gereksinimleri</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#howto">Apache nasıl ayarlanır?</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#multiple">Çok sayıda sürecin yapılandırılması</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#single">Sanal konaklar tek bir sürecin yapılandırılması</a></li> +</ul><h3>Ayrıca bakınız:</h3><ul class="seealso"><li> +<a href="name-based.html">İsme Dayalı Sanal Konak Desteği</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="requirements" id="requirements">Sistem gereksinimleri</a></h2> + + <p><cite>IP’ye dayalı</cite> deyince, sunucunun <strong>her IP’ye dayalı + sanal konak için ayrı bir IP adresi</strong>ne sahip olduğunu anlıyoruz. + Bunun olması için, makine ya çok sayıda ağ bağlantısına sahiptir ya da + makinede, günümüzde çoğu işletim sistemi tarafından desteklenen sanal + arabirimler kullanılıyordur. (Sanal arabirimlerle ilgili ayrıntılar için + sistem belgelerinize bakınız; bu konu genellikle IP rumuzları (ip aliases) + olarak geçer ve ayarlamak için genellikle "ifconfig" komutu + kullanılı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="howto" id="howto">Apache nasıl ayarlanır?</a></h2> + + <p>Çok sayıda konağı desteklemek üzere Apache iki şekilde + yapılandırılabilir. Ya her konak için ayrı bir <code class="program"><a href="../programs/httpd.html">httpd</a></code> + süreci çalıştırırsınız ya da tüm sanal konakları destekleyen tek bir + süreciniz olur.</p> + + <p>Çok sayıda süreç kullanıyorsanız:</p> + + <ul> + <li>Güvenli bölgeler oluşturmanız gerekiyordur. Örneğin, şirket2’deki hiç + kimse dosya sistemi üzerinden şirket1’e ait verileri okuyamasın, sadece + herkes gibi tarayıcı kullanarak okuyabilsin istenebilir. Bu durumda, + <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code>, + <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code>, + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> ve + <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> yönergeleri farklı + değerlerle yapılandırılmış iki ayrı süreç çalıştırmanız gerekir.</li> + + <li>Makine üzerindeki her IP adresini dinlemek için gereken + <a href="../misc/descriptors.html">dosya tanıtıcı</a> + ve bellek miktarını makul bir seviyede tutabilirsiniz. Bu sadece belli + adresleri dinleyerek veya çok sayıda adresle eşleşen adres kalıpları + kullanarak mümükün olabilir. Zaten, bir sebeple belli bir adresi dinleme + ihtiyacı duyarsanız, diğer tüm adresleri de ayrı ayrı dinlemeniz + gerekir. (Bir <code class="program"><a href="../programs/httpd.html">httpd</a></code> programı N-1 adresi dinlerken + diğerleri kalan adresleri dinleyebilir.)</li> + </ul> + + <p>Tek bir süreç kullanıyorsanız:</p> + + <ul> + <li><code class="program"><a href="../programs/httpd.html">httpd</a></code> yapılandırmasının sanal konaklar arasında + paylaşılmasına izin veriliyor demektir.</li> + + <li>Makine çok büyük miktarda isteği karşılayabilir ve ayrı ayrı + süreçlerin çalışmasından kaynaklanan önemli başarım kayıpları + yaşanmaz.</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="multiple" id="multiple">Çok sayıda sürecin yapılandırılması</a></h2> + + <p>Her sanal konak için ayrı bir <code class="program"><a href="../programs/httpd.html">httpd</a></code> yapılandırması + oluşturulur. Her yapılandırmada, o süreç tarafından sunulacak IP adresi + (veya sanal konak) için <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + yönergesi kullanılır. Örnek:</p> + + <div class="example"><p><code> + Listen www.birkobi.dom:80 + </code></p></div> + + <p>Burada konak ismi yerine IP adresi kullanmanız önerilir (ayrıntılar için + <a href="../dns-caveats.html">DNS ile ilgili konular</a> belgesine + bakı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="single" id="single">Sanal konaklar tek bir sürecin yapılandırılması</a></h2> + + <p>Bu durum için, ana sunucu ve sanal konakların tümüne gelen istekler tek + bir <code class="program"><a href="../programs/httpd.html">httpd</a></code> süreci tarafından karşılanır. Yapılandırma + dosyasında, her sanal konak için, farklı değerlere sahip <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code>, <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>, <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code>ve<code class="directive"><a href="../mod/mod_log_config.html#transferlog">TransferLog</a></code> + veya <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> yönergeleri + içeren ayrı birer <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> bölümü + oluşturulur. Örnek:</p> + + <div class="example"><p><code> + <VirtualHost www.birkobi.dom> + <span class="indent"> + ServerAdmin bilgi@posta.birkobi.dom<br /> + DocumentRoot /gruplar/birkobi/belgeler<br /> + ServerName www.birkobi.dom<br /> + ErrorLog /gruplar/birkobi/günlükler/hatalar.log<br /> + TransferLog /gruplar/birkobi/günlükler/erisim.log + </span> + </VirtualHost><br /> + <br /> + <VirtualHost www.digerkobi.dom> + <span class="indent"> + ServerAdmin bilgi@posta.digerkobi.dom<br /> + DocumentRoot /gruplar/digerkobi/belgeler<br /> + ServerName www.digerkobi.dom<br /> + ErrorLog /gruplar/digerkobi/günlükler/hatalar.log<br /> + TransferLog /gruplar/digerkobi/günlükler/erisim.log + </span> + </VirtualHost> + </code></p></div> + + <p>Burada konak isimlerinin yerlerine IP adreslerini kullanmanız önerilir + (ayrıntılar için <a href="../dns-caveats.html">DNS ile ilgili konular</a> + belgesine bakınız).</p> + + <p>Süreç oluşturmayı denetleyen yönergeler ve bir kaç başka yönerge dışında + hemen hemen tüm yapılandırma yönergeleri <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> bölümleri içinde kullanılabilir. Bir + yönergenin <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> bölümlerinde + kullanılıp kullanılmayacağını öğrenmek için <a href="../mod/directives.html">yönerge dizinini</a> kullanarak yönergenin <a href="../mod/directive-dict.html#Context">Bağlam</a>’ına bakınız.</p> + + <p><a href="../suexec.html">suEXEC sarmalayıcısı</a> kullanıldığı takdirde + <code class="directive"><a href="../mod/mod_suexec.html#suexecusergroup">SuexecUserGroup</a></code> yönergesi de + bir <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> bölümü içinde + kullanılabilir.</p> + + <p><em>GÜVENLİK:</em>Günlük dosyalarının yazılacağı yeri belirlerken, + Apache’yi başlatan kullanıcıdan başka kimsenin yazamayacağı bir yerin + seçilmesi bazı güvenlik risklerini ortadan kaldırmak bakımından önemlidir. + Ayrıntılar için <a href="../misc/security_tips.html">güvenlik ipuçları</a> + belgesine bakınız.</p> +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/ip-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/ip-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/ip-based.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/apache2/manual/vhosts/mass.html b/rubbos/app/apache2/manual/vhosts/mass.html new file mode 100644 index 00000000..408420d1 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/mass.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: mass.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mass.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: mass.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/mass.html.en b/rubbos/app/apache2/manual/vhosts/mass.html.en new file mode 100644 index 00000000..ee0f0f1d --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/mass.html.en @@ -0,0 +1,419 @@ +<?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>Dynamically Configured Mass Virtual Hosting - 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="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>Dynamically Configured Mass Virtual Hosting</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/vhosts/mass.html" title="English"> en </a> | +<a href="../ko/vhosts/mass.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/mass.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + + <p>This document describes how to efficiently serve an + arbitrary number of virtual hosts with the Apache httpd webserver. + </p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#motivation">Motivation</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#overview">Overview</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#simple">Simple Dynamic Virtual Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#homepages">A Virtually Hosted Homepages System</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#combinations">Using Multiple Virtual + Hosting Systems on the Same Server</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ipbased">More Efficient IP-Based Virtual Hosting</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#simple.rewrite">Simple Dynamic + Virtual Hosts Using <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#homepages.rewrite">A + Homepages System Using <code>mod_rewrite</code></a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#xtra-conf">Using a Separate Virtual + Host Configuration File</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="motivation" id="motivation">Motivation</a></h2> + + <p>The techniques described here are of interest if your + <code>httpd.conf</code> contains many + <code><VirtualHost></code> sections that are + substantially the same, for example:</p> + +<div class="example"><p><code> +NameVirtualHost 111.22.33.44<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.customer-1.com<br /> + DocumentRoot /www/hosts/www.customer-1.com/docs<br /> + ScriptAlias /cgi-bin/ /www/hosts/www.customer-1.com/cgi-bin<br /> +</span> +</VirtualHost><br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.customer-2.com<br /> + DocumentRoot /www/hosts/www.customer-2.com/docs<br /> + ScriptAlias /cgi-bin/ /www/hosts/www.customer-2.com/cgi-bin<br /> +</span> +</VirtualHost><br /> +# blah blah blah<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.customer-N.com<br /> + DocumentRoot /www/hosts/www.customer-N.com/docs<br /> + ScriptAlias /cgi-bin/ /www/hosts/www.customer-N.com/cgi-bin<br /> +</span> +</VirtualHost> +</code></p></div> + + <p>The basic idea is to replace all of the static + <code><VirtualHost></code> configurations with a mechanism + that works them out dynamically. This has a number of + advantages:</p> + + <ol> + <li>Your configuration file is smaller, so Apache starts + more quickly and uses less memory.</li> + + <li>Adding virtual hosts is simply a matter of creating the + appropriate directories in the filesystem and entries in the + DNS - you don't need to reconfigure or restart Apache.</li> + </ol> + + <p>The main disadvantage is that you cannot have a different log file for + each virtual host; however, if you have many virtual hosts, doing + this can be a bad idea anyway, because of the number of file + descriptors needed. It is better to log to a pipe or a fifo, and arrange for + the process at the other end to distribute the logs to the customers. + (This can also be used to accumulate statistics, etc.).</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="overview" id="overview">Overview</a></h2> + + <p>A virtual host is defined by two pieces of information: its + IP address, and the contents of the <code>Host:</code> header + in the HTTP request. The dynamic mass virtual hosting technique + used here is based on automatically inserting this information into the + pathname of the file that is used to satisfy the request. This + can be most easily done by using <code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> + with Apache 2.0. Alternatively, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> can be used. + Both of these modules are disabled by default; you must enable + one of them when configuring and building Apache if you want to + use this technique.</p> + + <p>A couple of things need to be `faked' to make the dynamic + virtual host look like a normal one. The most important is the + server name, which is used by Apache to generate + self-referential URLs etc. It is configured with the + <code>ServerName</code> directive, and it is available to CGIs + via the <code>SERVER_NAME</code> environment variable. The + actual value used at run time is controlled by the <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> + setting. With <code>UseCanonicalName Off</code>, the server name + is taken from the contents of the <code>Host:</code> header in the + request. With <code>UseCanonicalName DNS</code>, it is taken from a + reverse DNS lookup of the virtual host's IP address. The former + setting is used for name-based dynamic virtual hosting, and the + latter is used for IP-based hosting. If Apache cannot work out + the server name because there is no <code>Host:</code> header, + or the DNS lookup fails, then the value configured with + <code>ServerName</code> is used instead.</p> + + <p>The other thing to `fake' is the document root (configured + with <code>DocumentRoot</code> and available to CGIs via the + <code>DOCUMENT_ROOT</code> environment variable). In a normal + configuration, this is used by the core module when + mapping URIs to filenames, but when the server is configured to + do dynamic virtual hosting, that job must be taken over by another + module (either <code>mod_vhost_alias</code> or + <code>mod_rewrite</code>), which has a different way of doing + the mapping. Neither of these modules is responsible for + setting the <code>DOCUMENT_ROOT</code> environment variable so + if any CGIs or SSI documents make use of it, they will get a + misleading value.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="simple" id="simple">Simple Dynamic Virtual Hosts</a></h2> + + <p>This extract from <code>httpd.conf</code> implements the + virtual host arrangement outlined in the <a href="#motivation">Motivation</a> section above, but in a + generic fashion using <code>mod_vhost_alias</code>.</p> + +<div class="example"><p><code> +# get the server name from the Host: header<br /> +UseCanonicalName Off<br /> +<br /> +# this log format can be split per-virtual-host based on the first field<br /> +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +# include the server name in the filenames used to satisfy requests<br /> +VirtualDocumentRoot /www/hosts/%0/docs<br /> +VirtualScriptAlias /www/hosts/%0/cgi-bin +</code></p></div> + + <p>This configuration can be changed into an IP-based virtual + hosting solution by just turning <code>UseCanonicalName + Off</code> into <code>UseCanonicalName DNS</code>. The server + name that is inserted into the filename is then derived from + the IP address of the virtual host.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="homepages" id="homepages">A Virtually Hosted Homepages System</a></h2> + + <p>This is an adjustment of the above system, tailored for an + ISP's homepages server. Using a slightly more complicated + configuration, we can select substrings of the server name to + use in the filename so that, for example, the documents for + <code>www.user.isp.com</code> are found in + <code>/home/user/</code>. It uses a single <code>cgi-bin</code> + directory instead of one per virtual host.</p> + +<div class="example"><p><code> +# all the preliminary stuff is the same as above, then<br /> +<br /> +# include part of the server name in the filenames<br /> +VirtualDocumentRoot /www/hosts/%2/docs<br /> +<br /> +# single cgi-bin directory<br /> +ScriptAlias /cgi-bin/ /www/std-cgi/<br /> +</code></p></div> + + <p>There are examples of more complicated + <code>VirtualDocumentRoot</code> settings in the + <code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> documentation.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="combinations" id="combinations">Using Multiple Virtual + Hosting Systems on the Same Server</a></h2> + + <p>With more complicated setups, you can use Apache's normal + <code><VirtualHost></code> directives to control the + scope of the various virtual hosting configurations. For + example, you could have one IP address for general customers' homepages, + and another for commercial customers, with the following setup. + This can, of course, be combined with conventional + <code><VirtualHost></code> configuration sections.</p> + +<div class="example"><p><code> +UseCanonicalName Off<br /> +<br /> +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon<br /> +<br /> +<Directory /www/commercial><br /> +<span class="indent"> + Options FollowSymLinks<br /> + AllowOverride All<br /> +</span> +</Directory><br /> +<br /> +<Directory /www/homepages><br /> +<span class="indent"> + Options FollowSymLinks<br /> + AllowOverride None<br /> +</span> +</Directory><br /> +<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.commercial.isp.com<br /> + <br /> + CustomLog logs/access_log.commercial vcommon<br /> + <br /> + VirtualDocumentRoot /www/commercial/%0/docs<br /> + VirtualScriptAlias /www/commercial/%0/cgi-bin<br /> +</span> +</VirtualHost><br /> +<br /> +<VirtualHost 111.22.33.45><br /> +<span class="indent"> + ServerName www.homepages.isp.com<br /> + <br /> + CustomLog logs/access_log.homepages vcommon<br /> + <br /> + VirtualDocumentRoot /www/homepages/%0/docs<br /> + ScriptAlias /cgi-bin/ /www/std-cgi/<br /> +</span> +</VirtualHost> +</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="ipbased" id="ipbased">More Efficient IP-Based Virtual Hosting</a></h2> + + <p>The configuration changes suggested to turn <a href="#simple">the first + example</a> into an IP-based virtual hosting setup result in + a rather inefficient setup. A new DNS lookup is required for every + request. To avoid this overhead, the filesystem can be arranged to + correspond to the IP addresses, instead of to the host names, thereby + negating the need for a DNS lookup. Logging will also have to be adjusted + to fit this system.</p> + +<div class="example"><p><code> +# get the server name from the reverse DNS of the IP address<br /> +UseCanonicalName DNS<br /> +<br /> +# include the IP address in the logs so they may be split<br /> +LogFormat "%A %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +# include the IP address in the filenames<br /> +VirtualDocumentRootIP /www/hosts/%0/docs<br /> +VirtualScriptAliasIP /www/hosts/%0/cgi-bin<br /> +</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="simple.rewrite" id="simple.rewrite">Simple Dynamic + Virtual Hosts Using <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></a></h2> + + <p>This extract from <code>httpd.conf</code> does the same + thing as <a href="#simple">the first example</a>. The first + half is very similar to the corresponding part above, except for + some changes, required for backward compatibility and to make the + <code>mod_rewrite</code> part work properly; the second half + configures <code>mod_rewrite</code> to do the actual work.</p> + + <p>There are a couple of especially tricky bits: by default, + <code>mod_rewrite</code> runs before other URI translation + modules (<code>mod_alias</code> etc.) - so if you wish to use these modules, <code>mod_rewrite</code> must be configured to accommodate + them. Also, some magic is required to do a + per-dynamic-virtual-host equivalent of + <code>ScriptAlias</code>.</p> + +<div class="example"><p><code> +# get the server name from the Host: header<br /> +UseCanonicalName Off<br /> +<br /> +# splittable logs<br /> +LogFormat "%{Host}i %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +<Directory /www/hosts><br /> +<span class="indent"> + # ExecCGI is needed here because we can't force<br /> + # CGI execution in the way that ScriptAlias does<br /> + Options FollowSymLinks ExecCGI<br /> +</span> +</Directory><br /> +<br /> +# now for the hard bit<br /> +<br /> +RewriteEngine On<br /> +<br /> +# a ServerName derived from a Host: header may be any case at all<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +## deal with normal documents first:<br /> +# allow Alias /icons/ to work - repeat for other aliases<br /> +RewriteCond %{REQUEST_URI} !^/icons/<br /> +# allow CGIs to work<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +# do the magic<br /> +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/docs/$1<br /> +<br /> +## and now deal with CGIs - we have to force a MIME type<br /> +RewriteCond %{REQUEST_URI} ^/cgi-bin/<br /> +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 [T=application/x-httpd-cgi]<br /> +<br /> +# that's it! +</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="homepages.rewrite" id="homepages.rewrite">A + Homepages System Using <code>mod_rewrite</code></a></h2> + + <p>This does the same thing as <a href="#homepages">the second + example</a>.</p> + +<div class="example"><p><code> +RewriteEngine on<br /> +<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +# allow CGIs to work<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +<br /> +# check the hostname is right so that the RewriteRule works<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.com$<br /> +<br /> +# concatenate the virtual host name onto the start of the URI<br /> +# the [C] means do the next rewrite on the result of this one<br /> +RewriteRule ^(.+) ${lowercase:%{SERVER_NAME}}$1 [C]<br /> +<br /> +# now create the real file name<br /> +RewriteRule ^www\.([a-z-]+)\.isp\.com/(.*) /home/$1/$2<br /> +<br /> +# define the global CGI directory<br /> +ScriptAlias /cgi-bin/ /www/std-cgi/ +</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="xtra-conf" id="xtra-conf">Using a Separate Virtual + Host Configuration File</a></h2> + + <p>This arrangement uses more advanced <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> + features to work out the translation from virtual host to document + root, from a separate configuration file. This provides more + flexibility, but requires more complicated configuration.</p> + + <p>The <code>vhost.map</code> file should look something like + this:</p> + +<div class="example"><p><code> +www.customer-1.com /www/customers/1<br /> +www.customer-2.com /www/customers/2<br /> +# ...<br /> +www.customer-N.com /www/customers/N<br /> +</code></p></div> + + <p>The <code>httpd.conf</code> should contain the following:</p> + +<div class="example"><p><code> +RewriteEngine on<br /> +<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +# define the map file<br /> +RewriteMap vhost txt:/www/conf/vhost.map<br /> +<br /> +# deal with aliases as above<br /> +RewriteCond %{REQUEST_URI} !^/icons/<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$<br /> +# this does the file-based remap<br /> +RewriteCond ${vhost:%1} ^(/.*)$<br /> +RewriteRule ^/(.*)$ %1/docs/$1<br /> +<br /> +RewriteCond %{REQUEST_URI} ^/cgi-bin/<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$<br /> +RewriteCond ${vhost:%1} ^(/.*)$<br /> +RewriteRule ^/(.*)$ %1/cgi-bin/$1 [T=application/x-httpd-cgi] +</code></p></div> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/mass.html" title="English"> en </a> | +<a href="../ko/vhosts/mass.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/mass.html" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/mass.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/mass.html.ko.euc-kr new file mode 100644 index 00000000..060c69b1 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/mass.html.ko.euc-kr @@ -0,0 +1,425 @@ +<?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="./">ȣƮ</a></div><div id="page-content"><div id="preamble"><h1>뷮 ȣƮ ϱ</h1> +<div class="toplang"> +<p><span> : </span><a href="../en/vhosts/mass.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/mass.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/mass.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate"> ֽ ƴմϴ. + ֱٿ ϼ.</div> + + + <p> ġ 1.3 뷮 ȣƮ ȿ + ϴ Ѵ. + </p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#motivation"></a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#overview"></a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#simple"> ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#homepages"> ȣƮϴ Ȩ ý</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#combinations"> ȣƮ + ý ϱ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ipbased"> ȿ IP ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#oldversion">ġ ϱ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#simple.rewrite"><code>mod_rewrite</code> + ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#homepages.rewrite"><code>mod_rewrite</code> + Ȩ ý</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#xtra-conf"> ȣƮ + ϱ</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="motivation" id="motivation"></a></h2> + + <p> <code>httpd.conf</code> + <code><VirtualHost></code> ǵ ִٸ ⼭ + ϴ ̴:</p> + +<div class="example"><p><code> +NameVirtualHost 111.22.33.44<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.customer-1.com<br /> + DocumentRoot /www/hosts/www.customer-1.com/docs<br /> + ScriptAlias /cgi-bin/ /www/hosts/www.customer-1.com/cgi-bin<br /> +</span> +</VirtualHost><br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.customer-2.com<br /> + DocumentRoot /www/hosts/www.customer-2.com/docs<br /> + ScriptAlias /cgi-bin/ /www/hosts/www.customer-2.com/cgi-bin<br /> +</span> +</VirtualHost><br /> +# ٺ ٺ ٺ<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.customer-N.com<br /> + DocumentRoot /www/hosts/www.customer-N.com/docs<br /> + ScriptAlias /cgi-bin/ /www/hosts/www.customer-N.com/cgi-bin<br /> +</span> +</VirtualHost> +</code></p></div> + + <p>⺻ <code><VirtualHost></code> + θ óϵ üϴ ̴. + ִ:</p> + + <ol> + <li> ۾ ġ ϰ + Ѵ.</li> + + <li>ȣƮ ߰ϱ Ͻýۿ + 丮 DNS ߰ϱ⸸ ϸȴ. , + ġ 缳ϰ ʿ䰡 .</li> + </ol> + + <p> ȣƮ ٸ α ٴ + ̴. ſ ȣƮ Ѵٸ ϱڸ + ٸ α . + fifo α , α óϿ + ( ִ) .</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="overview" id="overview"></a></h2> + + <p>ȣƮ IP ּҿ HTTP û <code>Host:</code> + Ѵ. ⺻ 뷮 + ȣƮ ڵ ȣƮ û + ϰο Ѵ. ̴ κ <code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> + Ͽ ذ , ġ 1.3.6 ϸ Ѵٸ + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> ؾ Ѵ. + ⺻ Ե ʴ´. Ϸ + ġ ϰ Ҷ ؾ Ѵ.</p> + + <p> ȣƮ Ϲ ȣƮó ̰Ϸ + `ӿ' Ѵ. ߿ ġ ڱ + URL 鶧 ̴. + <code>ServerName</code> þ ϸ, CGI + <code>SERVER_NAME</code> ȯ溯 ־. + <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> ȴ. + <code>UseCanonicalName Off</code≯ û <code>Host:</code> + ȴ. <code>UseCanonicalName DNS</code≯ + ȣƮ IP ּҸ DNS ˻Ͽ ˾Ƴ. + ڴ ̸ ȣƮ ϰ, ڴ IP + ȣƮ Ѵ. <code>Host:</code> ų + DNS ˻ Ͽ ġ ˾Ƴ ϸ + <code>ServerName</code> Ѵ.</p> + + <p>ٸ `' (<code>DocumentRoot</code> ϸ, + CGI <code>DOCUMENT_ROOT</code> ȯ溯 ־) + Ʈ̴. Ϲ core Ͽ + URI شϴ ϸ ã, ȣ Ҷ ٸ + (<code>mod_vhost_alias</code> <code>mod_rewrite</code>) + ٸ ̷ ۾ Ѵ. + <code>DOCUMENT_ROOT</code> ȯ溯 Ƿ + CGI SSI Ѵٸ ߸ + ִ.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="simple" id="simple"> ȣƮ</a></h2> + + <p> <a href="#motivation"></a> ȣƮ + <code>mod_vhost_alias</code> Ͽ Ϲ + ߴ.</p> + +<div class="example"><p><code> +# Host: ˾Ƴ<br /> +UseCanonicalName Off<br /> +<br /> +# ù° ʵ带 Ͽ α ȣƮ ִ<br /> +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +# û óϱ ϸ Ѵ<br /> +VirtualDocumentRoot /www/hosts/%0/docs<br /> +VirtualScriptAlias /www/hosts/%0/cgi-bin +</code></p></div> + + <p> <code>UseCanonicalName Off</code> + <code>UseCanonicalName DNS</code> ϱ⸸ ϸ IP + ȣƮ ȴ. ȣƮ IP ּҸ + ϸ ߰ ִ.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="homepages" id="homepages"> ȣƮϴ Ȩ ý</a></h2> + + <p>ISP Ȩ ߴ. + ϸ <code>www.user.isp.com</code> + <code>/home/user/</code> δ Ϻθ + ϸ ִ. + <code>cgi-bin</code> ȣƮ ʰ + ȣƮ Ѵ.</p> + +<div class="example"><p><code> +# ⺻ . <br /> +<br /> +# ϸ Ϻθ Ѵ<br /> +VirtualDocumentRoot /www/hosts/%2/docs<br /> +<br /> +# ϳ cgi-bin 丮<br /> +ScriptAlias /cgi-bin/ /www/std-cgi/<br /> +</code></p></div> + + <p><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> + <code>VirtualDocumentRoot</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="combinations" id="combinations"> ȣƮ + ý ϱ</a></h2> + + <p> ġ Ϲ + <code><VirtualHost></code> þ Ͽ + ȣƮ ִ. , + Ȩ IP ּ Ѱ, + ٸ IP ּ Ѱ οѴ. ó + <code><VirtualHost></code> ǿ + ִ.</p> + +<div class="example"><p><code> +UseCanonicalName Off<br /> +<br /> +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon<br /> +<br /> +<Directory /www/commercial><br /> +<span class="indent"> + Options FollowSymLinks<br /> + AllowOverride All<br /> +</span> +</Directory><br /> +<br /> +<Directory /www/homepages><br /> +<span class="indent"> + Options FollowSymLinks<br /> + AllowOverride None<br /> +</span> +</Directory><br /> +<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName www.commercial.isp.com<br /> + <br /> + CustomLog logs/access_log.commercial vcommon<br /> + <br /> + VirtualDocumentRoot /www/commercial/%0/docs<br /> + VirtualScriptAlias /www/commercial/%0/cgi-bin<br /> +</span> +</VirtualHost><br /> +<br /> +<VirtualHost 111.22.33.45><br /> +<span class="indent"> + ServerName www.homepages.isp.com<br /> + <br /> + CustomLog logs/access_log.homepages vcommon<br /> + <br /> + VirtualDocumentRoot /www/homepages/%0/docs<br /> + ScriptAlias /cgi-bin/ /www/std-cgi/<br /> +</span> +</VirtualHost> +</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="ipbased" id="ipbased"> ȿ IP ȣƮ</a></h2> + + <p><a href="#simple">ù° </a> + IP ȣƮ ٲ ִٰ ߴ. + û DNS ãƾϹǷ ſ ȿ̴. + ̸ IP ּҷ Ͻý ϰ + α ϸ ذ ִ. ġ + ٷ ʿ䰡 , DNS ˻ ʰ ȴ.</p> + +<div class="example"><p><code> +# IP ּҸ DNS ˻Ͽ ˾Ƴ<br /> +UseCanonicalName DNS<br /> +<br /> +# α ֵ IP ּҸ Ѵ<br /> +LogFormat "%A %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +# ϸ IP ּҸ Ѵ<br /> +VirtualDocumentRootIP /www/hosts/%0/docs<br /> +VirtualScriptAliasIP /www/hosts/%0/cgi-bin<br /> +</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="oldversion" id="oldversion">ġ ϱ</a></h2> + + <p> ġ 1.3.6 Ŀ Ե + <code>mod_vhost_alias</code> Ѵ. + <code>mod_vhost_alias</code> ġ Ѵٸ + ̹ ߵ <code>mod_rewrite</code> Ͽ, + Host:- ȣƮ, ִ.</p> + + <p> α Ͽ ִ. ġ 1.3.6 + α þ <code>%V</code> ԵǾ, 1.3.0 + - 1.3.3 <code>%v</code> ɼ ߴ. + 1.3.4 ̷ . ġ + <code>.htaccess</code> Ͽ <code>UseCanonicalName</code> + þ Ƿ α ̻ ϵ ִ. + Ƿ <code>%{Host}i</code> þ + Ͽ <code>Host:</code> α ̴. + , <code>%V</code> ʴ <code>:port</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="simple.rewrite" id="simple.rewrite"><code>mod_rewrite</code> + ȣƮ</a></h2> + + <p> <a href="#simple">ù° </a> ϴ + <code>httpd.conf</code> ̴. ó ù° + , ȣȯ <code>mod_rewrite</code> + Ǿ. ۾ + ϴ <code>mod_rewrite</code> Ѵ.</p> + + <p>Ư ؾ ִ. ⺻ + <code>mod_rewrite</code> (<code>mod_alias</code> ) ٸ + URI ȴ. ٸ URI + Ͽ <code>mod_rewrite</code> ؾ Ѵ. + , ȣƮ <code>ScriptAlias</code> + ؼ Ư ۾ ʿϴ.</p> + +<div class="example"><p><code> +# Host: ´<br /> +UseCanonicalName Off<br /> +<br /> +# splittable logs<br /> +LogFormat "%{Host}i %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +<Directory /www/hosts><br /> +<span class="indent"> + # ScriptAlias CGI <br /> + # ExecCGI Ѵ<br /> + Options FollowSymLinks ExecCGI<br /> +</span> +</Directory><br /> +<br /> +# κ̴<br /> +<br /> +RewriteEngine On<br /> +<br /> +# Host: ҹڰ ڼ ִ<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +## Ϲ óѴ:<br /> +# Alias /icons/ ϵ - ٸ alias ؼ ݺ<br /> +RewriteCond %{REQUEST_URI} !^/icons/<br /> +# CGI ϵ<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +# Ư ۾<br /> +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/docs/$1<br /> +<br /> +## CGI óѴ - MIME type ؾ Ѵ<br /> +RewriteCond %{REQUEST_URI} ^/cgi-bin/<br /> +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 [T=application/x-httpd-cgi]<br /> +<br /> +# ! +</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="homepages.rewrite" id="homepages.rewrite"><code>mod_rewrite</code> + Ȩ ý</a></h2> + + <p> <a href="#homepages">ι° </a> + Ѵ.</p> + +<div class="example"><p><code> +RewriteEngine on<br /> +<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +# CGI ϵ<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +<br /> +# RewriteRule ϵ ȣƮ ùٸ ˻Ѵ<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.com$<br /> +<br /> +# ȣƮ URI տ δ<br /> +# [C] ۼ Ѵ<br /> +RewriteRule ^(.+) ${lowercase:%{SERVER_NAME}}$1 [C]<br /> +<br /> +# ϸ <br /> +RewriteRule ^www\.([a-z-]+)\.isp\.com/(.*) /home/$1/$2<br /> +<br /> +# ü CGI 丮 Ѵ<br /> +ScriptAlias /cgi-bin/ /www/std-cgi/ +</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="xtra-conf" id="xtra-conf"> ȣƮ + ϱ</a></h2> + + <p> <code>mod_rewrite</code> Ͽ + ȣƮ Ʈ ˾Ƴ. + ʿϴ.</p> + + <p><code>vhost.map</code> :</p> + +<div class="example"><p><code> +www.customer-1.com /www/customers/1<br /> +www.customer-2.com /www/customers/2<br /> +# ...<br /> +www.customer-N.com /www/customers/N<br /> +</code></p></div> + + <p><code>http.conf</code> :</p> + +<div class="example"><p><code> +RewriteEngine on<br /> +<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +# Ѵ<br /> +RewriteMap vhost txt:/www/conf/vhost.map<br /> +<br /> +# alias óѴ<br /> +RewriteCond %{REQUEST_URI} !^/icons/<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$<br /> +# ã´<br /> +RewriteCond ${vhost:%1} ^(/.*)$<br /> +RewriteRule ^/(.*)$ %1/docs/$1<br /> +<br /> +RewriteCond %{REQUEST_URI} ^/cgi-bin/<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$<br /> +RewriteCond ${vhost:%1} ^(/.*)$<br /> +RewriteRule ^/(.*)$ %1/cgi-bin/$1 +</code></p></div> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../en/vhosts/mass.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/mass.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/mass.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/apache2/manual/vhosts/mass.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/mass.html.tr.utf8 new file mode 100644 index 00000000..ff3f9990 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/mass.html.tr.utf8 @@ -0,0 +1,406 @@ +<?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>Devingen olarak Yapılandırılan Kitlesel Sanal Barındırma - 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="./">Sanal Konaklar</a></div><div id="page-content"><div id="preamble"><h1>Devingen olarak Yapılandırılan Kitlesel Sanal Barındırma</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/mass.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/mass.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/mass.html" title="Türkçe"> tr </a></p> +</div> + + + <p>Bu belgede sanal konakların sonu belirsiz bir şekilde artışı karşısında + Apache httpd sunucusunun nasıl daha verimli kullanılacağı açıklanmıştır. + </p> + +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#motivation">Amaç</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#overview">Genel Bakış</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#simple">Basit Devingen Sanal Konaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#homepages">Sanal Kişisel Sayfalar Sistemi</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#combinations">Aynı Sunucuda Kişisel ve Kurumsal Sanal Konaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#ipbased">IP’ye dayalı sanal konakları daha verimli kılmak</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#simple.rewrite"><code>mod_rewrite</code> ile Kurumsal Müşteriler Sistemi</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#homepages.rewrite"><code>mod_rewrite</code> ile Kişisel Sayfalar Sistemi</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#xtra-conf">Sanal konaklar için ayrı bir yapılandırma dosyası kullanmak</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="motivation" id="motivation">Amaç</a></h2> + + <p>Burada açıklanan teknikler, <code>httpd.conf</code> dosyanızın + örnekteki gibi, aslında hemen hemen birbirinin aynı çok sayıda + <code><VirtualHost></code> bölümü içereceği zaman yapılacaklar ile + ilgilidir.</p> + +<div class="example"><p><code> +NameVirtualHost 111.22.33.44<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName musteri-1.dom<br /> + DocumentRoot /siteler/musteri-1.dom/belgeler<br /> + ScriptAlias /cgi-bin/ /siteler/musteri-1.dom/cgi-bin<br /> +</span> +</VirtualHost><br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName musteri-2.dom<br /> + DocumentRoot /siteler/musteri-2.dom/belgeler<br /> + ScriptAlias /cgi-bin/ /siteler/musteri-2.dom/cgi-bin<br /> +</span> +</VirtualHost><br /> +# blah blah blah<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName musteri-N.dom<br /> + DocumentRoot /siteler/musteri-N.dom/belgeler<br /> + ScriptAlias /cgi-bin/ /siteler/musteri-N.dom/cgi-bin<br /> +</span> +</VirtualHost> +</code></p></div> + + <p>Ana fikir, tüm durağan <code><VirtualHost></code> + yapılandırmalarını devingen olarak çalışan tek bir + <code><VirtualHost></code> bölümüyle değiştirmektir. Bunun elbette + bazı getirileri olacaktır:</p> + + <ol> + <li>Yapılandırma dosyanız küçüleceği için Apache daha çabuk + başlatılabilecek ve daha az bellek harcayacaktır.</li> + + <li>Yeni sanal konakların eklenmesi, DNS’de yeni girdiler oluşturmak ve + dosya sisteminde bununla ilgili dizinleri açmak dışında biraz daha + basit olacaktır; en azından Apache’yi yeniden yapılandırmak ve yeniden + başlatmak zorunda kalmayacaksınız.</li> + </ol> + + <p>Ana götürüsü ise her sanal konak için ayrı birer günlük dosyasına sahip + olamayacak olmanızdır. Öte yandan, dosya tanıtıcılarının sınırlı olması + nedeniyle bunu yapmayı zaten istemezsiniz. Günlük kayıtları için bir + fifo veya bir boru hattı oluşturmak ve diğer uçta çalışan bir süreç + vasıtasıyla günlükleri müşterilere paylaştırmak daha iyidir (ayrıca, bu, + istatistikleri toplamanızı da kolaylaştırı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="overview" id="overview">Genel Bakış</a></h2> + + <p>Bir sanal konak iki bilgiye bakarak belirlenir: IP adresi ve HTTP + isteğindeki <code>Host:</code> başlığının içeriği. Devingen sanal + barındırma tekniği, isteği yerine getirmek için kullanılacak dosya + yoluna bu bilgiyi kendiliğinden girmek esasına dayanır. Bu, Apache 2.0 + ile <code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> kullanarak oldukça kolay + yapılabileceği gibi <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> da kullanılabilir. Bu + modüllerin her ikisi de öntanımlı olarak devre dışıdır. Bu tekniği + kullanmak isterseniz Apache’yi yeniden yapılandırıp derleyerek bu iki + modülü etkin duruma getirmeniz gerekir.</p> + + <p>Devingen sanal konağı normal bir sanal konak gibi göstermek için bazı + şeyleri ’göstermelik’ olarak yapmak gerekir. Bunlardan en önemlisi, + Apache tarafından göreli URL’lerden normal URL’leri ve benzerlerini + üretmek için kullanılan sunucu ismidir. Sunucu ismi + <code>ServerName</code> yönergesi ile yapılandırılır ve CGI’ler + tarafından <code>SERVER_NAME</code> ortam değişkeni üzerinden + kullanılır. Çalışma anındaki asıl değer <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> yönergesi tarafından denetlenir. + <code>UseCanonicalName Off</code> olduğunda sunucu ismi isteğin + <code>Host:</code> başlık alanından elde edilir. <code>UseCanonicalName + DNS</code> belirtilmişse, sunucu ismi, sanal konağın IP adresinden + tersine DNS sorgusu yapılarak elde edilir. Birincisi isme dayalı sanal + konaklar tarafından ikincisi ise IP’ye dayalı sanal konaklar tarafından + kullanılır. Eğer Apache, istekte <code>Host:</code> başlığının olmayışı + veya DNS sorgusunun başarısız olması sebebiyle sunucu ismini elde + edemezse son çare olarak <code>ServerName</code> yönergesinde yazılı + değeri kullanır.</p> + + <p>‘Göstermelik’ yapılan şeylerden biri de <code>DocumentRoot</code> + yönergesi ile yapılandırılan belge kök dizini olup CGI’ler tarafından + <code>DOCUMENT_ROOT</code> ortam değişkeni üzerinden kullanılır. Normal + yapılandırmada <code class="module"><a href="../mod/core.html">core</a></code> modülü tarafından dosya isimlerini + URI’lere eşlerken kullanılır. Fakat sunucu devingen sanal konakları + kullanmak üzere yapılandırıldığında, eşleştirmeyi farklı yollardan yapan + başka bir modül devreye girer (<code>mod_vhost_alias</code> veya + <code>mod_rewrite</code>). <code>DOCUMENT_ROOT</code> ortam değişkenine + değerini atamaktan sorumlu olan bu iki modülden biri kullanılmazsa CGI + veya SSI belgeleri yanlış değerlerle üretilirler.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="simple" id="simple">Basit Devingen Sanal Konaklar</a></h2> + + <p>Yukarıda <a href="#motivation">Amaç</a> bölümünde özetlenen sanal konak + düzenlemesinin <code>mod_vhost_alias</code> kullanarak daha soysal bir + tarzda gerçekleştirilmiş halini içeren <code>httpd.conf</code> bölümü + aşağıdadır.</p> + +<div class="example"><p><code> +# sunucu ismini Host: başlığından elde edelim<br /> +UseCanonicalName Off<br /> +<br /> +# Bu günlükleme biçiminde ilk alana bakarak<br /> +# sanal konak günlükleri ayrıştırılabilir<br /> +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +# istekleri yerine getirmek için kullanılacak<br /> +# dosya isimlerine sunucu ismini ekleyelim<br /> +VirtualDocumentRoot /siteler/%0/belgeler<br /> +VirtualScriptAlias /siteler/%0/cgi-bin +</code></p></div> + + <p>Bu yapılandırmayı IP’ye dayalı sanal konaklar için kullanmak isterseniz + <code>UseCanonicalName Off</code> yerine <code>UseCanonicalName + DNS</code> yazmanız yeterlidir. Böylece dosya ismine eklenecek konak + ismi sanal konağın IP adresinden türetilir.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="homepages" id="homepages">Sanal Kişisel Sayfalar Sistemi</a></h2> + + <p>Bu sistem, yukarıdaki yapılandırmanın bir ISS’nin kişisel sayfalar + sunucusuna uyarlanmasından başka bir şey değildir. Biraz daha karmaşık + bir yapılandırma ile dosya isimlerine <code>/home/kullanıcı/</code> + dizinlerini ekleyebiliriz. Farklı olarak her sanal konak için bir tane + değil hepsi için bir tane <code>cgi-bin</code> olacaktır.</p> + +<div class="example"><p><code> +# Son bölüm hariç yukarıdaki yapılandırma, burada...<br /> +<br /> +# sunucu ismine eklenecek dosya isimlerini oluşturalım<br /> +VirtualDocumentRoot /siteler/%2/belgeler<br /> +<br /> +# ortak cgi-bin dizini<br /> +ScriptAlias /cgi-bin/ /siteler/std-cgi/<br /> +</code></p></div> + + <p><code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> belgesinde daha karmaşık + <code>VirtualDocumentRoot</code> örnekleri vardı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="combinations" id="combinations">Aynı Sunucuda Kişisel ve Kurumsal Sanal Konaklar</a></h2> + + <p>Daha karmaşık ayarlamalar yaparak Apache’inin normal + <code><VirtualHost></code> bölümlerini farklı kitlesel sanal konak + yapılandırmaları için kullanabilirsiniz. Örneğin, bireysel + müşterileriniz için bir IP adresiniz, kurumsal müşterileriniz için de + başka bir IP adresiniz olsun. Her biri için ayrı ayrı sanal konaklar + ayarlamak yerine aşağıdaki gibi bir yapılandırma kullanabilirsiniz:</p> + +<div class="example"><p><code> +UseCanonicalName Off<br /> +<br /> +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon<br /> +<br /> +<Directory /siteler/kurumsal><br /> +<span class="indent"> + Options FollowSymLinks<br /> + AllowOverride All<br /> +</span> +</Directory><br /> +<br /> +<Directory /siteler/bireysel><br /> +<span class="indent"> + Options FollowSymLinks<br /> + AllowOverride None<br /> +</span> +</Directory><br /> +<br /> +<VirtualHost 111.22.33.44><br /> +<span class="indent"> + ServerName kurumsal.iss.dom<br /> + <br /> + CustomLog logs/access_log.kurumsal vcommon<br /> + <br /> + VirtualDocumentRoot /siteler/kurumsal/%0/belgeler<br /> + VirtualScriptAlias /siteler/kurumsal/%0/cgi-bin<br /> +</span> +</VirtualHost><br /> +<br /> +<VirtualHost 111.22.33.45><br /> +<span class="indent"> + ServerName bireysel.iss.dom<br /> + <br /> + CustomLog logs/access_log.bireysel vcommon<br /> + <br /> + VirtualDocumentRoot /siteler/bireysel/%0/belgeler<br /> + ScriptAlias /cgi-bin/ /siteler/std-cgi/<br /> +</span> +</VirtualHost> +</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="ipbased" id="ipbased">IP’ye dayalı sanal konakları daha verimli kılmak</a></h2> + + <p><a href="#simple">İlk örnekte</a> IP’ye dayalı sanal konaklar için + kullanılmak istenirse yapılandırmada neyin nasıl değiştirileceği + belirtilmişti. Her istek için ayrı bir DNS sorgusu gerekeceğinden bu + başarım düşmesine yol açar. DNS sorgusu ihtiyacını ortadan kaldırmak + için, bir çözüm olarak dosya sistemi, konak isimleri yerine IP + adreslerine göre düzenlenebilir. Günlük kayıtları da IP adreslerine göre + ayrıştırılacak şekilde ayarlanabilir.</p> + +<div class="example"><p><code> +# Sunucu ismini IP adresinden ters DNS sorgusu ile elde edelim<br /> +UseCanonicalName DNS<br /> +<br /> +# Günlük kayıtları IP adreslerine göre ayrıştırılabilsin<br /> +LogFormat "%A %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +# dosya isimleri IP adreslerini içersin<br /> +VirtualDocumentRootIP /siteler/%0/belgeler<br /> +VirtualScriptAliasIP /siteler/%0/cgi-bin<br /> +</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="simple.rewrite" id="simple.rewrite"><code>mod_rewrite</code> ile Kurumsal Müşteriler Sistemi</a></h2> + + <p>Buradaki <code>httpd.conf</code> bölümü de <a href="#simple">ilk + örnekteki</a> gibi elde edilmiştir. İlk yarı, bazı değişiklikler dışında + yukarıdaki örneğe çok benzer. Bu değişiklikler yapılandırmanın + <code>mod_rewrite</code> bölümünün düzgün çalışması ve geriye doğru + uyumluluk için gereklidir. İkinci yarı, asıl işi yapan + <code>mod_rewrite</code> yapılandırmasını içerir.</p> + + <p>Biraz uzmanlık gerektiren bazı kısımlar var: Öntanımlı olarak + <code>mod_rewrite</code> diğer (<code>mod_alias</code>, vs. gibi) URI + dönüşüm modüllerinden önce çalışır. Dolayısıyla bu modülleri kullanmak + isterseniz, <code>mod_rewrite</code>’ı bunlara izin verecek şekilde + yapılandırmalısınız. Ayrıca her devingen sanal konağa eşdeğer bir + <code>ScriptAlias</code> yapmak için de biraz büyü yapmak gerekir.</p> + +<div class="example"><p><code> +# Sunucu ismini Host: başlığınıdan alalım.<br /> +UseCanonicalName Off<br /> +<br /> +# Günlük dosyasından bilgileri ayıklayabilelim.<br /> +LogFormat "%{Host}i %h %l %u %t \"%r\" %s %b" vcommon<br /> +CustomLog logs/access_log vcommon<br /> +<br /> +<Directory /siteler/hosts><br /> +<span class="indent"> + # ScriptAlias için yaptıklarımızla CGI betiklerini<br /> + # çalışmaya zorlayamayacağımızdan ExecCGI burada gerekli.<br /> + Options FollowSymLinks ExecCGI<br /> +</span> +</Directory><br /> +<br /> +# İşin zor yanına geldik.<br /> +<br /> +RewriteEngine On<br /> +<br /> +# Host: başlığından elde edilen sunucu isminde harf<br /> +# büyüklükleri çeşitli olabilir. Hepsini küçük harf yapalım.<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +## önce normal belgelerle anlaşalım:<br /> +# Alias /icons/ çalışsın - diğer rumuzlar için yineleyelim<br /> +RewriteCond %{REQUEST_URI} !^/icons/<br /> +# CGI’ler de çalışsın.<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +# Biraz da büyü yapalım.<br /> +RewriteRule ^/(.*)$ /siteler/${lowercase:%{SERVER_NAME}}/belgeler/$1<br /> +<br /> +## Artık CGI’lerle anlaşabiliriz. - Bir MIME türü isteyelim.<br /> +RewriteCond %{REQUEST_URI} ^/cgi-bin/<br /> +RewriteRule ^/(.*)$ /siteler/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 [T=application/x-httpd-cgi]<br /> +<br /> +# Bu kadar! +</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="homepages.rewrite" id="homepages.rewrite"><code>mod_rewrite</code> ile Kişisel Sayfalar Sistemi</a></h2> + + <p>Burada da <a href="#homepages">ikinci örnekte</a> yaptıklarımızı + yapıyoruz.</p> + +<div class="example"><p><code> +RewriteEngine on<br /> +<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +# CGI’ler çalışsın.<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +<br /> +# konak ismi doğru mu bakalım yoksa RewriteRule çalışmaz.<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.dom$<br /> +<br /> +# URI’nin başına sanal konak ismini ekleyelim.<br /> +# [C], bunu bitirdikten sonra, sonraki rewrite ile devam et demek.<br /> +RewriteRule ^(.+) ${lowercase:%{SERVER_NAME}}$1 [C]<br /> +<br /> +# Artık asıl dosya ismini oluşturabiliriz.<br /> +RewriteRule ^www\.([a-z-]+)\.isp\.dom/(.*) /home/$1/$2<br /> +<br /> +# Ortak CGI dizinini tanımlayalım.<br /> +ScriptAlias /cgi-bin/ /siteler/std-cgi/ +</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="xtra-conf" id="xtra-conf">Sanal konaklar için ayrı bir yapılandırma dosyası kullanmak</a></h2> + + <p>Burada, sanal konak isimlerinden belge kök dizini elde ederken + <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> modülünün daha gelişkin özelliklerinden + yararlanarak isimleri ayrı bir dosyadan okutacağız. Bu, esnekliği + artırır ama daha karmaşık bir yapılandırma gerekir.</p> + + <p>Aşağıdaki içeriğe sahip bir <code>vhost.map</code>dosyamız olsun:</p> + +<div class="example"><p><code> +musteri-1.dom /siteler/kurumsal/1<br /> +musteri-2.dom /siteler/kurumsal/2<br /> +# ...<br /> +musteri-N.dom /siteler/kurumsal/N<br /> +</code></p></div> + + <p><code>httpd.conf</code> dosyamız da şunları içerecektir:</p> + +<div class="example"><p><code> +RewriteEngine on<br /> +<br /> +RewriteMap lowercase int:tolower<br /> +<br /> +# Eşlem dosyasını tanımlayalım<br /> +RewriteMap vhost txt:/siteler/conf/vhost.map<br /> +<br /> +# Rumuzları yukarıdaki gibi halledelim.<br /> +RewriteCond %{REQUEST_URI} !^/icons/<br /> +RewriteCond %{REQUEST_URI} !^/cgi-bin/<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$<br /> +# Eşlemeyi dosyalar için de yapalım.<br /> +RewriteCond ${vhost:%1} ^(/.*)$<br /> +RewriteRule ^/(.*)$ %1/belgeler/$1<br /> +<br /> +RewriteCond %{REQUEST_URI} ^/cgi-bin/<br /> +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$<br /> +RewriteCond ${vhost:%1} ^(/.*)$<br /> +RewriteRule ^/(.*)$ %1/cgi-bin/$1 +</code></p></div> + +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../en/vhosts/mass.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/vhosts/mass.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/mass.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/apache2/manual/vhosts/name-based.html b/rubbos/app/apache2/manual/vhosts/name-based.html new file mode 100644 index 00000000..10fcbf0e --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html @@ -0,0 +1,25 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: name-based.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: name-based.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: name-based.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: name-based.html.ja.utf8 +Content-Language: ja +Content-type: text/html; charset=UTF-8 + +URI: name-based.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: name-based.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/rubbos/app/apache2/manual/vhosts/name-based.html.de b/rubbos/app/apache2/manual/vhosts/name-based.html.de new file mode 100644 index 00000000..2799aa23 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html.de @@ -0,0 +1,270 @@ +<?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="de" xml:lang="de"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Untersttzung namensbasierter virtueller Hosts - 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/">Module</a> | <a href="../mod/directives.html">Direktiven</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossar</a> | <a href="../sitemap.html">Seitenindex</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/">Dokumentation</a> > <a href="../">Version 2.0</a> > <a href="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>Untersttzung namensbasierter virtueller Hosts</h1> +<div class="toplang"> +<p><span>Verfgbare Sprachen: </span><a href="../de/vhosts/name-based.html" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + <p>Das Dokument beschreibt, wann und wie namensbasierte virtuelle Hosts zu + verwenden sind.</p> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip">Namensbasierte gegenber IP-basierten + virtuellen Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#using">Die Verwendung von namensbasierten virtuellen Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compat">Kompatibilitt mit lteren Browsern</a></li> +</ul><h3>Siehe auch</h3><ul class="seealso"><li><a href="ip-based.html">Untersttzung IP-basierter virtueller + Hosts</a></li><li><a href="details.html">Tiefergehende Errterung der Zuweisung + virtueller Hosts</a></li><li><a href="mass.html">Dynamisch konfiguriertes + Massen-Virtual-Hosting</a></li><li><a href="examples.html">Beispiele fr virtuelle Hosts in typischen + Installationen</a></li><li><a href="examples.html#serverpath">ServerPath-Beispielkonfiguration</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="namevip" id="namevip">Namensbasierte gegenber IP-basierten + virtuellen Hosts</a></h2> + + <p>IP-basierte virtuelle Hosts verwenden die IP-Adresse der Verbindung, um den + korrekten virtuellen Host zur Bedienung einer Anfrage zu ermitteln. Folglich + bentigen Sie eine IP-Adresse fr jeden virtuellen Host. Bei der + Verwendung von namensbasierten virtuellen Hosts verlt sich der + Server darauf, dass der Client den Hostnamen als Bestandteil der HTTP-Header + angibt. Durch Anwendung dieser Technik knnen sich mehrere verschiedene + Hosts die gleiche IP-Adresse teilen.</p> + + <p>Die Verwendung von namensbasierten virtuellen Hosts ist gewhnlich + einfacher. Sie mssen lediglich Ihren DNS-Server darauf einstellen, + jeden Hostnamen auf die richtige IP-Adresse abzubilden, und dann den Apache + HTTP Server so konfigurieren, dass er die verschiedenen Hostnamen erkennt. + Namensbasierte virtuelle Hosts entschrfen auch den Bedarf an + knappen IP-Adressen. Daher sollten Sie namensbasierte virtuelle Hosts + verwenden, sofern kein besonderer Grund dafr existiert, IP-basierte + virtuelle Hosts zu whlen. Mgliche Grnde fr die + Verwendung IP-basierter virtueller Hosts sind:</p> + + <ul> + <li>Einige antike Clients sind nicht kompatibel zu namensbasierten + virtuellen Hosts. Damit namensbasierte virtuelle Hosts funktionieren, + muss der Client den HTTP-Host-Header senden. Dies ist bei HTTP/1.1 + vorgeschrieben und in allen modernen HTTP/1.0-Browsern als Erweiterung + implementiert. Wenn Sie Untersttzung fr veraltete Clients + bentigen und dennoch namensbasierte virtuelle Hosts verwenden, + dann finden Sie eine mgliche Lsung dafr am Ende des + Dokuments.</li> + + <li>Namensbasierte virtuelle Hosts knnen aufgrund der Natur des + SSL-Protokolls nicht mit SSL-gesicherten Servern verwendet werden.</li> + + <li>Einige Betriebssysteme und Netzwerkanlagen setzen Techniken zum + Bandbreiten-Management ein, die nicht zwischen Hosts unterscheiden + knnen, wenn diese nicht auf verschiedenen IP-Adressen liegen.</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="using" id="using">Die Verwendung von namensbasierten virtuellen Hosts</a></h2> + + <table class="related"><tr><th>Referenzierte Module</th><th>Referenzierte Direktiven</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table> + + <p>Um namensbasierte virtuelle Hosts zu verwenden, mssen Sie die + IP-Adresse (und mglicherweise den Port) des Servers benennen, an + der Anfragen fr die Hosts entgegengenommen werden. Dies wird mit + der Direktive <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + eingestellt. Im Normalfall, wenn alle IP-Adressen des Server verwendet + werden sollen, knnen Sie <code>*</code> als Argument fr + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> verwenden. Wenn Sie + vorhaben, mehrere Ports zu nutzen (etwa wenn SSL luft), sollten + Sie dem Argument einen Port hinzufgen, wie zum Beispiel + <code>*:80</code>. Beachten Sie, + dass die Angabe einer IP-Adresse in einer <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>-Anweisung den Server nicht + automatisch an dieser Adresse lauschen lt. Lesen Sie bitte "<a href="../bind.html">Bestimmen der vom Apache verwendeten Adressen und + Ports</a>" fr weitere Details. Zustzlich muss jede hier + angegebene IP-Adresse einer Netzwerkkarte des Servers zugeordnet sein.</p> + + <p>Der nchste Schritt ist die Erstellung eines <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Blocks fr jeden einzelnen + Host, den Sie bedienen wollen. Das Argument der Direktive <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> sollte das gleiche + sein wie das Argument der <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>-Anweisung (d.h. eine IP-Adresse + oder <code>*</code> fr alle Adressen). Innerhalb jedes <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Blocks bentigen + Sie zumindestens eine <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>-Anweisung, um zu bestimmen, welcher + Host bedient wird, und eine <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-Anweisung, um anzugeben, wo im + Dateisystem der Inhalt des Hosts abgelegt ist.</p> + + <div class="note"><h3>Der Hauptserver verschwindet</h3> + Wenn Sie virtuelle Hosts zu einem bestehenden Webserver hinzufgen, + mssen Sie auch einen <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Block fr den bestehenden Host + <span class="transnote">(<em>Anm.d..:</em> und bisherigen Hauptserver)</span> erstellen. + Die <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>- und + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-Anweisungen zu diesem + virtuellen Host sollten die gleichen sein wie die globalen <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>- und <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-Anweisungen. Fhren Sie diesen + virtuellen Host als erstes in der Konfigurationsdatei auf, so dass er als + Standard-Host fungiert. + </div> + + <p>Vorausgesetzt, Sie bedienen z.B. die Domain + <code>www.domain.tld</code> und mchten den virtuellen Host + <code>www.otherdomain.tld</code> hinzufgen, welcher auf + die gleiche IP-Adresse zeigt. Dann fgen Sie einfach Folgendes der + <code>httpd.conf</code> hinzu:</p> + + <div class="example"><p><code> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerAlias domain.tld *.domain.tld<br /> + DocumentRoot /www/domain<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent">ServerName www.otherdomain.tld<br /> + DocumentRoot /www/otherdomain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>Sie knnen anstelle des <code>*</code> bei den beiden Anweisungen + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> und <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> alternativ eine + eindeutige IP-Adresse angeben. Das kann man beispielsweise machen, um + einige namensbasierte virtuelle Hosts auf einer IP-Adresse zu betreiben und + entweder IP-basierte oder ein anderes Set von namensbasierten virtuellen + Hosts auf einer anderen Adresse.</p> + + <p>Viele Server wollen unter mehr als einem Namen erreichbar sein. Die + Direktive <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code>, die innerhalb + des <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Abschnittes angegeben wird, + ermglicht dies. Zum Beispiel zeigt die <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code>-Anweisung in dem ersten <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Block oben an, dass die + aufgefhrten Namen alternative Namen sind, die man verwenden kann, um + das gleiche Webangebot zu erreichen:</p> + + <div class="example"><p><code> + ServerAlias domain.tld *.domain.tld + </code></p></div> + + <p>Anfragen fr alle Hosts der Domain <code>domain.tld</code> werden + von dem virtuellen Host <code>www.domain.tld</code> bedient. Die + Platzhalter <code>*</code> und <code>?</code> knnen anstelle + entsprechender Namen verwendet werden. Natrlich knnen Sie nicht + einfach Namen erfinden und diese bei <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> oder <code>ServerAlias</code> + angeben, Sie mssen zunchst Ihren DNS Server entsprechend + konfigurieren, dass er diese Namen auf die mit Ihrem Server verknpfte + IP-Adresse abbildet.</p> + + <p>Und schluendlich knnen Sie die Konfiguration der virtuellen + Hosts mittels Angabe weiterer Direktiven innherhalb der <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Container + feineinstellen. Die meisten Direktiven knnen in diesen Containern + angegeben werden und verndern dann ausschlielich die + Konfiguration des entsprechenden virtuellen Hosts. Prfen Sie den <a href="../mod/directive-dict.html#Context">Kontext</a> einer Direktive, um + herauszufinden, ob eine bestimmte Direktive zulssig ist. + Im <em>Hauptserver-Kontext</em> (auerhalb der <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Container) definierte + Konfigurationsanweisungen werden nur dann angewendet, wenn sie nicht durch + Einstellungen des virtuellen Hosts auer Kraft gesetzt wurden.</p> + + <p>Wenn nun eine Anfrage eintrifft, prft der Server zuerst, ob sie eine + IP-Adresse verwendet, die der <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>-Anweisung entspricht. Ist dies der + Fall, dann sieht er sich jeden <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Abschnitt mit einer passenden + IP-Adresse an und versucht den einen zu finden, dessen <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>- oder <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code>-Anweisung mit dem gewnschten + Hostnamen bereinstimmt. Findet er einen, dann verwendet er die + Konfiguration dieses Servers. Wird kein passender virtueller Host gefunden, + dann wird <strong>der erste angegeben virtuelle Host</strong> verwendet, + dessen IP-Adresse pat.</p> + + <p>Die Folge davon ist, dass der erste aufgefhrte virtuelle Host der + <em>Standard</em>-Virtual-Host ist. Die <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-Anweisung des <em>Hauptservers</em> + wird <strong>niemals</strong> verwendet, wenn eine IP-Adresse mit einer + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>-Anweisung + bereinstimmt. Wenn Sie eine spezielle Konfiguration fr Anfragen + angeben mchten, die keinem bestimmten virtuellen Host entsprechen, + packen Sie diese Konfiguration einfach in einen <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>-Container und fhren diesen als + erstes in der Konfigurationsdatei auf.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="compat" id="compat">Kompatibilitt mit lteren Browsern</a></h2> + + <p>Wie zuvor erwhnt gibt es einige Clients, die nicht die notwendigen + Daten senden, mit denen namensbasierte virtuelle Hosts korrekt + funktionieren. Diesen Clients werden stets die Seiten des ersten, fr + diese IP-Adresse aufgefhrten virtuellen Hosts gesendet werden (des + <cite>primren</cite> namensbasierten virtuellen Hosts).</p> + + <div class="note"><h3>Was bedeutet lter?</h3> + <p>Beachten Sie bitte, wenn wir von lter sprechen, meinen wir auch + lter. Es ist sehr unwahrscheinlich, dass sie einen dieser Browser + heutzutage in Verwendung finden werden. Alle aktuellen Browser-Versionen + senden den <code>Host</code>-Header, so wie er fr namensbasierte + virtuelle Hosts bentigt wird.</p> + </div> + + <p>Mit der Direktive <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> existiert + eine mgliche Behelfskonstruktion, obgleich sie etwas schwerfllig + ist:</p> + + <p>Beispielkonfiguration:</p> + + <div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <br /> + <VirtualHost 111.22.33.44><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerPath /domain<br /> + DocumentRoot /web/domain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>Was bedeutet das? Es bedeutet, dass eine Anfrage fr eine mit + "<code>/domain</code>" beginnende URI von dem virtuellen Host + <code>www.domain.tld</code> bedient wird. Dies heit, dass die Seiten + fr alle Clients unter <code>http://www.domain.tld/domain/</code> + abrufbar sind, wenngleich Clients, die den Header <code>Host:</code> + senden, auch ber <code>http://www.domain.tld/</code> auf sie zugreifen + knnen.</p> + + <p>Legen Sie einen Link auf der Seite Ihres primren virtuellen Hosts zu + <code>http://www.domain.tld/domain/</code>, um die Behelfslsung + verfgbar zu machen. Bei den Seiten der virtuellen Hosts mssen + Sie dann sicherstellen, entweder auschlielich relative Links + (<em>z.B.</em> "<code>file.html</code>" oder + "<code>../icons/image.gif</code>") zu verwenden oder Links, die das + einleitende <code>/domain/</code> enthalten (<em>z.B.</em>, + "<code>http://www.domain.tld/domain/misc/file.html</code>" oder + "<code>/domain/misc/file.html</code>").</p> + + <p>Dies erfordert etwas Disziplin, die Befolgung dieser Richtlinien stellt + jedoch grtenteils sicher, dass Ihre Seiten mit allen Browsern + funktionieren, alten wie neuen.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Verfgbare Sprachen: </span><a href="../de/vhosts/name-based.html" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Lizenziert unter der <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Module</a> | <a href="../mod/directives.html">Direktiven</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossar</a> | <a href="../sitemap.html">Seitenindex</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/apache2/manual/vhosts/name-based.html.en b/rubbos/app/apache2/manual/vhosts/name-based.html.en new file mode 100644 index 00000000..837739a0 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html.en @@ -0,0 +1,248 @@ +<?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>Name-based Virtual Host Support - 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="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>Name-based Virtual Host Support</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + <p>This document describes when and how to use name-based virtual hosts.</p> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip">Name-based vs. IP-based Virtual Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#using">Using Name-based Virtual Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compat">Compatibility with Older Browsers</a></li> +</ul><h3>See also</h3><ul class="seealso"><li><a href="ip-based.html">IP-based Virtual Host Support</a></li><li><a href="details.html">An In-Depth Discussion of Virtual Host Matching</a></li><li><a href="mass.html">Dynamically configured mass virtual hosting</a></li><li><a href="examples.html">Virtual Host examples for common setups</a></li><li><a href="examples.html#serverpath">ServerPath configuration 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="namevip" id="namevip">Name-based vs. IP-based Virtual Hosts</a></h2> + + <p>IP-based virtual hosts use the IP address of the connection to + determine the correct virtual host to serve. Therefore you need to + have a separate IP address for each host. With name-based virtual + hosting, the server relies on the client to report the hostname as + part of the HTTP headers. Using this technique, many different hosts + can share the same IP address.</p> + + <p>Name-based virtual hosting is usually simpler, since you need + only configure your DNS server to map each hostname to the correct + IP address and then configure the Apache HTTP Server to recognize + the different hostnames. Name-based virtual hosting also eases + the demand for scarce IP addresses. Therefore you should use + name-based virtual hosting unless there is a specific reason to + choose IP-based virtual hosting. Some reasons why you might consider + using IP-based virtual hosting:</p> + + <ul> + <li>Some ancient clients are not compatible with name-based virtual + hosting. For name-based virtual hosting to work, the client must send + the HTTP Host header. This is required by HTTP/1.1, and is + implemented by all modern HTTP/1.0 browsers as an extension. If you + need to support obsolete clients and still use name-based virtual + hosting, a possible technique is discussed at the end of this + document.</li> + + <li>Name-based virtual hosting cannot be used with SSL secure servers + because of the nature of the SSL protocol.</li> + + <li>Some operating systems and network equipment implement bandwidth + management techniques that cannot differentiate between hosts unless + they are on separate IP addresses.</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="using" id="using">Using Name-based Virtual Hosts</a></h2> + +<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table> + + <p>To use name-based virtual hosting, you must designate the IP + address (and possibly port) on the server that will be accepting + requests for the hosts. This is configured using the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive. + In the normal case where any and all IP addresses on the server should + be used, you can use <code>*</code> as the argument to <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. If you're planning to use + multiple ports (e.g. running SSL) you should add a Port to the argument, + such as <code>*:80</code>. Note that mentioning an IP address in a + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive does not + automatically make the server listen to that IP address. See + <a href="../bind.html">Setting which addresses and ports Apache uses</a> + for more details. In addition, any IP address specified here must be + associated with a network interface on the server.</p> + + <p>The next step is to create a <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block for + each different host that you would like to serve. The argument to the + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> directive + should be the same as the argument to the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive (ie, an IP address, + or <code>*</code> for all addresses). Inside each <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block, you will need at minimum a + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> directive to designate + which host is served and a <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + directive to show where in the filesystem the content for that host + lives.</p> + + <div class="note"><h3>Main host goes away</h3> + <p>If you are adding virtual hosts to an existing web server, you + must also create a <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block for the existing host. The <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> and <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> included in this virtual host should be the + same as the global <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> and + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>. List this virtual + host first in the configuration file so that it will act as the default + host.</p> + </div> + + <p>For example, suppose that you are serving the domain + <code>www.domain.tld</code> and you wish to add the virtual host + <code>www.otherdomain.tld</code>, which points at the same IP address. + Then you simply add the following to <code>httpd.conf</code>:</p> + + <div class="example"><p><code> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerAlias domain.tld *.domain.tld<br /> + DocumentRoot /www/domain<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent">ServerName www.otherdomain.tld<br /> + DocumentRoot /www/otherdomain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>You can alternatively specify an explicit IP address in place of the + <code>*</code> in both the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> and <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> directives. For example, you might want to do this + in order to run some name-based virtual hosts on one IP address, and either + IP-based, or another set of name-based virtual hosts on another address.</p> + + <p>Many servers want to be accessible by more than one name. This is + possible with the <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> + directive, placed inside the <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> section. For example in the first <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block above, the + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> directive indicates that + the listed names are other names which people can use to see that same + web site:</p> + + <div class="example"><p><code> + ServerAlias domain.tld *.domain.tld + </code></p></div> + + <p>then requests for all hosts in the <code>domain.tld</code> domain will + be served by the <code>www.domain.tld</code> virtual host. The wildcard + characters <code>*</code> and <code>?</code> can be used to match names. + Of course, you can't just make up names and place them in <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> or <code>ServerAlias</code>. You must + first have your DNS server properly configured to map those names to an IP + address associated with your server.</p> + + <p>Finally, you can fine-tune the configuration of the virtual hosts + by placing other directives inside the <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> containers. Most directives can be + placed in these containers and will then change the configuration only of + the relevant virtual host. To find out if a particular directive is allowed, + check the <a href="../mod/directive-dict.html#Context">Context</a> of the + directive. Configuration directives set in the <em>main server context</em> + (outside any <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + container) will be used only if they are not overridden by the virtual host + settings.</p> + + <p>Now when a request arrives, the server will first check if it is using + an IP address that matches the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. If it is, then it will look at each <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> section with a matching + IP address and try to find one where the <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> or <code>ServerAlias</code> matches the requested + hostname. If it finds one, then it uses the configuration for that server. + If no matching virtual host is found, then <strong>the first listed virtual + host</strong> that matches the IP address will be used.</p> + + <p>As a consequence, the first listed virtual host is the <em>default</em> + virtual host. The <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> from + the <em>main server</em> will <strong>never</strong> be used when an IP + address matches the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + directive. If you would like to have a special configuration for requests + that do not match any particular virtual host, simply put that configuration + in a <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + container and list it first in the configuration file.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="compat" id="compat">Compatibility with Older Browsers</a></h2> + + <p>As mentioned earlier, there are some clients + who do not send the required data for the name-based virtual + hosts to work properly. These clients will always be sent the + pages from the first virtual host listed for that IP address + (the <cite>primary</cite> name-based virtual host).</p> + + <div class="note"><h3>How much older?</h3> + <p>Please note that when we say older, we really do mean older. You are + very unlikely to encounter one of these browsers in use today. All + current versions of any browser send the <code>Host</code> header as + required for name-based virtual hosts.</p> + </div> + + <p>There is a possible workaround with the <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> + directive, albeit a slightly cumbersome one:</p> + + <p>Example configuration:</p> + + <div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <br /> + <VirtualHost 111.22.33.44><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerPath /domain<br /> + DocumentRoot /web/domain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>What does this mean? It means that a request for any URI + beginning with "<code>/domain</code>" will be served from the + virtual host <code>www.domain.tld</code>. This means that the + pages can be accessed as <code>http://www.domain.tld/domain/</code> + for all clients, although clients sending a <code>Host:</code> header + can also access it as <code>http://www.domain.tld/</code>.</p> + + <p>In order to make this work, put a link on your primary + virtual host's page to + <code>http://www.domain.tld/domain/</code>. Then, in the virtual + host's pages, be sure to use either purely relative links + (<em>e.g.</em>, "<code>file.html</code>" or + "<code>../icons/image.gif</code>") or links containing the + prefacing <code>/domain/</code> (<em>e.g.</em>, + "<code>http://www.domain.tld/domain/misc/file.html</code>" or + "<code>/domain/misc/file.html</code>").</p> + + <p>This requires a bit of discipline, but adherence to these + guidelines will, for the most part, ensure that your pages will + work with all browsers, new and old.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Trke"> 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/apache2/manual/vhosts/name-based.html.es b/rubbos/app/apache2/manual/vhosts/name-based.html.es new file mode 100644 index 00000000..a3b31d36 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html.es @@ -0,0 +1,292 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Soporte de Hosting Virtual basado en nombres - Servidor HTTP Apache</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/">Mdulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="../faq/">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa de este sitio web</a></p> +<p class="apache">Versin 2.0 del Servidor HTTP Apache</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/">Servidor HTTP</a> > <a href="http://httpd.apache.org/docs/">Documentacin</a> > <a href="../">Versin 2.0</a> > <a href="./">Hosting Virtual</a></div><div id="page-content"><div id="preamble"><h1>Soporte de Hosting Virtual basado en nombres</h1> +<div class="toplang"> +<p><span>Idiomas disponibles: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" title="Espaol"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + <p>Este documento describe cmo y cundo debe usarse hosting virtual + basado en nombres.</p> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip">Diferencias entre el hosting vitual +basado en nombres y el basado en IPs</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#using">Cmo usar hosting vitual basado en +nombres</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compat">Compatibilidad con navegadores +antiguos</a></li> +</ul><h3>Consulte tambin</h3><ul class="seealso"><li><a href="ip-based.html">Hosting virtual basado en +IPs</a></li><li><a href="details.html">Discusin en profundidad sobre el +proceso de seleccin de host virtual</a></li><li><a href="mass.html">Configuracin dinmica de Hosting virtual masivo</a></li><li><a href="examples.html">Ejemplos de hosting virtual para +configuraciones tpicas</a></li><li><a href="examples.html#serverpath">Ejemplo de +configuracin de ServerPath</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="namevip" id="namevip">Diferencias entre el hosting vitual +basado en nombres y el basado en IPs</a></h2> + + <p>El hosting virtual basado en IPs usa la direccin IP de la + conexin para determinar qu host virtual es el que tiene que + servir. Por lo tanto, necesitar tener diferentes direcciones IP + para cada host. Si usa hosting virtual basado en nombres, el + servidor atiende al nombre de host que especifica el cliente en + las cabeceras de HTTP. Usando esta tcnica, una sola direccin IP + puede ser compartida por muchos sitios web diferentes.</p> + + <p>El hosting virtual basado en nombres es normalmente ms + sencillo, porque solo necesita configurar su servidor de DNS para + que localice la direccin IP correcta y entonces configurar Apache + para que reconozca los diferentes nombres de host. Usando hosting + virtual basado en nombres tambin se reduce la demanda de + direcciones IP, que empieza a ser un bien escaso. Por lo tanto, + debe usar hosting virtual basado en nombres a no ser que haya + alguna razn especial por la cual tenga que elegir usar hosting + vitual basado en direcciones IP. Algunas de stas razones pueden + ser:</p> + + <ul> + <li>Algunos clientes antiguos no son compatibles con el + hosting virtual basado en nombres. Para que el hosting + virtual basado en nombres funcione, el cliente debe enviar la + cabecera de Host HTTP. Esto es necesario para HTTP/1.1, y est + implementado como extensin en casi todos los navegadores + actuales. Si necesita dar soporte a clientes obsoletos y usar + hosting virtual basado en nombres, al final de este documento + se describe una tcnica para que pueda hacerlo.</li> + + <li>El hosting virtual basado en nombres no se puede usar + junto con SSL por la naturaleza del protocolo SSL.</li> + + <li>Algunos sistemas operativos y algunos elementos de red + tienen implementadas tcnicas de gestin de ancho de banda que + no pueden diferenciar entre hosts a no ser que no estn en + diferentes direcciones IP.</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="using" id="using">Cmo usar hosting vitual basado en +nombres</a></h2> + +<table class="related"><tr><th>Mdulos Relacionados</th><th>Directivas Relacionadas</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table> + + <p>Para usar hosting virtual basado en nombres, debe especificar + en el servidor qu direccin IP (y posiblemente qu puerto) se va + a usar para atender las peticiones a los diferentes hosts. Esto + se hace con la directiva <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. Normalmente, cualquiera + o todas las direcciones IP del servidor pueden usarse, tambin + puede usar <code>*</code> como argumento para la directiva + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. Si va a usar + ms de un puerto (por ejemplo si va usar SSL) debe aadir un + puerto a cada argumento, por ejemplo <code>*:80</code>. Tenga en + cuenta que especificando una direccin IP en la directiva + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> no hace que + el servidor escuche automticamente en esa direccin IP. Consulte + la seccin <a href="../bind.html">Especificar las direcciones y + puertos que usa Apache</a> para obtener ms informacin. Adems, + cualquier direccin IP especificada debe asociarse con un + dispositivo de red del servidor.</p> + + <p>El siguiente paso es crear un bloque <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> para cada host diferente que + quiera alojar en el servidor. El argumento de la directiva + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + debe ser el mismo que el argumento de la directiva <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> (por ejemplo, una + direccin IP, o un <code>*</code> para usar todas las direcciones + que tenga el servidor). Dentro de cada bloque <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>, necesitar + como mnimo una directiva <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> para designar qu host se + sirve y una directiva <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> para indicar dnde estn + los contenidos a servir dentro del sistema de ficheros.</p> + + <div class="note"><h3>Aadir hosts vituales a un servidor web ya existente</h3> + <p>Si est aadiendo hosts virtuales a un servidor web ya + existente, debe crear tambin un bloque <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> para el + host que ya tenga funcionando. Los valores de las directivas + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> y <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> desde este nuevo host + virtual deben tener los mismos valores que los de las + directivas <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + globales. Ponga este host virtual como el primero en el + archivo de configuracin para que sea el que acte como host + por defecto.</p> + </div> + + <p>Por ejemplo, suponga que est sirviendo el dominio + <code>www.domain.tld</code> y quiere aadir el host virtual + <code>www.otherdomain.tld</code>, que apunta a la misma direccin + IP. Entonces, lo nico que tiene que hacer es aadir lo siguiente + al fichero <code>httpd.conf</code>:</p> + + <div class="example"><p><code> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerAlias domain.tld *.domain.tld<br /> + DocumentRoot /www/domain<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent">ServerName www.otherdomain.tld<br /> + DocumentRoot /www/otherdomain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>Tambin puede optar por especificar una direccin IP + explcitamente en lugar de usar un <code>*</code> en las + directivas <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> y + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>. Por ejemplo, puede hacer esto + para hacer funcionar diferentes hosts virtuales basados en nombres + en una direccin IP, o basados en IPs, o un conjunto de hosts + virtuales basados en nombres en otra direccin.</p> + + <p>Tambin puede que quiera que se acceda a un determinado sitio + web usando diferentes nombres. Esto es posible con la directiva + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code>, puesta dentro de + la seccin <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>. Por ejemplo, en el primer bloque + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> de + arriba, la directiva <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> indica la lista de nombres + que pueden usarse para acceder a un mismo sitio web:</p> + + <div class="example"><p><code> + ServerAlias domain.tld *.domain.tld + </code></p></div> + + <p>entonces las peticiones para todos los hosts en el dominio + <code>domain.tld</code> sern servidas por el host virtual + <code>www.domain.tld</code>. Los carcteres comodines + <code>*</code> y <code>?</code> pueden usarse para encontrar + equivalencias con los nombres. Por supuesto, no puede inventarse + nombres y ponerlos en la directiva <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> o + <code>ServerAlias</code>. Primero debe tener su servidor de DNS + debidamente configurado para que pueda hacer corresponder esos + nombres con una direccin IP de su servidor.</p> + + <p>Para terminar, puede mejorar el rendimiento de la configuracin + de los hosts virtuales poniendo otras directivas dentro de las + secciones <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>. La mayor parte de las + directivas pueden ponerse en esos containers y cambiarn solo la + configuracin del host virtual al que se refieran. Para ver si una + directiva en particualar puede usarse as, consulte el <a href="../mod/directive-dict.html#Context">Contexto</a> de la + directiva. Las directivas de configuracin especificadas en el + <em>contexto del servidor principal</em> (fuera de + cualquier seccin <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>) se usan nica y + exclusivamente si sus valores no son sustituidos por alguno de los + parmetros de configuracin del host virtual.</p> + + <p>Cuando llega una peticin, el servidor primero verifica si se + est usando una direccin IP que coincide con el valor de la + directiva <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. Si es el caso, mirar en cada + seccin <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> cuya IP coincida e intentar + encontrar si el valor de la directiva <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> o de la directiva <code>ServerAlias</code> + coincide con el nombre del sitio web de la peticin. Si encuentra + una coincidencia, usa la configuracin de ese servidor. Si no la + encuentra, usa <strong>el primer host virtual de la lista</strong> + cuya direccin IP coincida con el de la peticin.</p> + + <p>Como consecuencia, el primer host virtual de la lista es el que + se usa <em>por defecto</em>. La directiva <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> del <em>servidor + principal</em> no se usar <strong>nunca</strong> cuando una + direccin IP coincida con el valor de la directiva <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. Si quiere usar una + configuracin especial para peticiones que no coinciden con ningn + host virtual en concreto, ponga esa configuracin en una seccin + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> y + pngala la primera en el fichero de configuracin.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="compat" id="compat">Compatibilidad con navegadores +antiguos</a></h2> + + <p>Como se dijo antes, hay algunos clientes que no envan los + datos necesarios para que funcione correctamente el hosting + virtual basado en nombres. Estos clientes van a recibir siempre + como respuesta a sus peticiones, pginas del primer host virtual + que haya en la lista para esa direccin IP (el host virtual + <cite>primario</cite> basado en nombres).</p> + + <div class="note"><h3>Cmo de antiguo?</h3> + <p>Tenga en cuenta que cuando decimos antiguo, queremos decir + realmente antiguo. Es muy poco probable que encuentre uno de esos + navegadores en uso todava. Todas las versiones actuales de + cualquier navegador envan la cabecera <code>Host</code> que se + necesita para que el hosting virtual basado en nombres + funcione.</p> + </div> + + <p>Existe una manera de evitar este problema con la directiva + <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code>, aunque es un poco + complicada:</p> + + <p>Ejemplo de configuracin:</p> + + <div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <br /> + <VirtualHost 111.22.33.44><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerPath /domain<br /> + DocumentRoot /web/domain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>Qu significa esto? Esto significa que una peticin de + cualquier URI que empiece por "<code>/domain</code>" ser servida + por el host virtual <code>www.domain.tld</code>. Esto significa + que las pginas pueden accederse como + <code>http://www.domain.tld/domain/</code> por todos los clientes, + aunque los clientes que enven una cabecera <code>Host:</code> + pueden tambin acceder con + <code>http://www.domain.tld/</code>.</p> + + <p>Para hacer que esto funcione, ponga un enlace en la pgina de + su host virtual primario a + <code>http://www.domain.tld/domain/</code>. Entonces, en las + pginas del host virtual, asegrese de que usa o enlaces relativos + (<em>por ejemplo</em>, "<code>file.html</code>" o + "<code>../icons/image.gif</code>") o enlaces que contengan el + <code>/domain/</code> anterior (<em>por ejemplo</em>, + "<code>http://www.domain.tld/domain/misc/file.html</code>" o + "<code>/domain/misc/file.html</code>").</p> + + <p>Esto requiere un poco de disciplina, pero siguiendo estas + reglas, puede asegurarse, casi en todos los casos, de que las + pginas de su sitio web podrn ser accedidas desde cualquier + navegador, ya sea nuevo o antiguo.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Idiomas disponibles: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" title="Espaol"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licencia bajo los trminos de la <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Mdulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="../faq/">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa de este sitio web</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/apache2/manual/vhosts/name-based.html.ja.utf8 b/rubbos/app/apache2/manual/vhosts/name-based.html.ja.utf8 new file mode 100644 index 00000000..c106bfc0 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html.ja.utf8 @@ -0,0 +1,273 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ja" xml:lang="ja"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>名前ベースのバーチャルホスト - Apache HTTP サーバ</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 サーバ バージョン 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 サーバ</a> > <a href="http://httpd.apache.org/docs/">ドキュメンテーション</a> > <a href="../">バージョン 2.0</a> > <a href="./">バーチャルホスト</a></div><div id="page-content"><div id="preamble"><h1>名前ベースのバーチャルホスト</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/name-based.html" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + <p>この文書では名前ベースのバーチャルホストをどんなとき、 + どうやって使うかを説明します。</p> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip">名前ベースと IP ベースのバーチャルホストの比較</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#using">名前ベースのバーチャルホストを利用する</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compat">古いブラウザとの互換性</a></li> +</ul><h3>参照</h3><ul class="seealso"><li><a href="ip-based.html">ネームベースのバーチャルホスト</a></li><li><a href="details.html">バーチャルホストのマッチングについての詳細</a></li><li><a href="mass.html">大量のバーチャルホストの動的な設定</a></li><li><a href="examples.html">バーチャルホストの一般的な設定例</a></li><li><a href="examples.html#serverpath">ServerPath 設定例</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="namevip" id="namevip">名前ベースと IP ベースのバーチャルホストの比較</a></h2> + + <p>IP ベースのバーチャルホストでは、応答する + バーチャルホストへのコネクションを決定するために IP + アドレスを使用します。ですから、それぞれのホストに個々に IP + アドレスが必要になります。これに対して名前ベースのバーチャルホストでは、 + クライアントが HTTP ヘッダの一部としてホスト名を告げる、 + ということに依存します。この技術で同一 IP + アドレスを異なる多数のホストで共有しています。</p> + + <p>名前ベースのバーチャルホストは通常単純で、それぞれのホスト名と + それに対応する正確な IP アドレスを DNS で設定し、異なる + ホスト名を区別するように Apache HTTP サーバを設定するだけです。 + さらに、名前ベースのバーチャルホストは不足する IP + アドレスの需要を緩和します。したがって、IP ベースのバーチャルホストを + 選択すべき特定の理由がなければ名前ベースのバーチャルホストを使うべきです。 + IP ベースのバーチャルホストを使用することを考慮する理由として、</p> + + <ul> + <li>名前ベースのバーチャルホストに対応していない古いクライアントがある + 名前ベースのバーチャルホストが働くためには、クライアントは + HTTP ホストヘッダを送ってこなければなりません。 + これは HTTP/1.1 の仕様で要求されていて、すべての現代的な + HTTP/1.0 ブラウザでも拡張として実装されています。 + とても古いクライアントをサポートしつつ、名前ベースの + バーチャルホストを行いたい場合は、この文書の最後の方に + 書かれている解決策になるかもしれない方法を見てください。</li> + + <li>名前ベースのバーチャルホストは SSL プロトコルの特徴により、 + SSL セキュアサーバには使えません。</li> + + <li>オペレーティングシステムやネットワーク装置のなかには、 + 別の IP アドレス上でない場合、複数のホストを別扱いできないような + 帯域管理の方法を実装しているものがあります。</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="using" id="using">名前ベースのバーチャルホストを利用する</a></h2> + +<table class="related"><tr><th>関連モジュール</th><th>関連ディレクティブ</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table> + + <p>名前ベースのバーチャルホストを使うには、そのホストへの + リクエストを受け付けるサーバの IP アドレス (もしかしたらポートも) + を指定する必要があります。 + これは <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + ディレクティブで設定します。通常、<code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> で + <code>*</code> の属性を使ってサーバの全ての IP アドレスを使います。 + (例えば SSL の使用などで) 複数のポートを使うことを計画しているのであれば、 + 引数に <code>*:80</code> のようにポートも含めるようにしてください。 + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> ディレクティブで + IP アドレスを書いても、 + 自動的にサーバがその IP アドレスをリッスンするということはないことに + 注意してください。詳細は「<a href="../bind.html">Apache の使うアドレスと + ポートを設定する</a>」を読んでください。さらに、ここで指定された + IP アドレスは全てサーバのネットワークインターフェースと関連付けられて + いなければなりません。</p> + + <p>次は、扱うホストそれぞれに対して <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> ブロックを + 作成してください。<code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + ディレクティブの引数は <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + ディレクティブの引数と同じにしてください (すなわち、IP アドレスか、全てのアドレスを意味する + <code>*</code>)。それぞれの <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + ディレクティブの中には、最低限、どのホストが扱われるかを示す <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> ディレクティブと、 + そのホスト用のコンテンツがファイルシステム上のどこにあるかを示す + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> ディレクティブを + 書く必要があります。</p> + + <div class="note"><h3>メインホストはなくなります</h3> + <p>既にあるウェブサーバにバーチャルホストを追加する場合、 + 既存のウェブサーバに対しても <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + ブロックを作らなければなりません。このバーチャルホストの + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> と + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + は、グローバルな <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> と + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + と同じものにします。また、このバーチャルホストを設定ファイルの中で + 先頭に置いて、デフォルトホストとして動作するようにします。</p> + </div> + + <p>たとえば、<code>www.domain.tld</code> を動かしていて、 + さらにバーチャルホスト <code>www.otherdomain.tld</code> + を追加するとしましょう。このバーチャルホストは同一 IP を指しているとします。 + そのような場合は、<code>httpd.conf</code> + に以下のようなコードを追加するだけです</p> + + <div class="example"><p><code> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerAlias domain.tld *.domain.tld<br /> + DocumentRoot /www/domain<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent">ServerName www.otherdomain.tld<br /> + DocumentRoot /www/otherdomain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> 及び + <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> のどちらの場合も、 + * の部分には明示的に IP アドレスを指定することができます。 + 例えば、ある IP アドレスでは名前ベースのバーチャルホストを使いたい一方で、 + 別の IP アドレスでは、他の IP ベースのバーチャルホストや + 別組の名前ベースのバーチャルホストを使いたい場合、 + そう設定することになるでしょう。</p> + + <p>複数の名前でサーバアクセスができるようにしたいことも多いでしょう。 + このようなことは、<code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> ディレクティブを <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + セクションに記述することで実現できます。 + 例えば上記の <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> の例であれば、 + 次のように一覧に挙げられた名前が、 + ユーザが同一のウェブサイトとして目にして使用できるサーバ名である、 + と <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> + ディレクティブで指定できます。</p> + + <div class="example"><p><code> + ServerAlias domain.tld *.domain.tld + </code></p></div> + + <p><code>domain.tld</code> ドメインへの全てのホストへのリクエストは + <code>www.domain.tld</code> のバーチャルホストが処理します。 + 名前をマッチさせるために、ワイルドカード文字 * や ? + を使用することもできます。もちろん思いつきの名前を作って、 + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> や + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> + にその名前を書くといったことはできません。まずは、 + これらの名前が サーバに付けられた IP アドレスにマップされるように + DNS サーバを適切に設定しなければなりません。</p> + + <p>最後に、<code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> コンテナの中に + 他のディレクティブを書くことで、バーチャルホストの設定を細かく調整 + することができます。 + ほとんどのディレクティブはこれらのコンテナに設置することができて、 + 変更点はそのバーチャルホストに対してのみ有効になります。 + どのディレクティブを書くことができるかは、ディレクティブの <a href="../mod/directive-dist.html#context">コンテキスト</a> を + 調べてください。<em>主サーバコンテキスト</em> + (<code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + コンテナの外) の設定用ディレクティブはバーチャルホストでの設定で + 上書きされない場合のみ使用されます。</p> + + <p>リクエストが来ると、サーバはまず最初に <code class="directive"><a href="../mod/core.html#namevirtualhost"><NameVirtualHost></a></code> + にマッチする IP アドレスかどうかをチェックします。マッチすれば + マッチした IP アドレスの <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + のそれぞれのセクションの中から + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> か + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> + に要求されたホスト名があるか探します。 + 見つかればそのサーバ用の設定を使います。マッチするバーチャルホスト + が見つからなければ、マッチした IP アドレスの + <strong>リストの最初にあるバーチャルホスト</strong> が使われます。</p> + + <p>結果として、リストの最初のバーチャルホストが <em>デフォルト</em> の + バーチャルホストになります。IP アドレスが <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + ディレクティブにマッチした場合は、<em>メインのサーバ</em> の + <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + は<strong>決して使われません</strong> + どのバーチャルホストにもマッチしないリクエストに対して、 + 特別な設定をしたいのであれば、設定ファイル中の最初の + <code><VirtualHost></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="compat" id="compat">古いブラウザとの互換性</a></h2> + + <p>以前述べたように、名前ベースのバーチャルホストが正しく動作する + ために必要な情報を送ってこないクライアントが依然として存在しています。 + そのようなクライアントに対しては、該当する IP アドレスについて、 + 一番最初に設定されているバーチャルホスト + (<cite>プライマリ</cite>の名前ベースのバーチャルホスト) + からページが送り返されます。</p> + + <div class="note"><h3>どのぐらい古いの ?</h3> + <p>「古い」と表現している場合、本当に古いことを意味して使っています。 + 不幸にして今現在でもこのような古いブラウザに遭遇することがあります。 + 現在のブラウザは全て、名前ベースのバーチャルホストに必要な + <code>Host</code> ヘッダを送ります。</p> + </div> + + <p><a href="../mod/core.html#serverpath"><code>ServerPath</code></a> + ディレクティブで対処が可能です。ちょっと不格好ですけれども。</p> + + <p>設定例</p> + + <div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <br /> + <VirtualHost 111.22.33.44><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerPath /domain<br /> + DocumentRoot /web/domain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>この例にはどういう意味があるでしょうか? これは + "<code>/domain</code>" で始まる URI へのリクエストはすべて、 + バーチャルホスト <code>www.domain.tld</code> で処理される、 + という意味です。つまり、すべてのクライアントで + <code>http://www.domain.tld/domain/</code> でアクセスできるページが、 + <code>Host:</code> ヘッダを送ってくるクライアントであれば + <code>http://www.domain.tld/</code> としてもアクセスできる、 + という意味です。</p> + + <p>これが動作するようにするには、 + プライマリのバーチャルホストのページに + <code>http://www.domain.tld/domain/</code> へのリンクを設置します。 + そして、バーチャルホストのページでは、純粋な相対リンク (<em>例:</em> + "<code>file.html</code>" や "<code>../icons/image.gif</code>")、 + あるいは <code>/domain/</code> で始まるリンク (<em>例:</em> + "<code>http://www.domain.tld/domain/misc/file.html</code>" や + "<code>/domain/misc/file.html</code>") だけを設置します。</p> + + <p>これには、幾分かの規律が必要となりますが、 + このようなガイドラインを忠実に守ることにより、たいていの場合、 + すべてのブラウザで ― 新しいブラウザでも古いものでも ― + 作成したページが見えるということを保証します。</p> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/name-based.html" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.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/apache2/manual/vhosts/name-based.html.ko.euc-kr b/rubbos/app/apache2/manual/vhosts/name-based.html.ko.euc-kr new file mode 100644 index 00000000..47527a79 --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html.ko.euc-kr @@ -0,0 +1,238 @@ +<?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="./">ȣƮ</a></div><div id="page-content"><div id="preamble"><h1≯ ȣƮ </h1> +<div class="toplang"> +<p><span> : </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + <p> ̸ ȣƮ ϴ + Ѵ.</p> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip"≯ IP ȣƮ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#using"≯ ȣƮ ϱ</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compat"> ȣȯ</a></li> +</ul><h3></h3><ul class="seealso"><li><a href="ip-based.html">IP ȣƮ </a></li><li><a href="details.html">ȣƮ ã ڼ </a></li><li><a href="mass.html">뷮 ȣƮ ϱ</a></li><li><a href="examples.html">Ϲ ȣƮ </a></li><li><a href="examples.html#serverpath">ServerPath </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="namevip" id="namevip"≯ IP ȣƮ</a></h2> + + <p>IP ȣƮ IP ּҸ + ȣƮ Ѵ. ȣƮ ٸ IP ּҸ + Ѵ. ̸ ȣƮ Ŭ̾Ʈ + HTTP ȣƮ ˷ֱ ٶ. ̷ + IP ּҷ ٸ ȣƮ ִ.</p> + + <p≯ ȣƮ DNS ȣƮ ùٸ + IP ּҷ ϵ ȣƮ ϰ, ٸ ȣƮ + ֵ ġ ϱ⸸ ϸǹǷ ϴ. ̸ + ȣƮ IP ּҰ ʿ. Ƿ Ư + IP ȣƮ ٸ ̸ ȣƮ + ؾ Ѵ. IP ȣƮ ؾ δ:</p> + + <ul> + <li≯ ȣƮ ʴ + Ŭ̾Ʈ ִ. ̸ ȣƮ Ϸ + Ŭ̾Ʈ HTTP Host Ѵ. ̴ + HTTP/1.1 ʼ̰, ֱ HTTP/1.0 鵵 + Ȯ Ѵ. ̸ ȣƮ ϸ鼭 + Ŭ̾Ʈ ؾ Ѵٸ ִ + .</li> + + <li>SSL ݻ SSL ȼ ̸ + ȣƮ .</li> + + <li> ü Ʈ ġ ٸ IP ּҸ + ȣƮ ϴ Ʈ 뷮(bandwidth) + Ѵ.</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="using" id="using"≯ ȣƮ ϱ</a></h2> + +<table class="related"><tr><th>õ </th><th>õ þ</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table> + + <p≯ ȣƮ Ϸ + IP ּҸ (Ƹ Ʈ) ؾ Ѵ. ̴ <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> þ ϴ. + Ϲ IP ּҸ Ѵٸ + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + ƱԸƮ <code>*</code> Ѵ. Ʈ + ( , SSL ) ȹ̶ <code>*:80</code> + ƱԸƮ Ʈ ߰ؾ Ѵ. <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> þ IP ּҸ + ־ٰ ڵ IP ּҸ ٸ + ϶. ڼ <a href="../bind.html">ġ + ּҿ Ʈ ϱ</a> ϶. , ⼭ + IP ּҴ Ʈ ̽̾ Ѵ.</p> + + <p> ܰ Ϸ ȣƮ <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + ̴. <code class="directive"><a href="../mod/core.html#virtualhost>"><VirtualHost>></a></code> þ ƱԸƮ + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> þ + ƱԸƮ( , IP ּҳ ּҸ ϴ <code>*</code>) + ƾ Ѵ. <code class="directive"><a href="../mod/core.html#virtualhost>"><VirtualHost>></a></code> ȿ + ּ ȣƮ ϴ <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> þ ȣƮ + Ͻý ִ ϴ <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> þ ʿϴ.</p> + + <div class="note"><h3> ȣƮ </h3> + <p> ϴ ȣƮ ߰Ѵٸ + ϴ ȣƮ <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> ϵ ߰ؾ + Ѵ. Ͽ ϴ <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> ü <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> ƾ Ѵ. + Ͽ ȣƮ ⺻ ȣƮ + ȴ.</p> + </div> + + <p> <code>www.domain.tld</code> ϰ + ־µ IP ּҿ + <code>www.otherdomain.tld</code> ȣƮ ߰ϰ + ʹٰ . <code>httpd.conf</code> + ߰ϸ ȴ:</p> + + <div class="example"><p><code> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerAlias domain.tld *.domain.tld<br /> + DocumentRoot /www/domain<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent">ServerName www.otherdomain.tld<br /> + DocumentRoot /www/otherdomain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + þ <code>*</code> IP ּҸ + ִ. , ̷ IP ּҿ ̸ + ȣƮ , ٸ ּҿ IP Ȥ ̸ + ȣƮ ִ.</p> + + <p> ̸ ֱ ٶ. ̴ + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + ȿ <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> + þ Ͽ ϴ. ù° <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> Ͽ + <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> þ + ϸ ̸ Ʈ ִ:</p> + + <div class="example"><p><code> + ServerAlias domain.tld *.domain.tld + </code></p></div> + + <p><code>domain.tld</code> ο ִ ȣƮ + û <code>www.domain.tld</code> ȣƮ Ѵ. + ̸ ٶ ϵī <code>*</code> <code>?</code> + ִ. <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>̳ <code>ServerAlias</code> + ̸ ־ٰ ƴϴ. ̸ + IP ּҷ ϵ DNS ˸° ؾ Ѵ.</p> + + <p> <code class="directive"><a href="../mod/core.html#<virtualhost>"><<VirtualHost>></a></code> ȿ ٸ + þ Ͽ ȣƮ ڼ ִ. + κ þ , õ ȣƮ + Ѵ. þ 밡 ˷ þ <a href="../mod/directive-dict.html#Context"></a> + Ȯ϶. (<code class="directive"><a href="../mod/core.html#<virtualhost>"><<VirtualHost>></a></code> ƴ) + <em>ּ</em> þ ȣƮ + þ 쿡 ȴ.</p> + + <p>û <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> IP + ּ ˻Ѵ. ٸ IP ּҸ <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + ǵ鿡 û ȣƮ ġϴ <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>̳ + <code>ServerAlias</code> ã´. ã Ѵ. + ȣƮ ãϸ, IP ּҿ شϴ + <strong>ȣƮ ù° </strong> Ѵ.</p> + + <p> ó ȣƮ <em>⺻</em> + ȣƮ ȴ. IP ּҰ <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> þ شϸ, + <em>ּ</em> <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> + <strong></strong> ʴ´. Ư ȣƮ + شʴ û Ϸ <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></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="compat" id="compat"> ȣȯ</a></h2> + + <p>̹ ̸ ȣƮ ùٷ ϱ + ʿ ʴ Ŭ̾Ʈ ִ. ̷ Ŭ̾Ʈ + û IP ּҿ ù° ȣƮ + (<cite></cite> ̸ ȣƮ) + Ѵ.</p> + + <div class="note"><h3> ϴ°?</h3> + <p>⼭ Ǿ Ѵ. + ó ̷ Ǿ. + ̸ ȣƮ ʿ <code>Host</code> + .</p> + </div> + + <p> ణ 彺 <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> þ ذ ִ:</p> + + <p> :</p> + + <div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <br /> + <VirtualHost 111.22.33.44><br /> + <span class="indent"> + ServerName www.domain.tld<br /> + ServerPath /domain<br /> + DocumentRoot /web/domain<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>̰ ΰ? "<code>/domain</code>" ϴ + URI û ȣƮ <code>www.domain.tld</code> + Ѵ. , <code>Host:</code> Ŭ̾Ʈ + <code>http://www.domain.tld/</code>ε , + <code>http://www.domain.tld/domain/</code>δ + Ŭ̾Ʈ ִ.</p> + + <p≯ ȣƮ ִ + <code>http://www.domain.tld/domain/</code> ũ + ִ´. ȣƮ 븵ũ ( , + "<code>file.html</code>" ̳ "<code>../icons/image.gif</code>") + Ȥ ("<code>http://www.domain.tld/domain/misc/file.html</code>"̳ + "<code>/domain/misc/file.html</code>" ) տ + <code>/domain/</code> ũ Ѵ.</p> + + <p> Ģ ʿ Ģ κ + ̳ ̳ + ִ.</p> + +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.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/apache2/manual/vhosts/name-based.html.tr.utf8 b/rubbos/app/apache2/manual/vhosts/name-based.html.tr.utf8 new file mode 100644 index 00000000..7fef092a --- /dev/null +++ b/rubbos/app/apache2/manual/vhosts/name-based.html.tr.utf8 @@ -0,0 +1,256 @@ +<?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>İsme Dayalı Sanal Konaklar - 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="./">Sanal Konaklar</a></div><div id="page-content"><div id="preamble"><h1>İsme Dayalı Sanal Konaklar</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.html" title="Türkçe"> tr </a></p> +</div> + + <p>Bu belgede isme dayalı sanal konakların ne zaman, nasıl kullanılacakları + açıklanmıştır.</p> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip">İsme dayalı ve IP’ye dayalı Sanal Konaklar</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#using">İsme Dayalı Sanal Konakların Kullanımı</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#compat">Artık Tarihe Karışmış Tarayıcılarla Uyumluluk</a></li> +</ul><h3>Ayrıca bakınız:</h3><ul class="seealso"><li><a href="ip-based.html">IP Adresine Dayalı Sanal Konaklar</a></li><li><a href="details.html">Konak Eşlemenin Derinliğine İncelenmesi</a> +</li><li><a href="mass.html">Devingen olarak Yapılandırılan Kütlesel Sanal +Barındırma</a></li><li><a href="examples.html">Çok kullanılan sanal konak yapılandırma +örnekleri</a></li><li><a href="examples.html#serverpath">ServerPath yapılandırma örneği</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="namevip" id="namevip">İsme dayalı ve IP’ye dayalı Sanal Konaklar</a></h2> + + <p>IP’ye dayalı sanal konaklarda sunulacak sanal konağı doğru tespit + edebilmek için bağlantının yapıldığı IP adresine bakılır. Bu bakımdan her + konak için ayrı bir IP adresine gereksinim vardır. İsme dayalı sanal + konaklarda ise sunucu, istemcinin HTTP başlığının bir parçası olarak + gönderdiği konak adını kullanır. Bu teknikte aynı IP adresini çok sayıda + farklı konak kullanabilir.</p> + + <p>İsme dayalı sanal barındırma nispeten daha kolaydır, çünkü her konak + ismini doğru IP adresiyle eşlemek için DNS sunucunuzu yapılandırdıktan + sonra Apache HTTP sunucusunu farklı konak isimlerini tanıyacak şekilde + yapılandırmanız yeterli olur. İsme dayalı sanal barındırma ayrıca zaten + kıt olan IP adreslerine talebi de azaltır. Bu nedenle, IP’ye dayalı sanal + konakları kullanmanızı gerektirecek çok özel bir sebep olmadıkça isme + dayalı sanal konaklar kullanmalısınız. IP’ye dayalı sanal konakların + kullanımını gerektirebilecek bazı durumlar:</p> + + <ul> + <li>Bazı tarihi istemciler isme dayalı sanal konaklarla uyumlu değildir. + İsme dayalı sanal konakların çalışması için istemcinin HTTP Host + başlığı göndermesi gerekir. Bu da HTTP/1.1 desteği gerektirir. + Günümüzdeki HTTP/1.0 istemcileri bir eklenti olarak HTTP/1.1’i de + desteklemektedir. Tarihi eser haline gelmiş HTTP/1.1 desteği + bulurmayan eski istemcileri hala isme dayalı sanal konaklarla + desteklemek isterseniz bu belgenin sonunda bunu mümkün kılabilecek bir + tekniğe yer verilmiştir.</li> + + <li>İsme dayalı sanal konaklar SSL portokolünün doğası gereğince SSL’li + güvenli sunucular için kullanılamazlar.</li> + + <li>Bazı işletim sistemlerinin ve ağ donanımlarının gerçekleştirdiği + band genişliği yönetim teknikleri IP adresleri farklı olmadığı sürece + konaklar arasında ayrım yapamazlar.</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="using" id="using">İsme Dayalı Sanal Konakların Kullanımı</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/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table> + + <p>İsme dayalı sanal konakları kullanmak için, bu konaklar için istekleri + kabul edecek sunucuya IP adresini (ve muhtemelen portu da) + belirtmelisiniz. Bu işlem <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> yönergesiyle yapılır. Normal + şartlar altında sunucu üzerinde bütün IP adreslerinin kullanılması + gerekir; bunun için <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> + yönergesine argüman olarak <code>*</code> belirtebilirsiniz. Çok sayıda + port kullanmayı planlıyorsanız (SSL çalıştırmak gibi), argümana + <code>*:80</code> şeklinde port ekleyebilirsiniz. Yalnız, <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> yönergesinde bir IP adresi + belirtmiş olmakla sunucunun kendiliğinden o IP adresini dinlemeyeceğine + dikkat ediniz. Bu konuda ayrıntılı bilgi edinmek için <a href="../bind.html">Apache’nin kullanacağı adreslerin ve portların + ayarlanması</a> belgesine bakınız. Ayrıca, sunucuda, burada belirttiğiniz + IP adresine sahip bir ağ arabirimi olmalıdır.</p> + + <p>Sonraki adım sunacağınız her konak için ayrı bir <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümü oluşturmaktır. + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + yönergesinin argümanı ile eşleşen bir <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> yönergesi tanımlanmış olmalıdır + (bu değer normalde ya bir IP adresidir ya da <code>*</code>’dır). Her + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümü + içinde sunulan konağı belirtmek üzere en azından bir adet <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> yönergesine ve konak içeriğinin dosya + sisteminde bulunduğu yeri gösteren bir <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> yönergesine ihtiyacınız olacaktır.</p> + + <div class="note"><h3>Ana konağı unutmayın</h3> + <p>Mevcut sitenize sanal konaklar eklerseniz, mevcut siteniz için de bir + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümü + oluşturmalısınız. Bu sanal konak bölümü içinde kullanacağınız + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> ve <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> yönergelerinin argümanları, bu + yönergelerin sunucu geneli için belirttiğiniz değerlerini + içermelidir. Bu sanal konağı yapılandırma dosyanızdaki ilk sanal konak + yapın ki, öntanımlı konak olsun.</p> + </div> + + <p>Örnek olarak, <code>www.biralan.tld</code> adresinden sitenizi sunmakta + olduğunuzu ve bunun yanına aynı IP adresini kullanan + <code>www.digeralan.tld</code> sanal konağını eklemek istediğinizi + varsayalım. Bunun için <code>httpd.conf</code> dosyanıza basitçe şu + satırları ekleyebilirsiniz:</p> + + <div class="example"><p><code> + NameVirtualHost *:80<br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent"> + ServerName www.biralan.tld<br /> + ServerAlias biralan.tld *.biralan.tld<br /> + DocumentRoot /siteler/biralan<br /> + </span> + </VirtualHost><br /> + <br /> + <VirtualHost *:80><br /> + <span class="indent">ServerName www.digeralan.tld<br /> + DocumentRoot /siteler/digeralan<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>İsterseniz, <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> ve + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> + yönergelerinde argüman olarak <code>*</code> yerine doğrudan bir IP adresi + belirtebilirsiniz. Hatta, daha sonra, isme dayalı sanal konakları bir IP + adresinden ve IP’ye dayalı olanları veya isme dayalı diğer bir sanal konak + grubunu diğer IP adreslerinden sunmak isteyebilirsiniz.</p> + + <p>Çoğu sunucunun birden fazla isim ile erişilebilir olması istenir. Bu, + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümü + içine bir <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> yönergesi + yerleştirmek suretiyle mümkün olur. Örneğin yukarıdaki örnekte, + kullanıcıların aynı siteye farklı isimlerle erişmelerini mümkün kılmak + için bölüm içine şu satırı ekleyebilirsiniz:</p> + + <div class="example"><p><code> + ServerAlias biralan.tld *.biralan.tld + </code></p></div> + + <p>Böylece <code>biralan.tld</code> alanındaki tüm konaklar için gelen + isteklere <code>www.biralan.tld</code> sanal konağından hizmet sunulmuş + olur. Konak isimleriyle eşleşmek üzere dosya ismi kalıp karakterleri + <code>*</code> ve <code>?</code> kullanılabilir. Şüphesiz bu isimleri sırf + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> veya + <code>ServerAlias</code> yönergesinde belirtmiş olmakla bu isimleri + erişilebilir kılamazsınız. Öncelikle, bu isimleri sunucunuzdaki IP + adresleriyle eşlemek üzere yapılandıracağınız bir DNS sunucunuz + olmalıdır.</p> + + <p>Son olarak, sanal konak yapılandırmanıza, <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümlerinin içine başka yönergeler + yerleştirerek ince ayar çekebilirsiniz. Çoğu yönerge bu bölümlere + yerleştirilebilir ve sadece o sanal konakla ilgili yapılandırmayı + değiştirmek için kullanılabilir. Belli bir yönergenin sanal konak + bölümlerinde kullanılıp kullanılmayacağını yönergenin açıklamasında <a href="../mod/directive-dict.html#Context">Bağlam</a> satırına bakarak + öğrenebilirsiniz. <em>Ana sunucu bağlamındaki</em> (<code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümleri dışındaki) + yapılandırma yönergelerinden sadece sanal konak bölümlerinde geçersiz + kılınmamış olanlar kullanılacaktır.</p> + + <p>Sunucuya bir istek geldiğinde, sunucu önce IP adresiyle eşleşmesi olası + <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> bölümleri var mı diye + bakar. Varsa, IP adresini eşleştirmek için <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> bölümlerine tek tek bakar ve + istenen konak ismi ile eşleşen bir <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> veya <code>ServerAlias</code> yönergesi bulmaya + çalışır. Bir tane bulduğunda, sunucu için onun yapılandırmasını kullanır. + İsimle eşleşen bir sanal konak bulamazsa IP adresiyle eşleşen <strong>ilk + sanal konağın</strong> yapılandırmasını kullanır.</p> + + <p>Bir önkabul olarak yapılandırma dosyasında rastlanan ilk sanal konak + <em>öntanımlı</em> sanal konaktır. IP adresi bir sanal konakla eşleştiği + takdirde <em>ana sunucunun</em> <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> değeri <strong>asla</strong> kullanılmayacaktır. + Sanal konaklardan hiçbiriyle eşleşmeyen istekler için özel bir + yapılandırmanız olsun isterseniz, bu yapılandırmayı yapılandırma + dosyanızdaki ilk <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> bölümüne yerleştirmeniz + yetecektir.</p> + +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="compat" id="compat">Artık Tarihe Karışmış Tarayıcılarla Uyumluluk</a></h2> + + <p>Evvelce de bahsedildiği gibi, isme dayalı sanal konakların gerektiği gibi + çalışması için gerekli veriyi göndermeyen bazı istemciler vardır. Bu + istemcilere daima o IP adresinin yapılandırma dosyasındaki ilk sanal + konağının (isme dayalı <cite>başat</cite> sanal konak) sayfaları + gönderilir.</p> + + <div class="note"><h3>Ne kadar eski?</h3> + <p>Lütfen dikkat edin, eski deyince gerçekten de antika demek istiyoruz. + Günümüzde bu tür tarayıcılara rastlamanız neredeyse imkansızdır. Günümüz + tarayıcılarının hepsi isme dayalı sanal konakların gerektirdiği + <code>Host</code> başlığını gönderirler.</p> + </div> + + <p>Olayı fazla germeden <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code> + yönergesini kullanarak sorunun çevresinden dolanmak mümkündür:</p> + + <p>Örnek yapılandırma:</p> + + <div class="example"><p><code> + NameVirtualHost 111.22.33.44<br /> + <br /> + <VirtualHost 111.22.33.44><br /> + <span class="indent"> + ServerName www.biralan.tld<br /> + ServerPath /biralan<br /> + DocumentRoot /siteler/biralan<br /> + </span> + </VirtualHost><br /> + </code></p></div> + + <p>Bu ne anlama geliyor? Anlamı, "<code>/biralan</code>" ile başlayan her + URI isteği <code>www.biralan.tld</code> sanal konağı tarafından sunulacak, + demektir. Yani, tüm istemcilerin + <code>http://www.biralan.tld/biralan/</code> olarak eriştiği yere + <code>Host:</code> başlığı gönderen istemciler + <code>http://www.biralan.tld/</code> olarak erişirler.</p> + + <p>Bunu gerçekleştirebilmek için başat sanal konağın baş sayfasına + <code>http://www.biralan.tld/biralan/</code> için bir bağ koyduktan sonra + sanal konağın sayfalarında ya tamamen göreli bağlar + ("<code>dosya.html</code>", "<code>../simgeler/resim.png</code>" gibi) + veya <code>/biralan/</code> ile öncelenmiş bağlar + ("<code>http://www.biralan.tld/biralan/muht/dosya.html</code>" veya + "<code>/biralan/muht/dosya.html</code>" gibi) kullanın.</p> + + <p>Bu işlem biraz disiplin gerektirse de bu yazılanlara sıkı sıkıya bağlı + kalarak hem eski hem de yeni tarayıcıların sayfalarınızı doğru + görüntülemesini sağlamış olursunuz.</p> + +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="../en/vhosts/name-based.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../es/vhosts/name-based.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="../tr/vhosts/name-based.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 |