It's always best to force either www. or no www. It's up to you which one you choose, but otherwise you will face issues with Google thinking you have duplicate content.
(2013-01-15, 03:38 PM)Euan T. Wrote: [ -> ]It's always best to force either www. or no www. It's up to you which one you choose, but otherwise you will face issues with Google thinking you have duplicate content.
As mentioned in the other thread [linked in the OP] both are now set to www.
1] Do you think both www. and non www. versions should be submitted to Google via their Webmaster Tools Dashboard? Or just one?
2] How about the user/login issue as per the first post in this thread? My initial impression was this was a cache or cookie related issue, no?
Thanks again in advance.
1. I would only submit the version you are using. If you're redirecting non www. addresses to their www. counterparts, you should be okay just submitting the www.
2. It's certainly related to the cookies. Cookies are picky things and only work on the domain they are specified for to stop other sites accessing them. Your browser considers
www.mysite.com and mysite.com to be two different hosts.
(2013-01-15, 06:32 PM)Euan T. Wrote: [ -> ]1. I would only submit the version you are using. If you're redirecting non www. addresses to their www. counterparts, you should be okay just submitting the www.
2. It's certainly related to the cookies. Cookies are picky things and only work on the domain they are specified for to stop other sites accessing them. Your browser considers www.mysite.com and mysite.com to be two different hosts.
Not strictly true, www. simply tells the brower to use the http:// protocol, as opposed to any of the other allowed protocols. http and www have nothing to do with hosts, they are the same command.
Other protocols allowed are https a secure secure sever, ftp for the transfer of files between server and user, file, edit and news, some sites use all of these protocols to access varying parts of the website.
Actually, www. is a subdomain. I can easily set up a site that is only accessed via www. and simply not found for requests without it. You have to specifically add it to the virtualhost (unless you use a wildcard subdomain, which I tend not to).
Thanks chaps for the input.
1] I have added a redirect to my .htaccess file to manage the non www. to the www. ...and it works successfully.
2] Well, this still seems a little unclear. What I will do is see if the redirect will eliminate the need to manage this now.
(2013-01-15, 08:17 PM)Euan T. Wrote: [ -> ]Also ensure your cookie domain is set to www.mydomain.com
At the moment the cookie domain is set to: blank
and the cookie path is set to: /
The forum resides in the root.
Do you still feel the cookie domain should be set to
http://www.mydomain.com ?
Just want to be 100% sure. Thanks as always!
No, the domain should be
www.mydomain.com
Not sure why it added http:// to my last post.