title: Heroku Custom Domain SSL Warning
body: <p>I'm trying to set up a GoDaddy-purchased custom domain for my Heroku Deployed app. I got it to work so that the www.<em>_</em>.com forwards correctly to my herokuapp (cedar), but 1) my attempts to get the naked address haven't worked, and 2) when I attempt to log on to the custom domain for the first time, I get a browser-dependent version of this warning, which I definitely don't want:</p>
  
  <blockquote>
    <p>"This is probably not the site you are looking for! ... You should
    probably not proceed... In this case, the address listed in the
    certificate does not match the address of the website your browser
    tried to go to. One possible reason for this is that your
    communications are being intercepted by an attacker who is presenting
    a certificate for a different website, which would cause a mismatch.
    Another possible reason is that the server is set up to return the
    same certificate for multiple websites, including the one you are
    attempting to visit, even though that certificate is not valid for all
    of those websites. Google Chrome can say for sure that you reached
    *.herokuapp.com, but cannot verify that that is the same site as  which you intended to reach. If you proceed, Chrome
    will not check for any further name mismatches."</p>
  </blockquote>
  
  <p>The HTTPS before the custom address is crossed out in red. Obviously, I don't want to scare visitors away with this warning, but I also don't want to have to buy an SSL certificate through GoDaddy. I don't really need SSL encryption. Any idea how to forward the naked site and get this to work without scaring off visitors?</p>
  
  <p>Thanks. I know this is a sort of vague question and not Stack Overflow's specialty, but I've fished around google/Heroku help/GoDaddy and found very little up-to-date info that could help me sort through all this.</p>
  
  <p>Sasha</p>