I made this: http://wwwizer.com and today Google announced the same thing.

A little bit of history.

Two years ago it started as just a simple redirect. Point your naked (www-less) domain to my IP (174.129.25.170) and every request for any url without "www." in front gets redirected to the same URL but with www in front. Really 4 lines of nginx config.

It is quite handy if you host website on Google App Engine or on Google Sites because if you are using your own domain it doesn't work without www subdomain. www.example.com works, example.com - doesn't. You need to make CNAME to ghs.google.com for your domain to work but you can't do this with naked (or root, or apex) domain.

It got popular (at least in my terms). 4100 websites are using it. 350000+ redirects a day.

So two months ago I decided to "expand" and maybe get some, you know, profit.

SSL for the Cloud. New product. Yay! You get dedicated IP, SSL certificate, point your domain to this IP and it proxies your app (or any URL of your choice actually). App Engine did not have SSL support at the moment, a lot of people were complaining but it looked like there were no progress on this matter.

And today comes this "Announcing SSL for Custom Domains" http://groups.google.com/group/google-appengine/browse_thread/thread/d7fb200cbe9d2010?pli=1

So what do you think I should do now?