Switch branches/tags
Nothing to show
Find file
Fetching contributors…
Cannot retrieve contributors at this time
86 lines (59 sloc) 3.99 KB
<!doctype html>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<script src=""></script>
<script src="javascripts/respond.js"></script>
<!--[if lt IE 9]>
<script src="//"></script>
<!--[if lt IE 8]>
<link rel="stylesheet" href="stylesheets/ie.css">
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<div class="wrapper">
<div id="title">
<p>localhost testing done right</p>
<p>Save this URL, memorize it, write it on a sticky note, tweet it, tell your colleagues about it!</p>
<p> (<a href=""></a>)</p>
<p>* (<a href=""></a>)</p>
<p>If you do any testing on your local system you’ve probably created hosts file entries (c:\windows\system32\drivers\etc\hosts) for different testing domains and had them point back to This works great but it requires just a bit of extra effort.</p>
<p>This trick is so obvious, so simple, and yet so powerful. I wouldn’t be surprised if there are other domain names like this out there, but I haven’t run across them yet so I just ordered the domain name which I’ll keep available for the internet community to use.</p>
<p>Here’s how it works. The entire domain name—and all wildcard entries—point to So without any changes to your host file you can immediate start testing with a local URL.</p>
<p>You name it, just use any * URL that you dream up and it will work for testing on your local system.</p>
<p><del>Another great advantage of using an internet DNS name is that we have a real SSL certificate for it. That means there's no more messing about with self-signed, untrusted certificates during development.</del></p>
<p><del>You can download the public and private key here: <a href=""></a></del></p>
<p><del>If you use this key, please add a calendar reminder to come back here before May 18<sup>th</sup> 2013 to download the renewed certificate.</del></p>
<p><strong>Update:</strong> The CA revoked our certificate because they considered the private key to be compromised. I'm not entirely sure how they detected this, but they refuse to reissue it. My best idea is to get a new key elsewhere and make the key accessible but through a CAPTCHA or something so that a bot can't discover it. Any better ideas would be appreciated.</p>
<h2>More details</h2>
<p>Read the introduction by <a href="">Scott Forsyth</a></p>
<p>Idea: <a href="">Scott Forsyth</a>, <a href="">Imar Spaanjaars</a></p>
<p>DNS and SSL: <a href="">Tatham Oddie</a></p>
<p>Site: <a href="">Brendan Forster</a>, <a href="">Aaron Powell</a></p>
<p>If you'd like to contribute to this site, <a href="">fork us on GitHub</a>.</p>
<!--[if !IE]><script>fixScale(document);</script><!--<![endif]-->