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

PR50388: the hijacking domain needs to be first if you're going to cause

Browse Source 
a collision on the interface.



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1040785 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Eric Covener
2010-11-30 21:43:36 +00:00
parent c163534ebc
commit dd6a2cc336
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

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