3 ms·
It must be a bug in their back-end infrastructure; there's no general reason why 'naked' domains should be any more prone to TCP connection problems than any ot
by gojomo 18y ago
It must be a bug in their back-end infrastructure; there's no general reason why 'naked' domains should be any more prone to TCP connection problems than any other domains. (TCP doesn't even care about domain names, and even in DNS, 'naked' 2nd-level domains are functionally equivalent to 3rd-level domains, 4th-level domains, etc.).
There is at least one legitimate reason using www (or any other subdomain) can be beneficial -- to isolate application cookies from your base domain, to assist caching. See here for details:
http://developer.yahoo.com/performance/rules.html#cookie_free http://developer.yahoo.com/performance/rules.html#cookie_fre...
However, you're probably far from needing to worry about that, and also segregating your static, highly-cacheable data to another domain is another way to get the same benefit.
(I tend to prefer non-www domains, too.)
- riobard 18y agoThanks for the info! I think the cookie/cache reason explained why virtually all major websites (millions hits/day) redirect naked domain to "www." subdomain. I also found the following info from here http://blog.bigcurl.de/2008/08/redirect-naked-domains-to-subdomain-in.html http://blog.bigcurl.de/2008/08/redirect-naked-domains-to-sub... "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." So using "www." domain for GAE seems to be a better solution if one wants faster access/response.