You basically need to have a separate server be able to handle the root 
(naked) domain and serve up a SSL certificate. A lot of services, such as 
Google App Engine do not do this for you, so you need something else 
capable of doing it.

You could also use it has free redirects up to a 
certain amount.

*Disclaimer: I am the developer behind the service, I understand self 
promotion is wrong and that is not my intention, this thread has been 
referenced a lot by people and I want to offer a modern alternative.*

On Sunday, 22 July 2012 14:13:23 UTC-3, Thomas Wiradikusuma wrote:
> Hi guys,
> I'm using GAE's official SSL SNI support in my app. Opening 
> is fine. But opening 
> (naked domain) gives warning (in Chrome) that essentially says, "Hey, the 
> cert is not for, it's Google's". Non-SSL (
> properly redirects to www. My appid is "neytap".
> So I got creative, I logged in to enom (from Google Apps) then removed all 
> A mappings (@ -> google IPs) and replaced them with one URL Redirect (@ -> 
> Non-SSL naked domain is still working, but 
> now Chrome gives me "This webpage is not available. Google Chrome's 
> connection attempt to was rejected. The website may be 
> down, or your network may not be properly configured." when I try to access 
> Anyone know how to properly redirect naked https domain in GAE? I notice 
> there is similar question in this forum (
> but it's 2009 and uses unofficial SSL support.

You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit
  • [google-appengine] Re:... Steve Verbeek

Reply via email to