Say you want to deploy an app on Google App Engine under your own domain name. Historicaly users were trained to enter the subdomain www before your naked domain name, so you configure this one too.
Both domains point to the same application.
The problem with this approach is that both domains will work, which can lead to inconsitent results.
You want to redirect one to the other and settle on a single domain but for now it is not possible to configure a redirect directly in Goole App Engine.
That is why I wrote redirector. It is a little application which redirects all the apps in your Google Apps account from a naked domain name to a subdomain.
Eg. bigcurl.de --> www.bigcurl.de
If you want it can also do this vice versa but be aware that you are not taking advantage of Googles geocaching mechanism with this approach.
One deployed application is sufficent to provide redirect service for all other applications in your Google Apps account.
You can find the code and setup instructions here.
Posts
3 Kommentare:
Why do you say it leads to inconsistent result? I like to browse withouth the www. subdomain. A lot of people like the www. part.
Why not let everyone browse the way they like?
What downsides could this have?
It has todo with caching your site using a CDN and with how google indexes your site. Finding both domains it thinks it is duplicated content.
I totaly support http://no-www.org/ but this is the way the internet is, at least you redirect from the naked domain.
Here is the simple way
http://www.ialwayscapital.com/2009/05/redirectforward-yahoo-naked-domainurl.html
Post a Comment