|
117 | 117 | <p>Suppose that you've assigned 192.0.2.1 to |
118 | 118 | <code>www.example1.dom</code> and 192.0.2.2 to |
119 | 119 | <code>www.example2.dom</code>. Furthermore, suppose that |
120 | | - <code>example2.dom</code> has control of their own DNS. With this |
121 | | - config you have put <code>example2.dom</code> into a position where |
122 | | - they can steal all traffic destined to <code>example1.dom</code>. To |
123 | | - do so, all they have to do is set <code>www.example2.dom</code> to |
124 | | - 192.0.2.1. Since they control their own DNS you can't stop them |
125 | | - from pointing the <code>www.example2.dom</code> record wherever they |
| 120 | + <code>example1.dom</code> has control of their own DNS. With this |
| 121 | + config you have put <code>example1.dom</code> into a position where |
| 122 | + they can steal all traffic destined to <code>example2.dom</code>. To |
| 123 | + do so, all they have to do is set <code>www.example1.dom</code> to |
| 124 | + 192.0.2.2. Since they control their own DNS you can't stop them |
| 125 | + from pointing the <code>www.example1.dom</code> record wherever they |
126 | 126 | wish.</p> |
127 | 127 |
|
128 | | - <p>Requests coming in to 192.0.2.1 (including all those where |
| 128 | + <p>Requests coming in to 192.0.2.2 (including all those where |
129 | 129 | users typed in URLs of the form |
130 | | - <code>http://www.example1.dom/whatever</code>) will all be served by |
131 | | - the <code>example2.dom</code> virtual host. To better understand why |
| 130 | + <code>http://www.example2.dom/whatever</code>) will all be served by |
| 131 | + the <code>example1.dom</code> virtual host. To better understand why |
132 | 132 | this happens requires a more in-depth discussion of how httpd |
133 | 133 | matches up incoming requests with the virtual host that will |
134 | 134 | serve it. A rough document describing this <a href="vhosts/details.html">is available</a>.</p> |
|
0 commit comments