Hi!
Ok... I'm going to have to admit my own error here. When I initially built a site (ccchapel.com), I don't think I handled Cookies the best way, since I was learning. When I initially created the cookie for the user to track their "default campus" (in case no subdomain was present in the URL) and their last visit.
Now, I have users that have multiple cookies, one for each subdomain (aurora.ccchapel.com, hudson.ccchapel.com, stow.ccchapel.com, etc.). So when they access a page like ccchapel.com/students, which is supposed to load the appropriate campus data based on the Cookie key, it can't always find one or uses a "default" one that was initialized to "hudson."
I think I fixed it by setting the domain when the cookie is created (myCookie.Domain = ".ccchapel.com"), but I'm not sure if I should add a temporary script that clears out all the other "CCC" cookies. It seems like Chrome and Safari match the "ccchapel.com" cookie rather than the new ".ccchapel.co ...
Go to the complete details ...