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">www.my-fake-site.com</a><br><br>(press enter twice)<br><br>You can also test SSL from the command line the same way with a little help:<br>
<a href="http://www.bearfruit.org/2008/04/17/telnet-for-testing-ssl-https-websites/">http://www.bearfruit.org/2008/04/17/telnet-for-testing-ssl-https-websites/</a><br><br><div class="gmail_quote">On Thu, May 13, 2010 at 7:09 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;">Say you have a name-based server configuration, .. the only way to test<br>
a site is to fake your local DNS in order to pass the correct URL in the<br>
link to the IP of your test server.<br>
<br>
That works fine if you are controlling the machine [i.e. edit the hosts<br>
file and substitute the test IP for that domain name], .. but how do you<br>
'give' a URL to the client to view?<br>
<br>
Any redirection would break the test as the first time you click a link on<br>
the test site it would direct to the 'real' site.<br>
<br>
Lee<br>
_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</blockquote></div><br><br clear="all"><br>-- <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>