Re:6,953 reasons why I still let Google host jQuery for me
by estel on Tuesday September 21, 2010 @05:11PM
(#1714131)
I've started to see some best-practice-if-you-ignore-user-expectation guides out there which say that allowing the domain to ignore the www is Not A Good Idea. I don't really know why this is the case, though.
Re:6,953 reasons why I still let Google host jQuery for me
by eli on Tuesday September 21, 2010 @06:48PM
(#1714407)
I've seen people worry that if incoming links are split between foo.com and www.foo.com, it will affect Google's ranking of your site.
I don't think this is true and, anyway, the right solution would be to redirect one to the other.
Re:6,953 reasons why I still let Google host jQuery for me
by mike-cardwell on Wednesday September 22, 2010 @04:25AM
(#1715534)
Google treats http://www.example.com/foo.html as a different page to http://example.com/foo.html and it is completely right to do so because they could be different pages.
You can use rel="canonical" to get around this, or a http redirect.
Re:6,953 reasons why I still let Google host jQuery for me
by alanh on Wednesday September 22, 2010 @04:38AM
(#1715563)
Best practices concerning www, including rel="canonical" and redirects:
Re:6,953 reasons why I still let Google host jQuery for me
by Encosia on Tuesday September 21, 2010 @11:59PM
(#1715127)
To be clear, I did not adjust any of my numbers to include an extrapolated extra 10%. Any numbers you see in my post are based on direct observation of a script tag's src attribute.
At first, that may seem like an awful lot of potential error. However, the one thing all of these inaccuracies have in common is that none of them favor the case for using a public CDN.
I would have to disagree with the last paragraph there. I think that if one is so incompetent that his page is not available without the "www.", that there is a very strong chance that such person hasn't heard of a CDN. So domains that are not working without the "www." are, in my opinion, favouring the non CDN way.