subdomain logins dont work in IE

[gmiernicki]

I had encountered a bug, but I'm not sure if its in WebsiteBaker or Internet Explorer. Here's the situation:

1) www.site.com is setup running WebsiteBaker 2.6.2
2) another.site.com is also setup running WebsiteBaker 2.6.2
3) Front-End Login capability is setup on the subdomain another.site.com

Steps to reproduce the error

1) Visit www.site.com front page in Internet Explorer 5/6/7
2) Go to another.site.com and then try to login
3) Login is unsuccessful and the login page refreshes with empty values after the Login button is clicked.

Additional Thoughts:

I setup php to sput out the $_SESSION / $_POST / $_GET data on the page to view the variables after the submit. It appears the username and password aren't getting posted to the login process page and it just jumps back to the login page again.

Everything works fine in all versions of firefox and opera.

Question: did we find a new IE bug, or is this a bug in websitebaker?

[kweitzel]

It sounds more like you use the same session header for both installations to me ...

cheers

Klaus

[gmiernicki]

So the subdomain just requires a different session header? I didn't think this would be a problem since the www.site.com site doesn't have login capability enabled and shouldn't be setting session data.

Am I wrong with thinking this?

Also, where might I be able to configure the session header?

[ruebenwurzel]

Hello,

you can define a seesion id in the advanced settings of WB. If you have different WB installations it is strongly recommanded to set for every WB install a different Seesion ID.

Also befor installing a second WB it is recommanded to clean all browser cahces. This way you can be shure that install does not fail. If you now have a install with blank settings, you should delete this install, cleaning your cache a do a new clean install.

Matthias

[gmiernicki]

Thanks ruebenwurzel, kweitzel! This really helped solve the problems we were having with a pretty big production site.

Before, it was unbeknown est to us why this was only occurring in IE and not other browsers. It was thought that it was a bug in IE, but now it seems to be just the way IE handles session data. I guess other browsers like firefox and opera encapsulate session data per subdomain whereas IE probably does it per domain.



Best Regards,