Since there are not more than one renderosity server, and we're being bounced between them -- there's a cookie specification issue you guys may want to fix.

Currently, the cookie is being set tot he full domain name (i.e. www.renderosity.com) on login. When you are switched to community.renderosity.com the cookie domain, with the www, is no longer valid.

The HTTP cookies specification and the CGI mudule for Perl both support setting the domain of a cookie to a less specific setting. The 'wildcard' is done by prefixing the domain with a leading dot -- for instacne, '.renderosity.com' would be recignised by all compliant browsers (in other words, just about all browsers anymore) as being valid for and to be sent to www.renderosity.com, community.renderosity.com, arthur.renderosity,com, and snorklepuss.renderosity.com.

Without the leading dot, it would only be valid for renderosity.com (no subdomain), and with anything preceding the dot, only the domain name (unless a further preceding dot was added, which would allow it for *.www.renderosity.com, for example).

Basically, with the cookie domain incorrect, when we pop to a different server we are no longer logged in, and if we peop to a different server from a link to a member-only function (free stuff, IM functions, My Home Page, etc) things break.

thanks looking into.

No worries.

BTW, the one restriction is that there has to be more than one dot if the dot is the first character. That is to say, 'renderosity.com' is fine, but doesn't get sent to www.renderosity.com. '.renderosity.com' is fine, and gets sent to www.renderosity.com and renderosity.com.

Just .com, however, is ignored, and treated as if SERVER_NAME was the setting. This is to prevent sharing of cookies between domains which is a security risk. If it wasn't disallowed, one could set a cookie for any .com domain, whcih would not only be bad, it would also slow down the Internet. B^)