Loriath wrote:Its not a cookie issue Boxcar. It is a domain issue. For Example: joe.site.com is not the same as site.com, it is a subdomain. Most hosts provide you with a main Cname address, such as site.com and also for backwards compatability, direct
http://www.site.com to the main site.com so they are equals. if that was the case, then the dns alias would tell my browser that these domains are equivalent. (or this could be done in mod rewrite for Apache webserver)
But for some reason, whether it is in the rewrite rules (don't make me explain that one lol I don't have the time) or the dns records or in the subdomain settings, they are not, and it means the browser does not see them as equal. This means that anyone that does not accept Third Party cookies, like me so I don't get all the tracker crap when I visit most sites (like facebook, ad sites, etc..), sees them as separate sites.
Technically, if they wanted to, they could make unmarkedboxcar.elitepve.com point directly to your profile page here on the forums (or for all of us). but that is a waste of resources.
Hi Loriath,
I took some time to try to understand what you would like me to achieve by rewrite rules. In the case of elitepve.com there are two A records, one witha dn one without www, both pointing to the same IPs (v4 and v6). The webserver then treats both exactly the same, meaning pointing to the same home directory.
This is exactly what a rewrite rule would also achieve if the both names would
not point to the same home by default. So adding a rewrite rule would change nothing. (Rewrite changes what is served, not what your browser thinks it sees). For example, try going to
http://elitepve.com/app.php/page/about, and then to
page/about. In this case it's mod rewrite that is serving you the same content for both.
Now the cookie that is set by the site has elitepve.com as domainname, no matter which name you used to access it. (Again, rewrite would not change that). Your browser is throwing a tantrum over that.
There are two things I could do: first i could change the cookie domain to
www.elitepve.com, but that would mess up all cookies already set, and would cause the same issue for you if you start by elitepve.com without www. Or I could implement a http redirect from
www.elitepve.com to elitepve.com to force you to use that variant, what would result in a reload everytime someone comes via the www extension.
The first solution is just the same as before but vice versa, the second solution makes no sense, if both names point to the same content anyway, IMHO.
If i have totally misunderstood the problem, please let me know.
Regards
Wolf