So I noticed the other night when messing on my website that if I'm logged in at http://mysite.com, then go to www.mysite.com, it's not logged in. And I assume this is because when the cookie is created, it's based on the URL location, and since the www is different without it, it doesn't recognize the cookie that is set when I add the www. Is there a simple fix for this?

You are correct. mysite.com and www.mysite.com are different domains. Since one is a subdomain of the other it is possible to use one cookie for both (by designating authority for cross-site scripting to the parent mysite.com) HOWEVER: Having your site accessible under multiple domains (www and no www count as multiple domains) is VERY BAD for SEO as it can flag you in the search engines as having duplicate content.

Pick either www or no www, but don't do both. Have a redirect on whichever you DON'T do so that visitors that type in the alternate will still end up at your site.

not sure you actually answerd the question there nyef...

But what he said is true you should stick to one or the other i personally think the www. thing should be dropped full stop. its silly..

anwyay

When you set the cookie you should have .domain.tld NOT domain.tld this means it works for that domain plus subdomains (ie www.)

example:

PHP Code:

setcookie("TestCookie", $value, time()+3600, "/", ".example.com", 1); 


Rep points apprieciated

Dan

If a cookie is set for domain .example.com (with the dot in front) it would be passed by browser to example.com and all its subdomains. If a cookie is set for domain .www.example.com it will be passed only to this subdomian and all its fourth level subdomains (test.www.example.com, asdf.www.example.com) and so on. You should check your cookie setting logic and correct it accordingly.

Redirect non www links to www links via this code in your .htaccess:

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.domain\.com
RewriteRule (.*) http://www.domain.com/$1 [L,R=301]