I visited a user today who was having issues.

He's using IE.

What I found was, if he's logged onto the board at wwww.mydomain.com/forums/ubbthreads, and then visits a page at mydomain.com/forums/ubbthreads (without the "www") he shows as not logged in. He has to log-in again while on the non-www url.

In my domains for HTTP Referer Check, I have all of these set:
http://www.mydomain.com
http://mydomain.com
http://www.mydomain.com
mydomain.com

This wouldn't be such a big deal, but I have parts of my site that users have to be logged in to visit. For whatever reason, sometimes people will email links without the "www"

Is there something I can adjust on my end so that when someone is logged in (no matter what URL they started at) they can jump around to both versions of the URL and still show as logged in?

no - that is correct.

http://www.mydomain.com is technically a sub-domain to mydomain.com and is therefore treated as a separate domain as far as the cookies are concerned.

This is not a limitation with threads.

You might be better have your site set-up so that any requests for domain.com/* are directed to http://www.domain.com/*

Thanks IAN!

What's the best way to go about this? Do I set up the redirect right in my DNS manager? Or, should I edit my htaccess file?

I think I remember Gizmo commenting on this very thing. I'll do a search.

Found it:
http://www.ubbcentral.com/forums/ubbthre...true#Post172823

Awwe, one of my favorite topics and it's solved by the time I get here :sniffle:

.htaccess

did it work ?

Yes, like a charm. However, with every little switch, something else that pops up.

Turns out, I have quite a few users linking to images from a photo gallery on my site. A lot of those images do not contain the "www" in the URL.

So, for some users they aren't showing up in avatar fields or posts. I think it's mainly with IE. (I see them fine with Firefox.).

Going forward, any image URLs they copy will have the "www", but for anything already linked to without the "www" they get the red x.

OK Gizmo, here's your chance...solve this one.

I don't see why that'd happen, if you used my code above in your .htaccess it should transparently forward them to the new image...