It turns out that the application for
Google App Engine can not be connected to the domain root, only to a subdomain like www. It used to be possible, but then for some reason it was covered up.
Many do not like this , but with the available means nothing is done. The support offers to order web forwarding from the registrar, but this usually costs money, and free forwarding on the home ADSL channel makes it impossible to use GAE with its high availability to make any sense.
There is a worse solution that I have long used for some other purposes: register a blog with
Tumblr , attach it to the desired domain (they have no restrictions), go to the appearance setting, edit the template, delete all the excess
1 and do
HTML redirection . Free and reliable enough (better than home ADSL line). In order for the tumblers not to be offended by this, they can leave a comment with an apology in the code.
Google itself aggravates the current situation with some technical difficulties. I understand everything, it happens, but why would he not find a free IP address in the storeroom and make a universal wwwizer on it? Let him respond to any requests by adding the www prefix if it doesn’t exist (and 404 if it already exists). Cheap and quite acceptable, it seems to me.
')
-
- You must leave
{block:Posts}{/block:Posts}
inside <body>, otherwise the tumblr will complain about the incorrect skin.