<div class="gmail_quote">On Thu, May 13, 2010 at 7:48 PM, L. V. Lammert <span dir="ltr"><<a href="mailto:lvl@omnitec.net">lvl@omnitec.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thu, 13 May 2010, Matthew Nuzum wrote:<br>
<br>
> Hi, if you need simple testing you can use telnet.<br>
><br>
> $ telnet 11.22.33.44 80<br>
> GET / HTTP/1.1<br>
> Host: <a href="http://www.my-fake-site.com" target="_blank">www.my-fake-site.com</a><br>
><br>
</div>Thanks for the suggestioh, but these are name-based hosts, ... simply<br>
telnetting to the IP is the same as using the IP in a browser - it gets<br>
the first site configured on the server [which is another issue entirely<br>
- making sure the 'Site is not on this server' message is the first in<br>
line <G>!].<br>
<div><div></div><div class="h5"><br>
<br></div></div></blockquote><div><br><br>Nope.<br><br>Name-based hosts work off the Host http header. You can telnet to the IP but then you have to enter the Host: header after the GET request. <br><br></div></div>-- <br>
Matthew Nuzum<br>newz2000 on freenode, skype, linkedin, <a href="http://identi.ca">identi.ca</a> and twitter<br><br>"Do not seek to follow in the footsteps of the wise. Seek what they sought." –Matsuo Bashō<br>