diff options
Diffstat (limited to '')
| -rw-r--r-- | docs/manual/vhosts/details.html | 17 | ||||
| -rw-r--r-- | docs/manual/vhosts/details.html.en | 348 | ||||
| -rw-r--r-- | docs/manual/vhosts/details.html.fr.utf8 | 369 | ||||
| -rw-r--r-- | docs/manual/vhosts/details.html.ko.euc-kr | 412 | ||||
| -rw-r--r-- | docs/manual/vhosts/details.html.tr.utf8 | 319 |
5 files changed, 1465 insertions, 0 deletions
diff --git a/docs/manual/vhosts/details.html b/docs/manual/vhosts/details.html new file mode 100644 index 0000000..8132639 --- /dev/null +++ b/docs/manual/vhosts/details.html @@ -0,0 +1,17 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: details.html.en +Content-Language: en +Content-type: text/html; charset=UTF-8 + +URI: details.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +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/docs/manual/vhosts/details.html.en b/docs/manual/vhosts/details.html.en new file mode 100644 index 0000000..d0fa1d0 --- /dev/null +++ b/docs/manual/vhosts/details.html.en @@ -0,0 +1,348 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>An In-Depth Discussion of Virtual Host Matching - Apache HTTP Server Version 2.4</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" /> +<script src="../style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.4</p> +<img alt="" src="../images/feather.png" /></div> +<div class="up"><a href="./"><img title="<-" 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.4</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="../fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Français"> fr </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="Türkçe"> tr </a></p> +</div> + + + <p>This document attempts to explain + exactly what Apache HTTP Server does when deciding what virtual host to + serve a request from.</p> + + <p>Most users should read about <a href="name-based.html#namevip"> + Name-based vs. IP-based Virtual Hosts</a> to decide which type they + want to use, then read more about <a href="name-based.html">name-based</a> + or <a href="ip-based.html">IP-based</a> virtualhosts, and then see + <a href="examples.html">some examples</a>.</p> + + <p>If you want to understand all the details, then you can + come back to this page.</p> + +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#configparsing">Configuration File</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><h3>See also</h3><ul class="seealso"><li><a href="ip-based.html">IP-based Virtual Host Support</a></li><li><a href="name-based.html">Name-based Virtual Hosts Support</a></li><li><a href="examples.html">Virtual Host examples for common setups</a></li><li><a href="mass.html">Dynamically configured mass virtual hosting</a></li><li><a href="#comments_section">Comments</a></li></ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="configparsing" id="configparsing">Configuration File</a></h2> + + <p>There is a <em>main server</em> which consists of all the + definitions appearing outside of + <code><VirtualHost></code> sections.</p> + + <p>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>Each <code>VirtualHost</code> directive includes one + or more addresses and optional ports.</p> + + <p>Hostnames can be used in place of IP addresses in a virtual + host definition, but they are resolved at startup and if any name + resolutions fail, those virtual host definitions are ignored. + This is, therefore, not recommended.</p> + + <p>The address can be specified as + <code>*</code>, which will match a request if no + other vhost has the explicit address on which the request was + received. </p> + + <p>The address appearing in the <code>VirtualHost</code> + directive can have an optional port. If the port is unspecified, + it is treated as a wildcard port, which can also be indicated + explicitly using <code>*</code>. + The wildcard port matches any port.</p> + + <p>(Port numbers specified in the <code>VirtualHost</code> directive do + not influence what port numbers Apache will listen on, they only control + which <code>VirtualHost</code> will be selected to handle a request. + Use the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive to + control the addresses and ports on which the server listens.) + </p> + + <p>Collectively the + entire set of addresses (including multiple + results from DNS lookups) are called the vhost's + <em>address set</em>.</p> + + <p>Apache automatically discriminates on the + basis of the HTTP <code>Host</code> header supplied by the client + whenever the most specific match for an IP address and port combination + is listed in multiple virtual hosts.</p> + + <p>The + <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> directive + may appear anywhere within the definition of a server. However, + each appearance overrides the previous appearance (within that + server). If no <code>ServerName</code> is specified, the server + attempts to deduce it from the server's IP address.</p> + + <p>The first name-based vhost in the configuration file for a + given IP:port pair is significant because it is used for all + requests received on that address and port for which no other + vhost for that IP:port pair has a matching ServerName or + ServerAlias. It is also used for all SSL connections if the + server does not support <a class="glossarylink" href="../glossary.html#servernameindication" title="see glossary">Server Name Indication</a>.</p> + + <p>The complete list of names in the <code>VirtualHost</code> + directive are treated just like a (non wildcard) <code>ServerAlias</code> + (but are not overridden by any <code>ServerAlias</code> statement).</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/mpm_common.html#receivebuffersize">ReceiveBufferSize</a></code>, + or <code class="directive"><a href="../mod/mpm_common.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">IP address lookup</a></h3> + + <p>When the connection is first received on some address and port, + the server looks for all the <code>VirtualHost</code> definitions + that have the same IP address and port.</p> + + <p>If there are no exact matches for the address and port, then + wildcard (<code>*</code>) matches are considered.</p> + + <p>If no matches are found, the request is served by the + main server.</p> + + <p>If there are <code>VirtualHost</code> definitions for + the IP address, the next step is to decide if we have to + deal with an IP-based or a name-based vhost.</p> + + + + <h3><a name="ipbased" id="ipbased">IP-based vhost</a></h3> + + <p>If there is exactly one <code>VirtualHost</code> directive + listing the IP address and port combination that was determined + to be the best match, no further actions are performed and + the request is served from the matching vhost.</p> + + + + <h3><a name="namebased" id="namebased">Name-based vhost</a></h3> + + <p>If there are multiple <code>VirtualHost</code> directives listing + the IP address and port combination that was determined to be the + best match, the "list" in the remaining steps refers to the list of vhosts + that matched, in the order they were in the configuration file.</p> + + <p>If the connection is using SSL, the server supports <a class="glossarylink" href="../glossary.html#servernameindication" title="see glossary">Server Name Indication</a>, and + the SSL client handshake includes the TLS extension with the + requested hostname, then that hostname is used below just like the + <code>Host:</code> header would be used on a non-SSL connection. + Otherwise, the first name-based vhost whose address matched is + used for SSL connections. This is significant because the + vhost determines which certificate the server will use for the + connection.</p> + + <p>If the request contains a <code>Host:</code> header field, the + list is searched for the first vhost with a matching + <code>ServerName</code> or <code>ServerAlias</code>, and the + request is served from that vhost. A <code>Host:</code> header + field can contain a port number, but Apache always ignores it and + matches against the real port to which the client sent the + request.</p> + + <p>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 (such as a HTTP/1.0 + request).</p> + + + + <h3><a name="persistent" id="persistent">Persistent connections</a></h3> + + <p>The <em>IP lookup</em> described above is only done <em>once</em> for a + particular TCP/IP session while the <em>name lookup</em> 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>Name-based virtual hosting is a process applied after + the server has selected the best matching IP-based virtual + host.</li> + + <li>If you don't care what IP address the client has connected to, use a + "*" as the address of every virtual host, and name-based virtual hosting + is applied across all configured virtual hosts.</li> + + <li><code>ServerName</code> and <code>ServerAlias</code> + checks are never performed for an IP-based vhost.</li> + + <li>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>Any port in the <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 two vhosts have an address in common, those common addresses + act as name-based virtual hosts implicitly. This is new behavior as of + 2.3.11.</li> + + <li>The main server is only used to serve a request if the IP + address and port number to which the client connected + does not match any vhost (including a + <code>*</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>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> + </ul> + +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/vhosts/details.html" title="English"> en </a> | +<a href="../fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Français"> fr </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="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/vhosts/details.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/vhosts/details.html.fr.utf8 b/docs/manual/vhosts/details.html.fr.utf8 new file mode 100644 index 0000000..29bc31d --- /dev/null +++ b/docs/manual/vhosts/details.html.fr.utf8 @@ -0,0 +1,369 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="fr" xml:lang="fr"><head> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Détails sur le fonctionnement des serveurs virtuels - Serveur HTTP Apache Version 2.4</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" /> +<script src="../style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p> +<p class="apache">Serveur HTTP Apache Version 2.4</p> +<img alt="" src="../images/feather.png" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">Serveur HTTP</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.4</a> > <a href="./">Serveurs virtuels</a></div><div id="page-content"><div id="preamble"><h1>Détails sur le fonctionnement des serveurs virtuels</h1> +<div class="toplang"> +<p><span>Langues Disponibles: </span><a href="../en/vhosts/details.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../fr/vhosts/details.html" title="Français"> fr </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="Türkçe"> tr </a></p> +</div> + + + <p>Ce document vise à expliquer dans le détail comment le serveur + HTTP Apache procède lors du choix de l'utilisation + d'un serveur virtuel en fonction d'une requête reçue.</p> + + <p>Il est recommandé de lire la documentation<a href="name-based.html#namevip"> + Serveurs virtuels à base de nom et serveurs virtuels à base + d'adresse IP</a> pour déterminer quel type de serveur virtuel nous + convient le mieux, puis de lire les documentations <a href="name-based.html">serveurs virtuels à base de nom</a> ou <a href="ip-based.html">serveurs virtuels à base d'adresse IP</a>, et enfin + d'étudier <a href="examples.html">quelques exemples</a>.</p> + + <p>Si vous voulez entrer dans les détails, vous pouvez revenir vers + cette page.</p> + +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#configparsing">Fichier de configuration</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#hostmatching">Choix du serveur virtuel</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#tips">Trucs et astuces</a></li> +</ul><h3>Voir aussi</h3><ul class="seealso"><li><a href="ip-based.html">Support des serveurs virtuels à base +d'adresse IP</a></li><li><a href="name-based.html">Support des serveurs virtuels à base +de nom</a></li><li><a href="examples.html">Exemples de serveurs virtuels pour une +configuration courante</a></li><li><a href="mass.html">Hébergement virtuel de masse configuré +dynamiquement</a></li><li><a href="#comments_section">Commentaires</a></li></ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="configparsing" id="configparsing">Fichier de configuration</a></h2> + + <p>Un <em>serveur principal (main_server)</em> contient toutes + les définitions qui apparaissent en dehors des sections + <code><VirtualHost></code>.</p> + + <p>Les serveurs virtuels, aussi + appelés <em>vhosts</em> (pour virtual hosts), sont définis par les + sections <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>.</p> + + <p>Chaque directive <code>VirtualHost</code> comporte une ou + plusieurs adresses et des ports optionnels.</p> + + <p>Il est possible d'utiliser des noms d'hôtes dans la définition + d'un serveur virtuel, mais ils seront résolus en adresses IP au + démarrage du serveur, et si une résolution de nom échoue, cette + définition de serveur virtuel sera ignorée. Cette méthode est par + conséquent déconseillée.</p> + + <p>L'adresse peut + être spécifiée sous la forme <code>*</code>, ce qui conviendra à la + requête si aucun autre serveur virtuel ne possède l'adresse IP + explicite correspondant à celle de la requête.</p> + + <p>L'adresse qui apparaît dans la directive <code>VirtualHost</code> + peut être associée à un port optionnel. Si aucun port n'est + spécifié, il s'agit d'un port générique qui peut aussi être spécifié + comme <code>*</code>. Le port générique correspond à toutes les + valeurs de port.</p> + + <p>(Il ne faut pas confondre les numéros de port sur lesquels Apache + est en écoute avec les numéros de port spécifiés dans la directive + <code>VirtualHost</code> ; ces derniers ne servent qu'à définir le + <code>serveur virtuel</code> qui sera sélectionné pour traiter la + requête. Pour définir les ports sur lesquels Apache est en écoute, + utilisez la directive <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>). + </p> + + <p>L'ensemble des adresses (y compris les résultats multiples + <code>A</code> issus des requêtes DNS) est appelé <em>jeu + d'adresses</em> du serveur virtuel.</p> + + <p>Apache fait automatiquement sa sélection à partir de l'en-tête + HTTP <code>Host</code> fourni par le client, lorsque la + correspondance la plus exacte du point de vue adresse IP/port a lieu + pour plusieurs serveurs virtuels.</p> + + <p>La directive <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> peut + apparaître en quelque endroit de la définition d'un serveur. + Cependant, chaque occurrence écrase la précédente (pour ce serveur). + Si aucune directive <code>ServerName</code> n'est spécifiée, le + serveur tente de déterminer le nom du serveur à partir de l'adresse + IP.</p> + + <p>Le premier serveur virtuel à base de nom apparaissant dans le + fichier de configuration pour une paire IP:port donnée est + significatif car c'est lui qui sera utilisé pour toutes les requêtes + reçues sur cette adresse IP/port et pour laquelle aucun autre + serveur virtuel ne possède un ServerName ou un ServerAlias + correspondant. Il sera aussi utilisé pour toutes les connexions SSL + si le serveur ne supporte pas l'<a class="glossarylink" href="../glossary.html#servernameindication" title="voir glossaire">Indication du nom du serveur</a>.</p> + + <p>Tous les noms spécifiés au sein d'une section + <code>VirtualHost</code> sont traités comme un + <code>ServerAlias</code> (sans caractères génériques), mais ne sont + écrasés par aucune directive <code>ServerAlias</code>.</p> + + <p>Pour chaque serveur virtuel, diverses valeurs sont initialisées + par défaut. En particulier :</p> + + <ol> + <li>Dans le cas où un serveur virtuel ne contient pas de directives + <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/mpm_common.html#receivebuffersize">ReceiveBufferSize</a></code>, + ou <code class="directive"><a href="../mod/mpm_common.html#sendbuffersize">SendBufferSize</a></code>, + alors la valeur de chacun de ces paramètres est héritée de celle du + serveur principal. (C'est à dire, héritée de la valeur finale après + lecture de la configuration du serveur principal.)</li> + + <li>Les permissions par défaut sur les répertoires de chaque + serveur virtuel sont assemblées avec celles du serveur principal. + Elles concernent également toutes les informations de configuration + par répertoire pour tous les modules.</li> + + <li>Les configurations par serveur pour chaque module sont assemblées + à partir de celles du serveur principal.</li> + </ol> + + <p>L'essentiel des valeurs de configuration des serveurs virtuels + provient de valeurs par défaut issues du serveur principal. + Mais la position dans le fichier de configuration des directives + du serveur principal n'a pas d'importance -- l'ensemble de la + configuration du serveur principal est lu avant que ces valeurs par + défaut soient appliquées aux serveur virtuels. Ainsi, même si la + définition d'une valeur apparaît après celle d'un serveur virtuel, + cette valeur peut affecter la definition du serveur virtuel.</p> + + <p>Dans le cas où le serveur principal n'a pas de <code>ServerName</code> + à ce stade, le nom de la machine sur laquelle tourne le programme + <code class="program"><a href="../programs/httpd.html">httpd</a></code> est utilisé à sa place. Nous appellerons + <em>jeu d'adresses du serveur principal</em> les adresses IP + renvoyées par une résolution DNS sur le <code>ServerName</code> + du serveur principal.</p> + + <p>Pour tous les champs <code>ServerName</code> non définis, dans + le cas d'une configuration en serveur virtuel par nom, la valeur + adoptée par défaut est la première adresse donnée dans la section + <code>VirtualHost</code> qui définit le serveur virtuel.</p> + + <p>Si un serveur virtuel contient la valeur magique + <code>_default_</code>, il fonctionne sur le même <code>ServerName</code> + que le serveur principal.</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">Choix du serveur virtuel</a></h2> + + <p>À la réception d'une requête, le serveur procède comme suit pour + déterminer quel serveur virtuel utiliser :</p> + + <h3><a name="hashtable" id="hashtable">Recherche de l'adresse IP</a></h3> + + <p>Lors d'une première connexion sur une adresse/port, le serveur + recherche toutes les directives <code>VirtualHost</code> qui + possèdent la même adresse IP/port.</p> + + <p>S'il n'y a aucune correspondance exacte pour cette adresse/port, + la recherche s'effectue sur la valeur générique (<code>*</code>).</p> + + <p>Si aucune correspondance n'est enfin trouvée, la requête sera + servie par le serveur principal.</p> + + <p>S'il existe des définitions <code>VirtualHost</code> pour + l'adresse IP, l'étape suivante consiste à déterminer si nous avons à + faire à un serveur virtuel à base de nom ou d'adresse IP.</p> + + + + <h3><a name="ipbased" id="ipbased">Serveur virtuel par IP</a></h3> + + <p>Si une seule section <code>VirtualHost</code> présente la + meilleure correspondance avec la paire adresse IP/port, aucune + action n'est entreprise et la requête est + traitée par le serveur virtuel qui correspond.</p> + + + + <h3><a name="namebased" id="namebased">Serveur virtuel par nom</a></h3> + + <p>Si plusieurs sections <code>VirtualHost</code> présentent la + meilleure correspondance avec la paire adresse IP/port, le terme + "liste" dans les étapes suivantes fait référence à la liste des + serveurs virtuels qui correspondent, selon l'ordre dans lequel ils + apparaissent dans le fichier de configuration.</p> + + <p>Si la connexion utilise SSL, si le serveur supporte l'<a class="glossarylink" href="../glossary.html#servernameindication" title="voir glossaire">Indication de nom de serveur</a>, + et si la négociation du client SSL inclut l'extension TLS dans le + nom d'hôte requis, alors ce nom d'hôte sera utilisé par la suite, tout + comme un en-tête <code>Host:</code> aurait été utilisé dans le cas + d'une connexion non-SSL. Si ces conditions ne sont pas réunies, le + premier serveur virtuel à base de nom dont l'adresse correspond sera + utilisé pour les connexions SSL. Ceci est important car c'est le + serveur virtuel qui détermine quel certificat le serveur va utiliser + pour la connexion.</p> + + <p>Si la requête contient un en-tête <code>Host:</code>, on + recherche dans la liste le premier serveur virtuel dont le + <code>ServerName</code> ou le <code>ServerAlias</code> correspond, + et c'est celui-ci qui va traiter la requête. Un en-tête + <code>Host:</code> peut comporter un numéro de port mais Apache + l'ignore systématiquement et utilise toujours le + port sur lequel il a effectivement reçu la requête.</p> + + <p>Le premier serveur virtuel du fichier de configuration qui + possède l'adresse spécifiée est prioritaire et intercepte toutes les + requêtes à destination d'un nom de serveur inconnu, ou toute requête + sans en-tête <code>Host:</code> (comme les requêtes HTTP/1.0).</p> + + + + <h3><a name="persistent" id="persistent">Connexions persistantes</a></h3> + + <p>La <em>recherche par adresse IP</em> décrite ci-avant n'est faite + qu'<em>une fois</em> pour chaque session TCP/IP, alors que la + <em>recherche par nom</em> est réalisée pour <em>chaque</em> requête au + cours d'une connexion persistante (KeepAlive). En d'autres termes, + il est possible pour un client de faire des requêtes sur + différents serveurs virtuels par nom, au cours d'une unique + connexion persistante.</p> + + + + <h3><a name="absoluteURI" id="absoluteURI">URI absolu</a></h3> + + <p>Au cas où l'URI de la requête est absolu, et que son nom de + serveur et son port correspondent au serveur principal (ou l'un + des serveurs virtuels configurés), <em>et</em> qu'ils correspondent + à l'adresse et au port de la requête, alors l'URI est amputé + de son préfixe protocole/nom de serveur/port et traité par le + serveur correspondant (principal ou virtuel). Si cette correspondance + n'existe pas, l'URI reste inchangé et la requête est considérée + comme une requête d'un serveur mandataire (proxy).</p> + + +<h3><a name="observations" id="observations">Observations</a></h3> + + <ul> + <li>La sélection d'un serveur virtuel en fonction de son nom est + un processus qui intervient après la sélection par le serveur du + serveur virtuel qui correspond le mieux du point de vue adresse + IP/port.</li> + + <li>Si vous ne tenez pas compte de l'adresse IP à laquelle le + client s'est connecté, indiquez un caractère "*" comme adresse + pour tous les serveurs virtuels, et la sélection du serveur + virtuel en fonction du nom s'appliquera alors à tous les serveurs + virtuels définis.</li> + + <li>Les vérifications sur <code>ServerName</code> et + <code>ServerAlias</code> ne sont jamais + réalisées pour les serveurs virtuels par IP.</li> + + <li>Seul l'ordre des serveurs virtuels par nom + pour une adresse donnée a une importance. Le serveur virtuel + par nom qui est présent en premier dans la configuration se + voit attribué la priorité la plus haute pour les requêtes + arrivant sur son jeu d'adresses IP.</li> + + <li>Le numéro de port contenu dans l'en-tête <code>Host:</code> n'est jamais utilisé + pour les tests de correspondances. Apache ne prend en compte + que le numéro de port sur lequel le client a envoyé la requête.</li> + + <li>Si deux serveurs virtuels partagent la même adresse, la + sélection se fera implicitement sur le nom. Il s'agit d'une + nouvelle fonctionnalité de la version 2.3.11.</li> + + <li>Le serveur principal ne sert les requêtes que + lorsque l'adresse IP et le port demandés par le client ne + correspondent à aucun serveur virtuel (y compris un serveur + virtuel <code>*</code>). En d'autres termes, le serveur + principal n'est utile que pour les combinaisons adresse/port + non spécifiées (sauf quand un serveur virtuel <code>_default_</code> + correspond au port).</li> + + <li>Il ne faut jamais employer de noms DNS dans des directives + <code>VirtualHost</code>, car cela oblige le serveur a s'appuyer + sur le DNS au moment du démarrage. De plus, vous vous exposez + à des problèmes de sécurité si vous n'avez pas la maîtrise du + DNS pour la totalité de vos domaines. Voir la documentation + <a href="../dns-caveats.html">disponible ici</a>, ainsi que + les deux points précisés ci-après.</li> + + <li>Un nom de serveur <code>ServerName</code> devrait toujours + être indiqué pour chaque serveur virtuel. Sans cela, une + résolution DNS est nécessaire pour chaque serveur virtuel.</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">Trucs et astuces</a></h2> + + <p>En plus des points évoqués sur la page des + <a href="../dns-caveats.html#tips">problèmes liés au DNS</a>, + voici quelques points intéressants :</p> + + <ul> + <li>Toujours positionner les définitions relatives au serveur + principal avant toute définition <code>VirtualHost</code>. + (Ceci améliore grandement la lisibilité de la configuration + -- la manière dont la configuration est interprétée après la + lecture des fichiers ne met pas en évidence le fait que les + définitions positionnées avant et surtout après les serveurs + virtuels peuvent impacter le fonctionnement de tous les + serveurs virtuels.)</li> + + </ul> + +</div></div> +<div class="bottomlang"> +<p><span>Langues Disponibles: </span><a href="../en/vhosts/details.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../fr/vhosts/details.html" title="Français"> fr </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="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Commentaires</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/vhosts/details.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Autorisé sous <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/vhosts/details.html.ko.euc-kr b/docs/manual/vhosts/details.html.ko.euc-kr new file mode 100644 index 0000000..ca5088a --- /dev/null +++ b/docs/manual/vhosts/details.html.ko.euc-kr @@ -0,0 +1,412 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head> +<meta content="text/html; charset=EUC-KR" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>°¡»óÈ£½ºÆ® ã±â¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸í - Apache HTTP Server Version 2.4</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" /> +<script src="../style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">¸ðµâ</a> | <a href="../mod/directives.html">Áö½Ã¾îµé</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">¿ë¾î</a> | <a href="../sitemap.html">»çÀÌÆ®¸Ê</a></p> +<p class="apache">Apache HTTP Server Version 2.4</p> +<img alt="" src="../images/feather.png" /></div> +<div class="up"><a href="./"><img title="<-" 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.4</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="../fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Français"> fr </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"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#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><h3>Âü°í</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="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°¡ Àý´ë URIÀÌ°í Ŭ¶óÀ̾ðÆ®°¡ º¸³½ ¿äûÀÇ + È£½ºÆ®¸í°ú Æ÷Æ®°¡ ÁÖ¼¹ö³ª ƯÁ¤ °¡»óÈ£½ºÆ®¿¡ ÇØ´çÇϸé, + ±× ÁÖ¼¹ö ȤÀº °¡»óÈ£½ºÆ®´Â 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="../fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Français"> fr </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="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/vhosts/details.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">¸ðµâ</a> | <a href="../mod/directives.html">Áö½Ã¾îµé</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">¿ë¾î</a> | <a href="../sitemap.html">»çÀÌÆ®¸Ê</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/vhosts/details.html.tr.utf8 b/docs/manual/vhosts/details.html.tr.utf8 new file mode 100644 index 0000000..ef4297d --- /dev/null +++ b/docs/manual/vhosts/details.html.tr.utf8 @@ -0,0 +1,319 @@ +<?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> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Sanal Konak Eşlemenin Derinliğine İncelenmesi - Apache HTTP Sunucusu Sürüm 2.4</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" /> +<script src="../style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modüller</a> | <a href="../mod/directives.html">Yönergeler</a> | <a href="http://wiki.apache.org/httpd/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.4</p> +<img alt="" src="../images/feather.png" /></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.4</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="../fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Français"> fr </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>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.</p> + + <p>Çoğu kullanıcı hangi türü kullanacağına karar vermek için önce <a href="name-based.html#namevip">İsme dayalı ve IP’ye dayalı Sanal + Konak</a> bölümünü, sonra <a href="name-based.html">İsme Dayalı Sanal + Konak Desteği</a> veya <a href="ip-based.html">IP’ye Dayalı Sanal Konak + Desteği</a> belgesini okumalı ve <a href="examples.html">bazı + örneklere</a> göz atmalıdır.</p> + + <p>Bunlardan sonra tüm ayrıntıları anlamak isterseniz tekrar bu sayfaya + gelebilirsiniz.</p> + +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#configparsing">Yapılandırma Dosyası</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><h3>Ayrıca bakınız:</h3><ul class="seealso"><li><a href="ip-based.html">IP’ye Dayalı Sanal Konak Desteği</a></li><li><a href="name-based.html">İsme Dayalı Sanal Konak Desteği</a></li><li><a href="examples.html">Çok Kullanılan Sanal Konak Örnekleri</a></li><li><a href="mass.html">Devingen olarak Yapılandırılan Kitlesel Sanal Barındırma</a></li><li><a href="#comments_section">Yorumlar</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ı</a></h2> + + <p>Bu belgede <code><VirtualHost></code> bölümleri dışında kalan + tanımlardan bahsederken <em>ana_sunucu</em> diyeceğiz.</p> + + <p><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>Her <code>VirtualHost</code> bölümü en az bir adres ve isteğe bağlı + portlar içerir.</p> + + <p>Sanal konak tanımlarının içindeki IP adreslerinin yerine konak isimleri + kullanılabilir, fakat bunlar başlatma sırasında çözümleneceklerinden + çözümlemedeki bir başarısızlık bu sanal konak tanımlarının yoksayılması + ile sonuçlanacaktır. Bu bakımdan önerilmez.</p> + + <p><code>VirtualHost</code> yönergesinde görünen her adresin seçimlik bir + portu olabilir. Eğer bir port belirtilmemişse, port olarak <code>*</code> + belirtilmiş gibi bütün portlar dinlenir.</p> + + <p>(<code>VirtualHost</code> yönergesinde belirtilen port numaraları Apache + httpd'nin dinleyeceği port numaraları olarak yorumlanmaz, sadece bir + isteği işleme sokarken hangi <code>VirtualHost</code> bölümünün + seçileceğini belirlerler. Sunucunun dinleyeceği adresleri ve portları + belirtmek için <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + yönergesini kullanın.)</p> + + <p>Adreslerin tamamını (DNS sorgularındaki çoklu sonuçlar dahil) içeren + kümeye <em>sankonların adres kümesi</em> denir.</p> + + <p>Apache httpd, bir IP adresi ve port birleşimi için en belirgin + eşleşmelerin listelendiği çok sayıdaki sanal konak arasında ayırdedici + olarak istemci tarafından sağlanan HTTP <code>Host</code> başlığını + kullanır.</p> + + <p><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> yönergesi sunucu + tanımının içinde herhangi bir yerde görünebilirse de her göründüğü yerde + bir öncekini iptal eder. Hiç <code>ServerName</code> belirtilmemişse, + Apache httpd, sunucu ismini sunucunun IP adresinden saptamaya + çalışır.</p> + + <p>Belli bir IP adresi ve port çifti için yapılandırma dosyasındaki ilk + isme dayalı sankon önemlidir, çünkü başka hiçbir sankonun ServerName veya + ServerAlias yönergesi ile eşleşmeyen bu adres ve port çifti için alınmış + tüm isteklerde bu sankon kullanılır. Ayrıca, sunucunun <a class="glossarylink" href="../glossary.html#servernameindication" title="sözlüğe bakınız">Sunucu İsmi Belirtimi</a>ni + desteklemediği durumlarda tüm SSL bağlantıları için bu sankon + kullanılır.</p> + + <p><code>VirtualHost</code> içindeki isimlerin sırası (jokersiz) bir + <code>ServerAlias</code> gibi ele alınır (fakat hiçbir + <code>ServerAlias</code> yönergesi ile geçersiz kılınmaz).</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/mpm_common.html#receivebuffersize">ReceiveBufferSize</a></code> ve + <code class="directive"><a href="../mod/mpm_common.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">IP adresi aranır</a></h3> + + <p>Bir adres ve port için bağlantı ilk alındığında Apache httpd tüm + <code>VirtualHost</code> tanımlarında bu çifti arar.</p> + + <p>Arama başarısız olursa <code>*</code> (herşey) eşleşmelerine + bakılır.</p> + + <p>Bir eşleşme bulunamazsa hizmet ana sunucudan sunulur.</p> + + <p>Arama sonucunda bu IP adresi için bulunmuş <code>VirtualHost</code> + tanımları varsa 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 en iyi eşleşme olarak saptanmış IP adresi ve port çiftini içeren + sadece bir <code>VirtualHost</code> yönergesi varsa 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>Eğer en iyi eşleşme olarak saptanmış IP adresi ve port çiftini içeren + birden fazla <code>VirtualHost</code> yönergesi varsa, sonraki + adımlardaki "liste" eşleşen sankonların listesi olup sankonlar listede + yapılandırma dosyasındaki yerlerine göre sıralanırlar.</p> + + <p>Bağlantı SSL kullanıyorsa, sunucunun <a class="glossarylink" href="../glossary.html#servernameindication" title="sözlüğe bakınız">Sunucu İsmi Belirtimi</a>ni + desteklediği durumlarda SSL istemci uzlaşımı, istenen konak ismiyle + birlikte TLS eklentisini de içeriyorsa, konak ismi, SSL olmayan + bağlantılardaki <code>Host:</code> başlığı kullanımına benzer şekilde + aşağıdaki gibi kullanılır. Aksi takdirde, SSL bağlantıları için adresin + eşleştiği ilk isme dayalı sankon kullanılır. Sunucunun bağlantı için + hangi sertifikayı kullanacağını sankon belirlediği için bu önemlidir.</p> + + <p>İstek bir <code>Host:</code> başlık alanı içeriyorsa, listede + <code>ServerName</code> veya <code>ServerAlias</code> alanı başlık alanı + ile eşleşen ilk sankona bakılır. <code>Host:</code> alanı bir port + içerebilirse de Apache httpd bunu yoksayarak daima istemcinin isteği + gönderdiği portu gerçek port kabul eder.</p> + + <p>Yapılandırma dosyasındaki belirtilen IP adresiyle eşleşen ilk sankon en + yüksek önceliğe sahiptir ve sunucu ismi bilinmeyen ve (bir HTTP/1.0 + isteği gibi) <code>Host:</code> başlık alanı içermeyen istekleri de + yakalar.</p> + + + + <h3><a name="persistent" id="persistent">Kalıcı bağlantılar</a></h3> + + <p>Yukarıda açıklanan <em>IP araması</em> belli bir TCP/IP oturumunda + <em>bir</em> defaya mahsus yapıldığı halde bir kalıcı/KeepAlive bağlantı + sırasında <em>her</em> istek için ayrı bir <em>arama</em> 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>İsme dayalı sanal konak işlemleri, sunucunun en iyi eşleşen IP'ye + dayalı sanal konağı seçmesinin ardından uygulanır.</li> + + <li>İstemcinin hangi IP adresine bağlandığını umursamıyorsanız, sanal + konaklarınızda adres olarak "*" kullanın, böylece yapılandırılmış + sankonların hepsine isme dayalı sanal konak işlemleri uygulanır.</li> + + <li>Bir IP’ye dayalı sankon için asla <code>ServerAlias</code> ve + <code>ServerPath</code> değerine bakılmaz.</li> + + <li>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>Eşleştirme işlemi sırasında <code>Host:</code> + başlık alanında belirtilen port asla kullanılmaz. Apache httpd daima + istemcinin isteği gönderdiği gerçek portu kullanır.</li> + + <li>Eğer aynı IP adresine sahip IP’ye dayalı iki sankon varsa, bunlara + örtük olarak isme dayalı sanal konak işlemleri uygulanır. 2.3.11 + sürümünden beri yeni davranış şekli budur.</li> + + <li>Ana_sunucunun bir isteğe hizmet sunabilmesi için istemcinin + bağlandığı IP adresi ve port hiçbir yerde belirtilmemiş ve + 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>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> + </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="../fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Français"> fr </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 class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Yorumlar</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/vhosts/details.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2023 The Apache Software Foundation.<br /><a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> 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="http://wiki.apache.org/httpd/FAQ">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritası</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file |