www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2026-01-06 09:01:14 +03:00
Code Activity

Typo.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97159 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Yoshiki Hayashi
2002-10-09 10:15:36 +00:00
parent 795c3a0302
commit d949e029bf
2 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/manual/dns-caveats.html.en
View File

@@ -92,18 +92,18 @@
<p>Suppose that you've assigned 10.0.0.1 to
<code>www.abc.dom</code> and 10.0.0.2 to
<code>www.def.dom</code>. Furthermore, suppose that
<code>def.com</code> has control of their own DNS. With this
config you have put <code>def.com</code> into a position where
they can steal all traffic destined to <code>abc.com</code>. To
<code>def.dom</code> has control of their own DNS. With this
config you have put <code>def.dom</code> into a position where
they can steal all traffic destined to <code>abc.dom</code>. To
do so, all they have to do is set <code>www.def.dom</code> to
10.0.0.1. Since they control their own DNS you can't stop them
from pointing the <code>www.def.com</code> record wherever they
from pointing the <code>www.def.dom</code> record wherever they
wish.</p>
<p>Requests coming in to 10.0.0.1 (including all those where
users typed in URLs of the form
<code>http://www.abc.dom/whatever</code>) will all be served by
the <code>def.com</code> virtual host. To better understand why
the <code>def.dom</code> virtual host. To better understand why
this happens requires a more in-depth discussion of how Apache
matches up incoming requests with the virtual host that will
serve it. A rough document describing this <a href="vhosts/details.html">is available</a>.</p>

12
docs/manual/dns-caveats.xml
View File

@@ -99,18 +99,18 @@
<p>Suppose that you've assigned 10.0.0.1 to
<code>www.abc.dom</code> and 10.0.0.2 to
<code>www.def.dom</code>. Furthermore, suppose that
<code>def.com</code> has control of their own DNS. With this
config you have put <code>def.com</code> into a position where
they can steal all traffic destined to <code>abc.com</code>. To
<code>def.dom</code> has control of their own DNS. With this
config you have put <code>def.dom</code> into a position where
they can steal all traffic destined to <code>abc.dom</code>. To
do so, all they have to do is set <code>www.def.dom</code> to
10.0.0.1. Since they control their own DNS you can't stop them
from pointing the <code>www.def.com</code> record wherever they
from pointing the <code>www.def.dom</code> record wherever they
wish.</p>
<p>Requests coming in to 10.0.0.1 (including all those where
users typed in URLs of the form
<code>http://www.abc.dom/whatever</code>) will all be served by
the <code>def.com</code> virtual host. To better understand why
the <code>def.dom</code> virtual host. To better understand why
this happens requires a more in-depth discussion of how Apache
matches up incoming requests with the virtual host that will
serve it. A rough document describing this <a
@@ -206,4 +206,4 @@
been deployed widely enough to be put into use on critical
webservers.</p>
</section>
</manualpage>
</manualpage>